Nodes/ComfyUI-ArchAi3d-Qwen/✅ Boolean Input
ComfyUI Node

✅ Boolean Input

A toggle you can name — the forgotten simplest node

By amir84ferdos·Created 11 months ago·Updated 5 months ago· 70
✅ Boolean Input
    • BOOLEAN
    namebool_input
    valuefalse

    A boolean input that outputs a BOOLEAN. That's the whole node. It exists because of the pack's web-interface integration: ComfyUI's built-in primitives don't carry a name for a frontend to render a labeled form field against, and this one does. In the default desktop UI it's just a checkbox you can drag anywhere; in the pack's hosted/API frontend, the name field becomes the label of a real form control that sets this value.

    Inputs: name (default bool_input - the identifier the web interface uses) and value (the boolean, default false). One output: BOOLEAN, carrying exactly the value you set. There is no computation, no state, no side effect. It's a wire-to-a-constant.

    Where it fits

    These named input nodes (String, Int, Float, and this one) are a family designed for one scenario: a ComfyUI workflow exposed through a web form or API where the end user shouldn't see the graph - they just flip "Enable upscale" and the graph runs. If you're building that kind of hosted setup, this is how you surface a toggle cleanly. If you're a desktop user, the built-in primitive node does the same job and you'll never touch this one.

    Installation

    It's part of ComfyUI-ArchAi3d-Qwen. ComfyUI Manager ("ArchAi3d Qwen") or:

    cd ComfyUI/custom_nodes/
    git clone https://github.com/amir84ferdos/ComfyUI-ArchAi3d-Qwen.git
    cd ComfyUI-ArchAi3d-Qwen
    pip install -r requirements.txt
    

    Restart, look under ArchAi3d/Inputs. Free personal use, paid commercial license (the pack's usual dual-license deal).

    Where people get burned

    Honestly, the main trap is expecting more. It outputs a bare BOOLEAN, which most of ComfyUI's node inputs (especially older ones) aren't typed to accept directly - they want an INT 0/1. If a node won't accept the wire, check its input type: BOOLEAN ≠ INT, and you may need a small converter node between them. And because the pack registers a whole family of these named inputs, don't confuse name (the frontend label) with value (the data) - renaming doesn't change what's output. If you just want a checkbox that outputs 0/1 into an INT input, the stock primitives are the smoother path.

    CategoryArchAi3d/Inputs

    Inputs (2)

    NameTypeDefaultDescription
    nameSTRINGbool_inputIdentifier name for this input (used by web interface)
    valueBOOLEANfalseThe boolean value to output

    Outputs (1)

    NameTypeDescription
    BOOLEANBOOLEAN