XPipe

Big ComfyUI workflows die by a thousand wires. The fix the ecosystem settled on is bundling - carry a whole group of related values down one cable and unpack it at the other end, the way rgthree's Context nodes do. XPipe is this pack's take: a pipe-bundle node with up to 20 any-type slots, per-slot overrides, and a single bundle wire that carries both the data and the slot names. If you've ever tried to move a dozen settings from a control section to a sampler section and watched the canvas turn into a spiderweb, this is the node that collapses that spiderweb into one line.

How it works

Each of the 20 slots (value_1 … value_20) is a MatchType input/output pair, so slot 3 can carry an IMAGE while slot 7 carries a FLOAT - every slot independently conforms to whatever you connect. The bundle wire is the xpipe_in / xpipe_out pair using the pack's custom xpipe type. Connect one XPipe's xpipe_out to another's xpipe_in and the entire group of values plus their names travels as one bundle.

The merge logic is where it gets useful. When a slot has its own input connected, that value overrides whatever came in the bundle at that position; when a slot is empty, it falls back to the bundle's value. So you can chain two XPipes and surgically override just the slots you care about at each stage, which makes it a building block for "config here, override there" workflows. The bundle format is a simple dict tagged __xpipe_bundle__ with a version number, so the node can detect a real bundle vs. garbage on the input.

Port names are customizable - you give slot 5 the name "seed" and slot 12 "cfg" and those names travel in the bundle, so downstream nodes and panels know what each value means without you memorizing positions. The names live in port_names, a serialized JSON string that the XPipe naming panel manages. The tooltip is blunt: don't edit it by hand.

Inputs that matter

• xpipe_in - the upstream bundle.
• value_1 … value_20 - the individual slots; a connected value overrides the bundle at that position.
• port_names - the slot-name JSON, managed by the panel.

Outputs: xpipe_out (the new bundle) plus value_1 … value_20 (the merged values, so you can unpack at the far end or tap individual slots).

Installing it

Part of ComfyUI-Xz3r0-Nodes. ComfyUI Manager: search ComfyUI-Xz3r0-Nodes, or:

cd ComfyUI/custom_nodes
git clone https://github.com/Xz3r0-M/ComfyUI-Xz3r0-Nodes.git
cd ComfyUI-Xz3r0-Nodes
pip install -r requirements.txt

Restart ComfyUI. No extra dependencies.

Gotchas

The author is refreshingly honest here: in the changelog they admit the current interface is a compromise - ComfyUI's frontend constraints forced a less slick design than they wanted, with some efficiency loss in the UI. So expect the naming panel to feel a little clunky; the data machinery is solid, the polish is the trade-off. Second, keep a mental model of the override rule: a connected slot always beats the bundle, so if you're debugging "why isn't my override applying," it's usually the reverse - a leftover connection is overriding the bundle. And 20 slots is a lot of ports on one node; on a small canvas it's visually dense, so the bundle wire is really the way to use it end-to-end. If you just need three wires grouped, rgthree's Context might be lighter; at ten-plus values, XPipe's flat slot model shines.