# Disable wires/connections between nodes

**URL:** <https://discourse.nodered.org/t/disable-wires-connections-between-nodes/99857>\
**Category:** Feature Requests\
**Tags:** editor, feature-request\
**Created:** [3 December 2025 20:42 UTC](https://discourse.nodered.org/t/disable-wires-connections-between-nodes/99857 "2025-12-03T20:42:11Z")\
**Posts on this page:** 20\
**Page:** 2

<div class="post-metadata">

**Author:** ![gregorius](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/gregorius/32/73816_2.png) [@gregorius](https://discourse.nodered.org/u/gregorius)\
**Post date:** [8 December 2025 17:47 UTC](https://discourse.nodered.org/t/disable-wires-connections-between-nodes/99857/22 "2025-12-08T17:47:54Z")

</div>

> [@gdvine](#):
>
> Would be very useful to disable a connection rather than having to delete it

What's wrong with this workaround --\> [Disable wires/connections between nodes - #8 by gregorius](https://discourse.nodered.org/t/disable-wires-connections-between-nodes/99857/8)

---

<div class="post-metadata">

**Author:** ![gdvine](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/gdvine/32/101799_2.png) [@gdvine](https://discourse.nodered.org/u/gdvine)\
**Post date:** [8 December 2025 21:00 UTC](https://discourse.nodered.org/t/disable-wires-connections-between-nodes/99857/23 "2025-12-08T21:00:00Z")

</div>

🤦‍♂️ That’s what I get for scanning the thread first thing in the morning. Very good workaround! Thanks

The OP implied there was a way to create some sort of macro to do this with a keyboard shortcut. Making macros isn’t possible, right? He was just referring to using 2 shortcuts in a row, right?

---

<div class="post-metadata">

**Author:** ![gregorius](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/gregorius/32/73816_2.png) [@gregorius](https://discourse.nodered.org/u/gregorius)\
**Post date:** [8 December 2025 21:40 UTC](https://discourse.nodered.org/t/disable-wires-connections-between-nodes/99857/24 "2025-12-08T21:40:52Z")

</div>

Just discovered this shortcut that isn't normally assigned:

 ![Screenshot 2025-12-08 at 22.35.01](https://us1.discourse-cdn.com/flex026/uploads/nodered/original/3X/8/9/89889b300c2b2d79284b83b84335868d6b56b3f1.png)

Assign that with some keyboard shortcut. And then assign this to a keyboard shortcut

![Screenshot 2025-12-08 at 22.39.44](https://us1.discourse-cdn.com/flex026/uploads/nodered/original/3X/c/d/cdedea9f7bc2707584dab8e47bb2e1b137f4d50b.png)

And then it should be quick to disable wires.

---

<div class="post-metadata">

**Author:** ![Trying\_to\_learn](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/trying_to_learn/32/28400_2.png) [@Trying\_to\_learn](https://discourse.nodered.org/u/Trying_to_learn)\
**Post date:** [9 December 2025 05:33 UTC](https://discourse.nodered.org/t/disable-wires-connections-between-nodes/99857/25 "2025-12-09T05:33:28Z")

</div>

Well, it will be quick to _disable_ the wire. But you would still have to DEPLOY to get it applied.

---

<div class="post-metadata">

**Author:** ![gregorius](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/gregorius/32/73816_2.png) [@gregorius](https://discourse.nodered.org/u/gregorius)\
**Post date:** [9 December 2025 05:36 UTC](https://discourse.nodered.org/t/disable-wires-connections-between-nodes/99857/26 "2025-12-09T05:36:06Z")

</div>

> [@Trying\_to\_learn](#):
>
> still have to DEPLOY to get it applied.

Add a shortcut for the deploy action, so that's three shortcuts.

---

<div class="post-metadata">

**Author:** ![Trying\_to\_learn](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/trying_to_learn/32/28400_2.png) [@Trying\_to\_learn](https://discourse.nodered.org/u/Trying_to_learn)\
**Post date:** [9 December 2025 05:39 UTC](https://discourse.nodered.org/t/disable-wires-connections-between-nodes/99857/27 "2025-12-09T05:39:25Z")

</div>

It wasn't meant as a put down. I was only saying that it is still a step which needs to be done.

---

<div class="post-metadata">

**Author:** ![gregorius](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/gregorius/32/73816_2.png) [@gregorius](https://discourse.nodered.org/u/gregorius)\
**Post date:** [9 December 2025 15:26 UTC](https://discourse.nodered.org/t/disable-wires-connections-between-nodes/99857/28 "2025-12-09T15:26:35Z")

</div>

> [@Trying\_to\_learn](#):
>
> It wasn't meant as a put down

Did I sound like I took as such? Sorry - I didn't read it at all like that. It was dark and stormy and early humourless morning.

I, for my part, map deploy to Cmd-S so it's not actually any work to deploy ...

---

<div class="post-metadata">

**Author:** ![rko](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/rko/32/45807_2.png) [@rko](https://discourse.nodered.org/u/rko)\
**Post date:** [9 December 2025 17:03 UTC](https://discourse.nodered.org/t/disable-wires-connections-between-nodes/99857/29 "2025-12-09T17:03:58Z")

</div>

Since this basically works with the workaround now, I was wondering whether this feature could be added quite easily. From an implementation perspective, the GUI would provide a “disable wire” function, and in the background there would still be a junction node but hidden, meaning it would no longer be visible to the user - done. A bit “ugly” in terms of implementation, but maybe worth considering?

---

<div class="post-metadata">

**Author:** ![gregorius](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/gregorius/32/73816_2.png) [@gregorius](https://discourse.nodered.org/u/gregorius)\
**Post date:** [9 December 2025 17:10 UTC](https://discourse.nodered.org/t/disable-wires-connections-between-nodes/99857/30 "2025-12-09T17:10:46Z")

</div>

> [@rko](#):
>
> but maybe worth considering?

No.

Either properly so that it's fully shown in frontend, i.e. that an junction node was inserted and it has been disabled or ..... - oh, in fact, I can't think of an alternative 😉

So, I for one, am against such a solution but hey, IDC.

---

<div class="post-metadata">

**Author:** ![rko](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/rko/32/45807_2.png) [@rko](https://discourse.nodered.org/u/rko)\
**Post date:** [9 December 2025 21:58 UTC](https://discourse.nodered.org/t/disable-wires-connections-between-nodes/99857/31 "2025-12-09T21:58:22Z")

</div>

"Properly" would probably mean that wires can have properties (now that's a cool sentence 🤣). But I don't think that's the case so far. The junction node also seems to be a workaround to avoid exactly this problem.

By IDC, do you mean "I don’t care"? About what?

---

<div class="post-metadata">

**Author:** ![gregorius](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/gregorius/32/73816_2.png) [@gregorius](https://discourse.nodered.org/u/gregorius)\
**Post date:** [10 December 2025 04:49 UTC](https://discourse.nodered.org/t/disable-wires-connections-between-nodes/99857/32 "2025-12-10T04:49:23Z")

</div>

> [@rko](#):
>
> and in the background there would still be a junction node but hidden

Another constellation that the frontend or NR has to work out whether to "hide" the junction node:

 ![Screenshot 2025-12-10 at 05.39.11](https://us1.discourse-cdn.com/flex026/uploads/nodered/original/3X/2/2/222fb1c8992d6642f3d082c1ede09776b931035f.png)

 ![Screenshot 2025-12-10 at 05.40.49](https://us1.discourse-cdn.com/flex026/uploads/nodered/original/3X/0/a/0acf140512d6bdf3bd7852a81444d201882e2623.png)

It's the hiding of the node that isn't considered in the suggestion. It's not that simple and as soon as you go into the details, you discover this is non-trivial consideration.

> [@rko](#):
>
> The junction node also seems to be a workaround

The junction node servers another purposes, it is being misused here. It's purpose is to bundle multiple connections from many nodes to one node or vice versa. Visually it looks nicer. For the execution of the flow, the junction node can be eliminated, it plays no role.

> [@rko](#):
>
> IDC

It's a typo, I meant to write IDGFB

---

<div class="post-metadata">

**Author:** ![rko](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/rko/32/45807_2.png) [@rko](https://discourse.nodered.org/u/rko)\
**Post date:** [10 December 2025 07:21 UTC](https://discourse.nodered.org/t/disable-wires-connections-between-nodes/99857/33 "2025-12-10T07:21:48Z")

</div>

It's indeed possible that hiding the `JN` node might create more problems than it solves. If still considered, I would start with the simplest case (`N ---> JN ---> N`), and probably stop there, until wires are allowed to have properties.

IDGFBE

---

<div class="post-metadata">

**Author:** ![gregorius](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/gregorius/32/73816_2.png) [@gregorius](https://discourse.nodered.org/u/gregorius)\
**Post date:** [10 December 2025 07:40 UTC](https://discourse.nodered.org/t/disable-wires-connections-between-nodes/99857/34 "2025-12-10T07:40:15Z")

</div>

> [@rko](#):
>
> IDGFBE

Confucius once said may the boomerang bend and come back as a banana.

> [@rko](#):
>
> I would start with the simplest case

Have a go yourself, edit the editor code and see if you can implement this. That's the best approach, to come with a working solution and not an open problem.

If you don't code JS, it's the best time to start: plenty of AI helpers to guide you along the path of becoming a JS Jedi.

Damn these dark and stormy mornings....

---

<div class="post-metadata">

**Author:** ![rko](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/rko/32/45807_2.png) [@rko](https://discourse.nodered.org/u/rko)\
**Post date:** [10 December 2025 07:49 UTC](https://discourse.nodered.org/t/disable-wires-connections-between-nodes/99857/35 "2025-12-10T07:49:21Z")

</div>

> [@gregorius](#):
>
> Confucius once said may the boomerang bend and come back as a banana.

You should consider changing your LLM model 🤓

> [@gregorius](#):
>
> Have a go yourself, edit the editor code and see if you can implement this. That's the best approach, to come with a working solution and not an open problem.

I might, if my family lets me.

---

<div class="post-metadata">

**Author:** ![gregorius](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/gregorius/32/73816_2.png) [@gregorius](https://discourse.nodered.org/u/gregorius)\
**Post date:** [10 December 2025 08:01 UTC](https://discourse.nodered.org/t/disable-wires-connections-between-nodes/99857/36 "2025-12-10T08:01:06Z")

</div>

> [@rko](#):
>
> You should consider changing your LLM model

Folks often confuse me with an LLM but then again an LLM would say that.

---

<div class="post-metadata">

**Author:** ![dceejay](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/dceejay/32/38_2.png) [@dceejay](https://discourse.nodered.org/u/dceejay)\
**Post date:** [10 December 2025 08:05 UTC](https://discourse.nodered.org/t/disable-wires-connections-between-nodes/99857/37 "2025-12-10T08:05:18Z")

</div>

Why not just disable the node the wire goes to, or comes from ? Saves adding a junction then disabling it.

---

<div class="post-metadata">

**Author:** ![rko](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/rko/32/45807_2.png) [@rko](https://discourse.nodered.org/u/rko)\
**Post date:** [10 December 2025 08:12 UTC](https://discourse.nodered.org/t/disable-wires-connections-between-nodes/99857/38 "2025-12-10T08:12:26Z")

</div>

If it's for example a node with multiple outputs/inputs, and I want to disable a single connection. Disabling the node would block everything, no?

Once I have some time to go back to the flow I was working on, I can provide a proper example, where it would make sense to disable a wire, in my opinion.

---

<div class="post-metadata">

**Author:** ![Paul-Reed](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/paul-reed/32/66906_2.png) [@Paul-Reed](https://discourse.nodered.org/u/Paul-Reed)\
**Post date:** [10 December 2025 08:58 UTC](https://discourse.nodered.org/t/disable-wires-connections-between-nodes/99857/39 "2025-12-10T08:58:45Z")

</div>

Has [node-red-contrib-flowgate (node) - Node-RED](https://flows.nodered.org/node/node-red-contrib-flowgate) been considered…

---

<div class="post-metadata">

**Author:** ![rko](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/rko/32/45807_2.png) [@rko](https://discourse.nodered.org/u/rko)\
**Post date:** [10 December 2025 09:19 UTC](https://discourse.nodered.org/t/disable-wires-connections-between-nodes/99857/40 "2025-12-10T09:19:21Z")

</div>

That would work as well. I just want things to be tidy (without extra "nodes" and logic).

---

<div class="post-metadata">

**Author:** ![dceejay](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/dceejay/32/38_2.png) [@dceejay](https://discourse.nodered.org/u/dceejay)\
**Post date:** [10 December 2025 09:40 UTC](https://discourse.nodered.org/t/disable-wires-connections-between-nodes/99857/41 "2025-12-10T09:40:59Z")

</div>

Yes - though in my experience it is fairly rare to have a node with multiple outputs feed another with multiple inputs - usually (for me) at least one of them just has a single connection - which is the end I would disable, but yes no doubt multiple to multiple do occur.

[Previous page](https://discourse.nodered.org/t/disable-wires-connections-between-nodes/99857.md?page=1)

[Next page](https://discourse.nodered.org/t/disable-wires-connections-between-nodes/99857.md?page=3)