Boolean Control Output 🦾
Drive two modes from a single switch
- text
- float
- int
- is_true
- is_false
Boolean Control Output is a "profile switcher" disguised as a logic node. You preconfigure two complete sets of values - text, a float, an integer - and one boolean flips the whole bundle at once. Flip it and you get a different prompt line, a different denoise, a different step count, all simultaneously.
The use case is obvious the second you see it: draft vs. final. You set the true side to "quick test" settings (low steps, low CFG, a placeholder prompt) and the false side to your real production values. One checkbox, and every downstream node sees the right numbers without you hunting through four widgets.
How it works
It's a deterministic fan-out. boolean_input selects between the two configured triples: when true, the node outputs true_text, true_float, true_int; when false, false_text, false_float, false_int. On top of that it always emits is_true and is_false - two boolean flags, one true and one false, so you can drive other boolean switches from the same decision without recomputing it.
So the outputs aren't just values - they're a tiny control bus. The is_true/is_false pair is genuinely handy for chaining: wire is_true into the boolean of a Boolean Switch or the ANY of an If node and you've extended the same choice to another branch for free.
The inputs that matter
boolean_input(required, default true) - the switch.true_text/true_float/true_int- the "on" profile.false_text/false_float/false_int- the "off" profile.
Outputs: text (STRING), float (FLOAT), int (INT), plus is_true and is_false (both BOOLEAN).
Install
Part of ComfyUI-Beyond_nodes. ComfyUI Manager → search "Beyond_nodes" → install → restart. Manual:
cd ComfyUI/custom_nodes
git clone https://github.com/beyondprompting/ComfyUI-Beyond_nodes
Restart. No extra dependencies.
Common issues
- The text inputs won't accept connections.
true_text/false_textare plain widgets by default. If you want them fed by other nodes, the pack doesn't force them into inputs - use a String node and a Boolean Switch if you need dynamic text. - I only need two of the five outputs. Fine - leave the rest dangling. Nothing requires you to use them all.
- I expected an image switch. This one is values only. For swapping images or masks, the pack's ImageMaskSwitch (or plain BooleanSwitch for any type) is the right tool.
It's a small node, but it's the one that turns "tweak six settings by hand each run" into "flip a checkbox." In the ecosystem doc's terms, it's a workflow-hygiene node - it doesn't generate anything, it keeps your graph sane.
Inputs (7)
| Name | Type | Default | Description |
|---|---|---|---|
| boolean_input | BOOLEAN | true | — |
| true_text | STRING | — | |
| true_float | FLOAT | 1.00 | — |
| true_int | INT | 1 | — |
| false_text | STRING | — | |
| false_float | FLOAT | 0.0 | — |
| false_int | INT | 0 | — |
Outputs (5)
| Name | Type | Description |
|---|---|---|
| text | STRING | — |
| float | FLOAT | — |
| int | INT | — |
| is_true | BOOLEAN | — |
| is_false | BOOLEAN | — |