Nodes/CRT-Nodes/Any Trigger (CRT)
ComfyUI Node

Any Trigger (CRT)

Turn 'something is plugged in' into a boolean

By PGCRT·Created 2 years ago·Updated 7 days ago· 129
Any Trigger (CRT)
  • any_input
  • boolean

This is about as small as a node gets: one wildcard input, one boolean output. But small nodes like this are the connective tissue that makes conditional graphs actually work, and Any Trigger exists to solve a specific annoyance - you often want to gate a downstream branch on "did this thing produce anything at all," regardless of what type that thing is.

What it's for

ComfyUI's type system is normally strict: an IMAGE output only plugs into an IMAGE input, a STRING into a STRING. The * (wildcard/any) type is the escape hatch a handful of logic nodes use to accept literally anything - a common pattern for switches, bypassers, and "is this branch active" checks (you'll see the same trick elsewhere in this pack and in other logic-node suites). Any Trigger takes that wildcard input and turns it into a plain BOOLEAN, which you can then wire into whatever condition-gated node you're using - an AnyTrigger-style switch, a fast bypasser, a conditional loader.

The practical use case: you have an optional branch of your graph (maybe an upscale pass, maybe an extra ControlNet) that only sometimes has something connected to it. Rather than hand-toggling a boolean widget every time you rewire the graph, you feed whatever that branch's output would be into Any Trigger, and let it report back whether something is actually there.

The inputs and outputs that matter

There's only one field, and it's optional:

  • any_input - a wildcard (*) socket. Accepts a connection from literally any output type.

Output: boolean - BOOLEAN type.

The schema doesn't give a tooltip explaining the exact truthiness rule (does an empty string count as "nothing," does a zero-valued int still trigger true, and so on), so treat the mapping as "is something connected and did it produce a value" rather than assuming it inspects the payload's content. If you need finer logic than presence/absence, you'll want a type-specific comparison node instead.

Installing it

Any Trigger is one of three nodes in CRT-Nodes' CRT/Logic category (alongside Boolean Invert and Strength to Steps), part of the larger CRT-Nodes suite by PGCRT (CRYPT_EXE).

ComfyUI Manager - search CRT-Nodes, install, restart.

Manual:

cd ComfyUI/custom_nodes
git clone https://github.com/PGCRT/CRT-Nodes.git
pip install -r requirements.txt

Restart ComfyUI. No extra downloads or heavy dependencies needed for this specific node - it's pure graph logic.

Common issues

  • Wildcard sockets sometimes fight ComfyUI's link validation. If you're re-wiring a graph and a link into any_input silently refuses to connect or shows as red, try connecting it fresh rather than dragging an existing wire - wildcard-typed inputs are occasionally finicky about accepting a rewired link versus a brand-new one, which is a known quirk of ComfyUI's wildcard type handling generally, not specific to this node.
  • If the pack fails to load entirely, check the console for an import error elsewhere in CRT-Nodes - this node has no optional dependencies of its own, so a missing-node problem here almost always traces back to something else in the pack failing to import (CRT-Nodes is written to keep loading and just drop the affected nodes when an optional import fails, so a partial install is common and usually harmless for nodes like this one).
  • Don't expect content-aware logic. This node answers "is anything here," not "is the value meaningfully non-empty." For example a connected STRING output holding "" may still read as present. If your gate needs to check for an actually-empty string or a specific value, pair this with a proper comparison node instead of relying on Any Trigger alone.
CategoryCRT/Logic

Inputs (1)

NameTypeDefaultDescription
any_inputopt*

Outputs (1)

NameTypeDescription
booleanBOOLEAN