Boolean Param

Some parameters aren't numbers, they're decisions. "Apply the LoRA or not." "Do the upscale pass or skip it." "Use the detailer." Those decisions are booleans, and in a hardcoded workflow they're baked into the graph. Boolean Param is the pack's way of turning a decision into a request field: one checkbox, one boolean output, nothing else.

It takes a single value input - a boolean that defaults to true - and passes it straight through as a value output. Wire that output into any node that takes a BOOLEAN input. The obvious companion is HelperModelSwitch (the pack's model router, which picks between two model streams based on exactly this kind of boolean), but anything with a boolean input works: conditional nodes, toggle-style settings, switches in other packs.

The default is the trap

The one thing that catches people is the default: it's true, not false. If you drop this node in, forget about it, and wire it into a switch, the "on" behavior is what you get until you change it. When you're building an API flow, think carefully about which state means what for your backend - an API that omits a field should probably leave the workflow in the state you intend as the fallback, and true is a specific choice, not a neutral one.

The pattern, same as every Param node

This pack's whole trick is that the node title becomes the API parameter name. Right-click → Title, rename it to something like use_lora, save the workflow in API format, and your backend overwrites inputs.value for this node's class_type before queueing. Your request payload gets a clean boolean field and the graph gets its decision. The checkbox on screen is just the default value the API can override.

One thing this node is not: a bypass or mute. It emits a boolean that downstream logic consumes. Whether anything actually gets skipped depends on the nodes you wire it into - a boolean into a switch routes data; it doesn't stop the graph from computing the unselected branch (worth rereading in the HelperModelSwitch article if that matters to you).

Install

cd ComfyUI/custom_nodes
git clone https://github.com/FaraamFide/ComfyUI-ParamNodes.git

Restart ComfyUI, or install via ComfyUI Manager by searching "ComfyUI-ParamNodes". No dependencies, no models. It shows up under Params/Input in the Add Node menu.

It's a checkbox with a wire. For API-driven workflows, that checkbox is how a backend says yes or no.