Ino Condition Boolean

If you've ever wanted a workflow to only run when two conditions are true - "the model downloaded AND the batch isn't empty" - you've needed this node. Ino Condition Boolean combines two booleans with AND or OR and outputs the result. The description: "Performs AND or OR operation on two boolean values."

It's the boolean glue for the pack's logic family, slotting right next to InoBooleanEqual (equality) and InoCompareInt (integer comparison). Where those test, this combines.

How it works

Three inputs: a condition combo (AND or OR) and two booleans, bool_1 and bool_2, both defaulting to true. AND returns true only when both are true; OR returns true when either is. Pick the operator, feed in the flags, and the BOOLEAN output tells you whether the gate is open. It's pure, instant logic - no state, no surprises.

Inputs and outputs

• condition - AND or OR. This is the whole point of the node, so get it right: AND is the stricter gate.
• bool_1 / bool_2 - the two conditions to combine.

Output: BOOLEAN - the combined result.

Where it wires in

Gating multi-condition branches. A download succeeds AND a file exists → proceed. The batch is empty OR the node is disabled → skip. Wire the booleans out of success outputs (the pack's file nodes all expose one) or comparison nodes, run them through this, and feed the result into a switch or an enabled toggle. That's how you build real if-logic out of the graph.

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

Like its siblings, the failure mode is type purity: it needs real booleans. A string "true" or an int 1 from another node will not combine the way you expect - cast first. And the classic logic-vs-English trap: "OR" in workflows is usually what people actually want when they say "I want to skip if either thing is true" - if you wired AND and your branch never fires, that's not a bug, that's AND being AND. When in doubt, reach for the one that lets the action happen.