Nodes/ComfyUI Ino Nodes/Ino Boolean Equal
ComfyUI Node

Ino Boolean Equal

Are these two booleans the same? The one-question logic node

By nobandegani·Created about a year ago·Updated 2 months ago· 6
Ino Boolean Equal
    • BOOLEAN
    inputtrue
    comparetrue

    Sometimes a node is exactly one question. Ino Boolean Equal asks it: are these two booleans equal? Take input and compare, and it outputs true when they match. That's the entire node - the description doesn't even try to dress it up: "Checks if two boolean values are equal."

    It's the boolean sibling of InoCompareInt (equality for ints) and InoConditionBoolean (AND/OR for bools). If you're building any kind of logic into a workflow, these three little nodes are your vocabulary.

    How it works

    Two boolean inputs, input and compare, both defaulting to true. It returns True when both are the same (both true or both false) and False when they differ. No state, no side effects, no async - instant, and safe to drop anywhere in the graph. The single output is named BOOLEAN.

    Inputs and outputs

    • input - the boolean you're testing (default true).
    • compare - the boolean you're comparing against (default true).

    Output: BOOLEAN - true when equal.

    Where it wires in

    Consistency checks and gating. Two settings that should agree - say, a master "enable LoRA" flag and a per-node toggle - feed them in here and you can verify they match or branch when they don't. Wire the output into a switch node or a conditional path and you've turned "these two flags agree" into an action. It's the kind of node you don't reach for until you need it, and then it's exactly right.

    Installing it

    Part of ComfyUI-InoNodes. ComfyUI Manager → search "ComfyUI Ino Nodes" → install → restart. Manual:

    cd ComfyUI/custom_nodes
    git clone https://github.com/nobandegani/ComfyUI-InoNodes
    cd comfyui_ino_nodes
    pip install -r requirements.txt
    

    Restart after. No keys, no models.

    Common issues

    The only way to trip this up is to feed it non-booleans. Some nodes output "true"/"false" as strings or 1/0 as ints, and comparing those against a real boolean won't behave the way you'd like - cast through the pack's InoCastAnyToInt or InoCastAnyToString first, or just know what your inputs are. That's genuinely the whole failure surface. If you're used to the = operator in InoCompareInt, note this is the dedicated boolean form - use whichever matches your input types.

    CategoryInoBoolHelper

    Inputs (2)

    NameTypeDefaultDescription
    inputBOOLEANtrue
    compareBOOLEANtrue

    Outputs (1)

    NameTypeDescription
    BOOLEANBOOLEAN