# Add new button to Node red editor

**URL:** <https://discourse.nodered.org/t/add-new-button-to-node-red-editor/61004>\
**Category:** Core Development\
**Created:** [8 April 2022 19:54 UTC](https://discourse.nodered.org/t/add-new-button-to-node-red-editor/61004 "2022-04-08T19:54:42Z")\
**Posts on this page:** 5\
**Page:** 1

<div class="post-metadata">

**Author:** ![flowaero](https://avatars.discourse-cdn.com/v4/letter/f/53a042/32.png) [@flowaero](https://discourse.nodered.org/u/flowaero)\
**Post date:** [8 April 2022 19:54 UTC](https://discourse.nodered.org/t/add-new-button-to-node-red-editor/61004/1 "2022-04-08T19:54:43Z")

</div>

Hi, I want to add new button/s next to the node-red native deploy button. What is the way to accomplish this?

The reason to do this -- the new button will deploy the flows to another instance of headless node red. This way, we (startup), will have separation between development and production deployment.

---

<div class="post-metadata">

**Author:** ![bakman2](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/bakman2/32/6207_2.png) [@bakman2](https://discourse.nodered.org/u/bakman2)\
**Post date:** [9 April 2022 05:38 UTC](https://discourse.nodered.org/t/add-new-button-to-node-red-editor/61004/2 "2022-04-09T05:38:59Z")

</div>

Welcome to the forum.

I don't know how critical your environment is, but what if someone clicks the wrong button ? Hint: this is going to happen.

Note there are various [API's available](https://nodered.org/docs/api/) for the editor and runtime.

You could also create an additional flow that performs an API call [to post/deploy](https://nodered.org/docs/api/admin/methods/post/flows/) the new flow at some instance, perhaps combine [it with a listener hook](https://nodered.org/docs/api/hooks/). This allows to build in guards and logic that can prevent mistakes.

---

<div class="post-metadata">

**Author:** ![paulkeates](https://avatars.discourse-cdn.com/v4/letter/p/9de053/32.png) [@paulkeates](https://discourse.nodered.org/u/paulkeates)\
**Post date:** [10 April 2022 14:21 UTC](https://discourse.nodered.org/t/add-new-button-to-node-red-editor/61004/3 "2022-04-10T14:21:36Z")

</div>

Hi,

It is possible to do it (add a button on the top of the page):  
 ![image](https://us1.discourse-cdn.com/flex026/uploads/nodered/original/3X/d/2/d24a77e97bd6acf4af78077e86f2480b8aa8b8e8.png)

I'm sorry though - I don't remember how I did it.  
I installed 'something' (a long time ago) that always displays that button...  
All it does (when clicked) is open a new tab with the /ui/ loaded (the node-red Dashboard).

Personally, I'd like it changed from the existing colour (red) so it does not 'collide' with the existing 'Deploy' button.

I'll try to figure out what I installed and update you...

Cheers,

Paul

---

<div class="post-metadata">

**Author:** ![JayDickson](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/jaydickson/32/90592_2.png) [@JayDickson](https://discourse.nodered.org/u/JayDickson)\
**Post date:** [10 April 2022 16:10 UTC](https://discourse.nodered.org/t/add-new-button-to-node-red-editor/61004/4 "2022-04-10T16:10:33Z")

</div>

I would personally recommend enabling the [projects](https://nodered.org/docs/user-guide/projects/#working-with-projects) feature and running dev, test, and prod as completely separate environments. You could then do all your work in dev, commit those changes to the repo, and pull them down in the test environment for validation, followed by pulling them down on prod if everything checks out. This also gives you better versioning and rollback capability, which is awesome if you're working on something mission critical.

---

<div class="post-metadata">

**Author:** ![system](https://us1.discourse-cdn.com/flex026/uploads/nodered/original/1X/d073cd938eafa2e558d7c2cd59003b3ef4963033.png) [@system](https://discourse.nodered.org/u/system)\
**Post date:** [9 June 2022 16:11 UTC](https://discourse.nodered.org/t/add-new-button-to-node-red-editor/61004/5 "2022-06-09T16:11:13Z")

</div>

This topic was automatically closed 60 days after the last reply. New replies are no longer allowed.