👺 User Input (Boolean)

In a big workflow, "which toggle was that again?" is a real problem. ComfyUI lets you build graphs where half the nodes have a plain boolean checkbox and zero context about what it controls. 👺 User Input (Boolean) is this pack's answer: a boolean input you can give a name - apply_controlnet, shuffle_first, whatever you want - that passes the value through as a labeled output. It's one of four user-input nodes in the pack (Boolean, Float, Seed, String), all built on the same idea: name your inputs so future-you can read the graph.

What it actually does is almost insultingly simple. You set the value toggle, and the node emits that boolean on its output. That's it. The input_name field is a label with zero effect on the value - it exists for the pack's controller/UI layer (and for your own sanity when you hover over the node). So if you're expecting magic like the value syncing to other nodes by name, adjust that expectation now: it's a labeled passthrough, full stop.

Where it earns its place is as the wiring hub for a single source of truth. Put one of these at the top of your graph labeled enable_upscale, wire its boolean output into every node that cares about upscaling, and you've got one toggle controlling five nodes instead of five checkboxes to hunt down. That's the pattern this whole user-input family is for - and if you later move to the pack's controller system (the Nilor Preset/Group nodes built for the Brando UI), the _controller_hook output on these nodes is what lets you bind them into groups declaratively. In plain ComfyUI that hook output comes out None and you can ignore it.

Inputs and output

• input_name - the label, e.g. my_bool_input. Cosmetic in vanilla ComfyUI, semantic in the controller UI.
• value - the true/false toggle (default false).
• boolean (BOOLEAN output) - the pass-through value. Wire it wherever a boolean is consumed.
• _controller_hook - only used by the pack's controller nodes; ignore it otherwise.

Installing it

Part of Nilor Nodes (nilor-corp/nilor-nodes):

cd ComfyUI/custom_nodes
git clone https://github.com/nilor-corp/nilor-nodes

or ComfyUI Manager → search "Nilor Nodes" → install → restart. No model files. The README lists Kijai's comfyui-kjnodes as a prerequisite, and the pack's dependency stack is heavy for a passthrough node (boto3, fastapi, huggingface_hub, openexr all install regardless).

Troubleshooting

The only way to be confused here is to expect more than it does. It doesn't broadcast its name to other nodes, it doesn't remember state across runs, and the hook output is inert outside the controller system. If you want actual graph-wide boolean control without the Brando UI, you wire the output manually - the label is for humans. There's no community support for this pack, so the source is your reference if anything surprises you. If you only need one toggle and your workflow is small, honestly, a plain checkbox is fewer nodes. This family earns its keep when the graph is big enough that naming things is the point.