Multi Switch Select

A switch that routes one of ten inputs to one of ten outputs, controlled by a single integer. Sounds like a toy. It's not - this is one of those boring utility nodes that quietly unlocks "one workflow, ten variants" patterns, the same idea behind the selector nodes that power most of the popular big packs.

The setup: select is an integer from 1 to 10. Whatever you plug into input_<select> comes out of output_<select>, and every other output stays empty. So with select=3, the value on input_3 appears at output_3 and nothing else comes out. That's the entire mechanic.

The lazy evaluation bit

Here's where it stops being dumb: the inputs are lazy. ComfyUI only actually evaluates the branch you selected - the other nine inputs don't need to be connected, and if they are, they aren't computed unless chosen. That means you can hang expensive subgraphs off all ten inputs - ten different LoRA stacks, ten different prompts, ten different image pipelines - and only the selected one runs. A 10-way A/B test that costs the same as running one path. That's the real reason this node exists.

Inputs and outputs

• select - the integer that decides everything, 1-10.
• input_1 ... input_10 - any type (*), all optional, all lazy. Most nodes only show the ones you wire.
• output_1 ... output_10 - the chosen input appears on its matching output; the rest are empty.

A note on output: it's a routing node, not a merging one. It's designed so each selected value has its own dedicated output slot - handy when different branches feed different downstream chains. If you just want "pick one of N and send it down one wire," the pack's Any Switch Select (which also has a boolean form) is the lighter fit. This one shines when branches fan out to different targets.

Installing it

ComfyUI Manager, search "ComfyUI 1hewNodes", install, restart. Or:

cd ComfyUI/custom_nodes
git clone https://github.com/1hew/ComfyUI-1hewNodes

Restart after either. The pack's install is heavy (opencv, rembg, ultralytics...) but this node needs nothing beyond the core - pure routing logic.

Gotchas

Empty outputs are None, so if a downstream node chokes on None, guard it or only wire outputs you actually use. And remember the 1-based indexing - select=1 routes input_1, not the zero-th thing. It's the same off-by-one that trips people on the whole family of these selector nodes. Also worth knowing: select accepts any integer but clamps to 1-10, so a stray 0 silently becomes 1 instead of erroring - check your number if the output feels wrong.