ComfyUI Node

Boolean OR Any

One socket list for 'at least one of these is true'

By Stibo·Created 5 months ago·Updated 2 months ago· 9
Boolean OR Any
  • values
  • BOOLEAN

"Should this run if any of these four things is true?" That question comes up constantly once a workflow has a few optional inputs - a reference image, a mask, a user toggle, a cached result - and you want the downstream step to fire if any one of them shows up. Boolean OR Any is the auto-growing version of OR built exactly for that: one list of sockets, up to 16 of them, true out if at least one is true.

How it differs from the two-input version

The plain Boolean OR in this pack takes exactly two operands. Fine for one decision, annoying when you're combining a handful of conditions - you end up stacking OR after OR in a chain that's hard to read and easy to miswire. OR Any collapses that into a single node: connect booleans, get one answer. It's the OR sibling of the pack's Boolean AND All, and you'll probably end up using both - AND All for "everything ready," OR Any for "anything ready."

Behavior worth knowing

The values input auto-grows as you connect sockets, up to 16 boolean inputs, and the output is a single BOOLEAN. The tooltip spells out the two edge cases:

  • Any single true input makes the output true. That's the whole job.
  • With nothing connected, it returns false. Note the difference from AND All, which returns true when empty. An empty OR is false, and that's the sensible reading - an unconnected gate says "no condition met."

Both behaviors are worth internalizing before you wire a big graph, because empty-input semantics are exactly the kind of thing that produces a "why is this always off/on" debugging session at 2am.

The output plugs into anything boolean-taking: switch selectors, bypass toggles, enabled flags - the usual gang.

Where it shines

Fallback routing. "Use the mask if there is one, otherwise use the depth map, otherwise just run plain" is a three-way OR feeding a switch, and with this node it's one gate instead of a chain. Same for "skip the expensive pass unless any optional stage is active."

Install

Part of Nifty Nodes for ComfyUI. Manager: search "Nifty Nodes for ComfyUI" → Install → restart. Manual:

cd ComfyUI/custom_nodes
git clone https://github.com/Stibo/comfyui-nifty-nodes

Restart ComfyUI. Pure logic, no models, no dependencies. The pack is MIT-licensed and new-ish (v2.1.0, mid-2026), so keep it updated if a workflow references it and ComfyUI doesn't recognize the class.

Gotchas

Don't forget the empty-list edge case. If you pre-build the workflow with the list partially wired, a false output can be a silent "nothing connected yet" rather than a real condition. And as with every boolean in this pack, the output is a value, not an execution control - pair it with a lazy switch or bypass node if you want the unused branch to actually be skipped.

Categorynifty/logic

Inputs (1)

NameTypeDefaultDescription
valuesoptCOMFY_AUTOGROW_V3Returns True if at least one connected boolean input is True. Returns False if nothing is connected.

Outputs (1)

NameTypeDescription
BOOLEANBOOLEAN