Reroute Triggerable

ComfyUI's built-in Reroute is one of those nodes you stop noticing because it's everywhere - a wire with a label that keeps your graph readable. Reroute Triggerable is a reroute, and then something more: it's a reroute that ComfyUI treats as triggerable, so it can participate in the graph's execution flow instead of being a passive wire.

What the author's README actually claims: "It enables a leaf node such as 'image preview' to not be a leaf anymore if connected." Translation: a preview node sitting at the end of a branch gets treated as a terminal - ComfyUI considers it an output and schedules it accordingly, which can interfere when you're trying to control when that preview refreshes. Slip a triggerable reroute into that branch and the execution ordering changes - the node can be gated and scheduled as part of your flow rather than firing the moment its input is ready. If you're chasing the "my previews compute at the wrong time / my workflow ends too early" class of problems, that's the fix it's aiming at.

How it works

Mechanically it's the simplest node in the pack: value in, the same value out, unchanged. The interesting part is the type plumbing. Like the rest of this pack it uses a wildcard AnyType, so it accepts literally any input type, and its VALIDATE_INPUTS always returns true - meaning it will never reject a connection the way a typed node would. The "triggerable" half is delivered through ComfyUI's advanced Mode > OnTrigger UI: because the node is marked triggerable, you get that mode on its context menu, and the reroute can then wait on a trigger instead of passing through immediately. It's the routing version of the sequencing tricks the pack's Wait nodes do with lazy inputs.

Inputs and outputs

• value (required, any type) - whatever you want rerouted.
• * (output, any type) - the same value, unchanged.

One input, one output, zero configuration. If you don't use the OnTrigger mode, it behaves like a plain reroute with slightly worse ergonomics (no sizing/labeling niceties beyond what ComfyUI gives any node) - so the value only shows up if you're actually building triggered flows.

Honest positioning

This is the pack's odd one out, and it shows. It's listed with the experimental nodes, its effect depends on ComfyUI frontend features that have been in flux (Nodes 2.0 reshuffled how some nodes render and trigger), and most workflows simply don't need it - a standard reroute does the pass-through job fine. Reach for it specifically when you've identified a leaf-node-execution-timing problem and you want a reroute that carries trigger semantics. Otherwise, plain Reroute is usually the right tool.

Install

Part of lokinou/comfyui-better-flow. Via ComfyUI Manager, search "comfyui-better-flow", or:

cd ComfyUI/custom_nodes
git clone https://github.com/lokinou/comfyui-better-flow.git

Restart ComfyUI fully - a real restart, not just Reload - so the node registers. No pip step, no model downloads; the pack is dependency-free.

One thing to watch

Because it's a wildcard node that accepts anything, it inherits the ecosystem's classic warning about anything-goes routing: it's convenient, but every any-type connection is one more place a workflow can silently do something unexpected. If you're sharing workflows, prefer typed reroutes where possible and keep this one for the cases where triggerability is the actual point.