Any Match Router

ComfyUI has no switch statement - you get a wired graph, and every branch you build always runs. Any Match Router is the closest thing to switch (x) { case ... } in this pack: one input value, up to 64 outputs, and a match text box that decides which single output receives it. Everything else gets nothing.

How the routing actually works

The implementation is a short loop, and its three quirks are all visible in it:

result = [None] * self.MAX_OUTPUT_INDEX
for index in range(1, self.MAX_OUTPUT_INDEX + 1):
    text = str(kwargs.get(f"text_{index}", ""))
    if text and text == match:
        result[index - 1] = any
        break
return tuple(result)

Read that carefully, because it defines the node:

• It's plain string equality. Case-sensitive, whitespace-sensitive, whole-string. No substring matching, no regex, no wildcards and no fuzzy anything. Cat does not match cat, and a trailing space you didn't see will make you think the node is broken.
• An empty text field is skipped, and match is compared as-is. So an empty match matches nothing at all - every output comes back None. That's the single most common way to sit there wondering why nothing is flowing.
• The first match wins and the loop breaks. Duplicate words across two text fields are a bug, not a shortcut: index 1 gets the value and the later twin gets nothing.

The node's declared inputs are any (required, wildcard - the value being routed) and match (STRING, the word you're testing against), plus the optional text_1 … text_64 fields that label the destinations. The outputs are any_out_1 … any_out_64. Backend-side, all 64 outputs are returned every run, mostly as None; the frontend hides the ones you haven't named.

The slots build themselves

This is where the schema and the screen disagree. The 64 text fields and 64 outputs aren't all on screen: a small frontend extension ships with the pack (web/js/dynamic_selectors.js) and maintains them as you type. Fill the last visible text field and the next one appears; an output socket is created only when its text field has something in it.

Two consequences worth internalizing. An output exists because you named it - delete the text in text_5 and any_out_5 vanishes, taking its wire with it, so save before you clear. And the socket labels are purely cosmetic: the visible output type mirrors whatever you plugged into any for readability, but the backend still treats it as wildcard.

If the node shows up with one output and no extra text fields, the extension didn't load - restart ComfyUI and hard-reload the browser tab (Ctrl+Shift+R). If you've turned on Nodes 2.0, know that the Vue frontend has been breaking third-party extensions for months; the standing workaround is to leave it off.

What you'd actually use it for

The killer feature isn't that it routes - a switch does that - it's that the router is driven by data. match is a normal STRING widget, so you can convert it to an input and let an upstream string decide the path: feed it a keyword, a label, a name that falls out of your own pipeline, and the graph reorganizes itself without you touching a wire.

Kept as a widget it's still useful: a variant selector, where you flip a word instead of rewiring. Against its packmates - Any Switch is A/B, Any If Else picks between two values, this one is dispatch.

One caveat, since the plumbing layer has a small culture war about this: routing any type into any socket is what earned the "please stop using the Anything Anywhere extension" backlash. Wildcard wiring makes a graph work and makes it harder to debug. Use it for dispatch you understand.

Installing it

MIT, brand new (first commits September 2026), and zero Python dependencies - empty dependency list, no requirements.txt, nothing to pip. It publishes to the ComfyUI registry automatically, so Manager sees it.

Manager → search ComfyUI Useful Stuff Nodes → Install. Or:

cd ComfyUI/custom_nodes
git clone https://github.com/ArtemKo7v/ComfyUI-UsefulStuffNodes

Restart ComfyUI, then reload the browser page - for this node that's not optional, because the dynamic slots are frontend work.

Where it goes wrong

All outputs None. Either match is empty, nothing matches its exact text, or the case/whitespace differs. The node can't tell you which, because it deliberately does nothing when there's no match. Copy the word straight out of the text field into match to rule out invisible characters.

Downstream nodes erroring. Same mechanism as any switch: the losing outputs carry None, the nodes behind them still execute, and anything expecting a real image or latent complains - usually naming the innocent node, not this one.

Missing node on a borrowed workflow. The JSON stores ArtemKo7vUsefulStuffNodesAnyMatchRouter; expect the red box until you install the pack.

Verdict: this is the one worth installing the pack for. It's a string-keyed dispatcher with no dependencies and no model downloads, and if you run workflows in several variants it removes a class of manual rewiring you'd otherwise be doing at 2am.