Remote Boolean (on prompt)

This one works differently from almost everything else in ComfyUI, so it's worth being explicit about the mechanism before touching it. Normally, to control a widget on another node, you right-click it, choose "Convert widget to input," and wire a value in - the connection is visible on the graph. Remote Boolean skips all of that. At the start of prompt execution, it reaches directly into another node by its numeric ID and forcibly overwrites one of that node's widget values. No wire. No visible connection on the graph at all - just a node holding an ID, a widget name, and a value.

Why this exists

It's built for automation: loop-driven or programmatically-assembled workflows where you want to flip a switch, mute state, or boolean toggle on a distant node without hand-wiring a conditional path through the graph to reach it. The README's own framing is blunt about it - "this node forcibly sets the widget_value of node_id" - and it's filed under the pack's _for_test Logic category, which is the author's own signal that this is a power tool for scripted/loop workflows, not a normal-graph building block.

The inputs

• node_id (INT, default 0) - the numeric ID of the target node whose widget you're overwriting. Find it via ComfyUI-Manager's node badges (shown as #ID Nickname), or ComfyUI's own node info.
• widget_name (STRING) - the internal name of the widget to overwrite. This has to match exactly - and it isn't always identical to the label you see on the node itself.
• value (BOOLEAN, default true) - what to force the widget to.

There's no output - is_output_node is true, meaning this executes as a side effect on the target node rather than producing something to wire further downstream.

The trap: node IDs aren't permanent

This is the thing that actually bites people, and it's the honest reason to be careful with this node rather than lean on it casually: node IDs can shift as you add, remove, or reorder nodes in a graph, and some workflows renumber on reload. A Remote Boolean pointed at node_id: 47 today can silently start hitting the wrong node - or no node at all - after you've edited the graph, and there's nothing on the wire to tell you that happened. Per the README, a mismatched widget type is simply disregarded rather than erroring, so a stale or wrong node_id/widget_name pair fails silently instead of loudly.

Practical mitigation: re-check the target ID after any graph edit near the node you're remote-controlling, and label this node clearly (a note, a color) so future-you remembers it's quietly reaching across the graph rather than assuming a wire will show it.

Installing it

Bundled with the pack. Via ComfyUI Manager: search ComfyUI Impact Pack, Install, restart. Manually:

cd ComfyUI/custom_nodes
git clone https://github.com/ltdrdata/ComfyUI-Impact-Pack
cd ComfyUI-Impact-Pack
pip install -r requirements.txt

(portable: python_embeded\python.exe -m pip install -r requirements.txt), restart. No models needed.

Common issues

Value not applying: check node_id first (it may have shifted), then widget_name for an exact match - mismatches are silently ignored rather than erroring, per the README, so nothing on screen tells you it failed. And if you're building anything you'll come back to later, leave yourself a note near this node - it's the one part of your graph whose actual effect isn't visible anywhere on the wires.