SP Any Pipe [40 Ports]

Forty ports is big-workflow territory - the size you reach for when a single graph is doing enough that it effectively needs a "master settings" bundle: this pack even ships a dedicated ParameterControlPanel node for exactly that pattern, and a 40-port Any Pipe is the kind of wire you'd use to carry that panel's output somewhere it's actually consumed. If you're still counting how many things you're bundling, you probably don't need this size yet - 20 or 30 ports covers most real workflows. Forty is for the graphs that have genuinely outgrown that.

The mechanism is identical across every size this pack ships (5/20/30/40/50): bundle a pile of arbitrary values into one wire instead of routing each individually. It's the same idea as rgthree's Context node or Impact Pack's basic pipes, just scaled up for a workflow with a lot more moving parts.

How it works

Every any_N_in socket takes ComfyUI's wildcard * type - a MODEL in slot 1, a STRING in slot 2, a FLOAT in slot 3, no complaints. Each any_N_out re-emits exactly what came in on the matching input, unchanged, in order. The exception is cpipe_in/cpipe_out, typed sp_anypipe specifically - that pair only accepts another Any Pipe's output, and it's how you chain nodes together if even forty ports isn't enough, or how you'd link this pipe as one stage of a longer pipeline of pipes.

Inputs and outputs

• any_1_in through any_40_in - forty optional wildcard inputs.
• cpipe_in - optional, sp_anypipe, chains in a prior pipe.
• Outputs: any_1_out through any_40_out, plus cpipe_out.

Every slot is optional - an empty input just produces an empty output.

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 ComfyUI. It's plain Python plumbing - nothing to download, no extra pip requirements specific to this node.

Common issues

A 40-port node is a big rectangle. At this size the node itself takes up real canvas space just listing sockets, most of which will sit empty in any given workflow. That's a fair trade if you genuinely need the ports, but if you're consistently using under half of them, dropping to 20 or 30 keeps the graph more readable without losing any capability.

Type errors surface far from their cause. Because every port is wildcard-typed, ComfyUI validates nothing about what's actually flowing through until a downstream node tries to use it - and with forty slots the odds of one being wired to the wrong thing go up. When something errors well past a big pipe, trace back through it before trusting the node that actually threw the error.

Losing track of which slot is which. Forty unlabeled index numbers is not a filing system. Group related ports into consistent ranges (settings in 1-10, conditionings in 11-20, and so on) and rename the node itself to say what it's carrying - the alternative is re-deriving your own workflow from scratch every time you reopen it.