Nodes/PixelML ComfyUI Nodes/BooleanInput_PixelML
ComfyUI Node

BooleanInput_PixelML

A named boolean toggle — the simplest node in the pack, and that's fine

By PixelML·Created 2 years ago·Updated 2 years ago· 0
BooleanInput_PixelML
    • BOOLEAN
    namebool_input
    valuefalse

    BooleanInput_PixelML is a checkbox on a wire. It takes a value toggle, a name label, and outputs a BOOLEAN - nothing more, nothing less. There's no parsing, no clamping, no fallback logic, because a boolean doesn't need any. In a pack whose other inputs exist to rescue values that arrive as unreliable text, this one just passes a toggle through.

    That makes it the rare node you can fully understand in ten seconds. Whether it's worth installing for is a different question - core ComfyUI already gives you boolean primitives by converting a toggle widget to an input, and this node doesn't add mechanics. What it does add is the name field: a label attached to the value so an automated or agentic workflow can tell which "flag" a toggle represents when it's inspecting the graph. If you're hand-building workflows, that's cosmetic. If something is driving your graph programmatically, it's the difference between a named signal and an anonymous wire.

    It comes from PixelML ComfyUI Nodes, a small pack centered on variable handling and workflow automation. This is the simplest member of the family.

    How it works

    The entire implementation is a pass-through: get_value returns the value you set. There's no conversion, no fallback, no edge cases. Set the toggle on and the output is True; flip it off and you get False. About the only subtlety is that it's a genuine BOOLEAN type - a True/False, not a string "true" or an integer 1 - so it plugs directly into boolean inputs on other nodes without needing a converter in between.

    The inputs

    • name (STRING, default "bool_input") - a label. It does not affect the output.
    • value (BOOLEAN, default false) - the toggle itself. This is the one you flip.

    The single BOOLEAN output wires into any node that takes a boolean: an enabled/disabled switch, a conditional routing node, a "use face detailer or not" gate.

    Install

    ComfyUI Manager is the easy route - search "PixelML ComfyUI Nodes" and install, then restart. By hand:

    cd ComfyUI/custom_nodes
    git clone https://github.com/PixelML/ComfyUI-PixelML-CustomNodes
    

    Restart and the node appears under the pack. One heads-up, same as every node in this pack: requirements.txt pins diffusers==0.24.0 and lists boto3/httpx/httpx-sse, but the shipped code never imports them. If Manager's install drags diffusers down and breaks other nodes, ignore the requirements file - a boolean pass-through needs nothing beyond what ComfyUI already bundles. The README's dependency list simply rotted behind the code.

    Honest take: if you only need a toggle, use the core boolean primitive and skip this pack entirely. Pick BooleanInput_PixelML when you want the label - which, in an agent-driven workflow, can genuinely matter.

    Categorysd

    Inputs (2)

    NameTypeDefaultDescription
    nameSTRINGbool_input
    valueBOOLEANfalse

    Outputs (1)

    NameTypeDescription
    BOOLEANBOOLEAN