SP Any Pipe [50 Ports]

Fifty ports is the ceiling - the largest of the five pipe sizes this pack ships, and realistically more than most workflows will ever fill. If you're reaching for this one, you're probably building something like a big all-in-one template: multiple checkpoints, several conditioning branches, an assortment of settings feeding a ParameterControlPanel-style control layer, all of it needing to cross the canvas as one bundle rather than fifty individual wires crossing every other connection you've already drawn. That's the whole point of the pipe family (5/20/30/40/50 ports) - the same trick as rgthree's Context node or Impact Pack's basic pipes, just at the extreme end here.

How it works

Every any_N_in socket is typed *, ComfyUI's wildcard - plug in a MODEL, a CLIP, a plain INT, whatever, and the graph editor won't stop you. Each matching any_N_out passes it straight back through, unchanged, in the same position. The cpipe_in/cpipe_out pair is the odd one out: typed sp_anypipe, not *, so it only accepts another Any Pipe node's output rather than an arbitrary value. That's for chaining - if even fifty ports isn't enough, or you'd rather compose two pipes than build one giant one, feed one pipe's cpipe_out into another's cpipe_in.

Inputs and outputs

• any_1_in through any_50_in - fifty optional wildcard inputs.
• cpipe_in - optional, sp_anypipe, for chaining a prior pipe.
• Outputs: any_1_out through any_50_out, plus cpipe_out.

All optional - nothing forces you to fill every socket.

Installing it

ComfyUI Manager - search "SP-Nodes", install, restart. Manually:

cd ComfyUI/custom_nodes
git clone https://github.com/bananasss00/ComfyUI-SP-Nodes

then restart. No model downloads, no dependencies specific to this node - it's organizational plumbing, nothing more.

Common issues

This is almost certainly more than you need. Fifty wildcard sockets on one node is a lot of surface area to scroll through, and most workflows top out well before that. Before reaching for the biggest pipe, check whether 20 or 30 actually covers what you're bundling - a smaller pipe you can see all of at once beats a huge one you have to scroll to audit.

Type errors show up nowhere near their cause. The wildcard typing that makes this node flexible also means ComfyUI validates nothing about what's actually in each slot until a downstream node chokes on it - and at fifty ports, one mis-wired slot is easy to lose track of. If a run fails with a type complaint downstream of a big pipe, work backward through the pipe before blaming the node that threw the error.

Fifty unlabeled ports is unmanageable without a system. At this size, treat port ranges like a schema you define once - models in 1-10, conditionings in 11-25, settings in 26-50, or whatever grouping fits your workflow - and rename the node to describe what it's carrying. Without that discipline, a 50-port pipe stops being an organizational tool and becomes its own source of confusion.