Input: Boolean (lab)

Input: Boolean (lab) is a checkbox that outputs a BOOLEAN. One widget, one value, one output. It's the kind of node you'd swear is pointless - until you hit a node that takes a boolean input instead of a widget, or you want a workflow-wide switch you can flip once at the top instead of hunting through a dozen nodes.

ComfyUI is inconsistent about where toggles live: some nodes expose a boolean as a widget on the node, others only accept it as a wired input. When you need to feed a boolean into a wired slot, or route it into a Convert to Any and then into whatever logic you're building, a constant-provider node is the clean way.

What it is

One input widget, value (default true), one output, boolean. Tick it, wire it, done. No conversion, no logic - it just exists so a true/false has a place to come from that isn't a random node's buried widget.

Where it earns its keep:

• A master switch - one visible toggle at the top of a workflow that feeds a bypass or a branch downstream.
• Feeding typed slots - a node that declares a BOOLEAN input gets a properly typed value, not a string that will error at runtime.
• Building logic - boolean into Convert to Any, into a format template, into a conditional. The pack's Convert to Any handles booleans fine, so this is a legit data source for graphs that branch.

Install

ComfyLab Pack installs as one package (nodes display with "(lab)" suffixes). ComfyUI Manager: search ComfyLab Pack, install, restart. Manual:

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

Restart after. No model files, no heavy dependencies.

Gotchas

• It's a constant, not a switch with memory. No latching, no "remember last state" - read it as a static value at run time.
• Don't build a fancier graph than you need. If the target node already has a checkbox widget, wiring a boolean input and using its widget is a conflict you'll debug for no reason. Pick one source per boolean.

It's three lines of Python wearing a nice node costume. But when a workflow needs a typed true at a specific spot, this is the least surprising way to provide one.