Nodes/Crystools/πŸͺ› Primitive boolean
ComfyUI Node Runs on cloud

πŸͺ› Primitive boolean

Primitive Boolean (Crystools)

By crystianΒ·Created 3 years agoΒ·Updated 9 months agoΒ· 1,940
πŸͺ› Primitive boolean
    • boolean
    β—„booleantrueβ–Ί

    The simplest node in the entire pack: one checkbox, one BOOLEAN output, default on. There's nothing else to it.

    Why you'd reach for it

    This is the node you plug into every one of Crystools' own switch nodes - Switch image, Switch string, Switch any, Switch conditioning - when you want the toggle itself to be a visible, reusable value rather than a raw True/False buried inside each switch's own widget. Wire one Primitive boolean into several switches at once and you've built a single master toggle that flips all of them together, instead of clicking through each switch individually.

    Worth knowing if you've used other utility packs: Crystools takes a different design stance than something like rgthree's Power Primitive, which is one node whose type you switch between STRING/INT/FLOAT/BOOLEAN from a menu. Crystools instead gives you a separate node per type - this one, Primitive integer, Primitive float, Primitive string, and Primitive string multiline - so you commit to the shape up front rather than reconfiguring one node later. Neither approach is wrong; it's just worth knowing which pack's convention you're following if you're mixing both in one graph.

    How it works

    A widget and an output - set the checkbox, get that value out.

    Inputs and outputs

    One required field: boolean (default true). One output: boolean. No hidden options, no advanced mode - it's exactly as simple as it looks.

    Installing it

    Nothing special required for this node beyond having the pack installed at all. Through ComfyUI Manager, search crystools. Manually:

    cd ComfyUI/custom_nodes
    git clone https://github.com/crystian/ComfyUI-Crystools.git
    cd ComfyUI-Crystools
    pip install -r requirements.txt
    

    Restart ComfyUI. No models, no extra dependencies for this node.

    Common issues

    Genuinely nothing to troubleshoot here - it's a checkbox. The only thing worth keeping straight is which state maps to which branch on whatever switch you're feeding it into: true routes to on_true, false to on_false, and that mapping is consistent across every switch node in the pack, so once you learn it here it holds everywhere else.

    If you're chaining several switches off one Primitive boolean and something isn't flipping the way you expect, the boolean value itself is the first thing to check with Show any - connect it in alongside your switches and confirm the value actually is what you think it is before assuming any of the downstream switches are misbehaving. Nine times out of ten a "broken switch" turns out to be a boolean that never got wired the way you thought it was.

    Categorycrystools πŸͺ›/Primitive

    Inputs (1)

    NameTypeDefaultDescription
    booleanBOOLEANtrueβ€”

    Outputs (1)

    NameTypeDescription
    booleanBOOLEANβ€”