If Branch Router

ComfyUI is a graph, but "make a choice inside the graph" has always been the awkward part. The stock answer is a pile of Primitive boolean nodes and mask arithmetic, or leaving ten alternative paths wired in and hoping the model you didn't pick doesn't blow up. This node is the cleaner version: one input, up to 32 if == value branches, and a guaranteed fallback output. Feed it an INT or STRING, and it routes to exactly one output - the rest come back as ExecutionBlocker, which tells ComfyUI to skip those paths entirely.

That last bit is the whole trick. A node whose unselected outputs block execution isn't just cosmetic tidiness; the branches you don't hit literally never run. No wasted sampler steps, no missing-node errors from a path that should have been dead. It's the difference between a switch statement and a stack of ifs where every branch executes and you patch over the results.

How it works

Under the hood it's dead simple. The route() function parses your condition list from a hidden JSON field, compares condition against each entry in order, and the first match wins. It then builds all 33 outputs - if_1 through if_32 plus otherwise - sets the one selected output to your payload, and fills every other slot with an ExecutionBlocker. ComfyUI's executor sees that blocker and skips everything downstream of it. No requirements.txt, no models, nothing but the core comfy_execution.graph module that ships with ComfyUI.

The inputs that actually matter

• condition (INT or STRING) - the value being tested. Feed it a prompt, an INT you got from elsewhere, whatever.
• compare_as - AUTO does integer comparison when both sides look like integers, and string comparison otherwise. INT and STRING force a mode. Leave it on AUTO until you hit an edge case.
• conditions_json - the list of expected values, like ["0", "1", "cat"]. The frontend hides this and edits it for you; you only touch it if the JS didn't load.
• string_trim and case_sensitive - string-matching hygiene. Trim is off by default, so "cat" won't match " cat " until you flip it.
• passthrough (optional, any type) - the thing you actually want the chosen branch to receive. This is the important one: if you don't connect it, the selected output just emits condition itself. If you want an IMAGE, LATENT, MODEL, or CONDITIONING to flow down the chosen path, that goes in passthrough.

The UI relabels outputs to if == 0, if == 1, and so on, with the last one named 否则 - the author's Chinese for "otherwise". Cosmetic, but worth knowing so you don't think your ComfyUI is glitching.

Installation

ComfyUI Manager, search "ComfyUI-IfBranchRouter", install, restart. Or the manual route:

cd ComfyUI/custom_nodes
git clone https://github.com/Lingyuuuux/ComfyUI-IfBranchRouter

Then restart ComfyUI. That's it - no pip install step, no model downloads, nothing to break your existing environment. Given the dependency-hell reputation most custom nodes carry (see the ecosystem doc on why transformers version wars eat weekends), a zero-dependency logic node is refreshing.

Where people get burned

• Order matters. First match wins, so put the most specific condition first.
• AUTO mode and "10.0": a string like 10.5 won't match an int branch, but 10.0 and "10" will. It parses floats that happen to be whole numbers.
• The 32-branch cap is a hard ceiling; hit the "add" button past it and nothing happens.
• If the workflow loads but the outputs are all if_1…if_32 instead of labels, the frontend JS didn't load. Edit conditions_json by hand - the format is just a JSON array.

Reach for this when you want one workflow to behave like several: a mode selector for SDXL vs. Flux, routing a prompt down a video path or an image path, A/B-ing samplers. It's a small node, but it's the kind of small node that makes big workflows actually maintainable.