Any to Pipe

Every large ComfyUI workflow eventually hits the same wall: wires. By the time you've got a model, a VAE, two conditionings and a seed all needing to cross the same stretch of canvas, the graph looks like spaghetti. This vsLinx node is the pack's answer - a single pipe output that bundles up to five values of any type into one connection. Pair it with its sibling Pipe to Any and you can route a whole bundle of unrelated values across the graph as one clean wire.

How it works

The five inputs (slot_1 through slot_5) are all optional and all any-typed. Leave a slot unconnected and you just don't use it - you can pack one value or five. Position is the contract: whatever goes into slot_2 here comes out of slot_2 on the receiving Pipe to Any, no labels, no magic. That positional rule is the one thing to remember when you're designing a bundle.

The pipe type is VSLINX_PIPE, so it's a real typed connection, not a hack. And it composes with the rest of the pack: the bypass/mute forward nodes are pipe-aware, meaning bypassing a branch still correctly propagates through an Any to Pipe → Pipe to Any chain to the real downstream nodes, and boolean values routed through a pipe resolve at the right slot instead of scanning everything.

Inputs and outputs

• slot_1 … slot_5 - all optional, all any-type.
• Output: pipe (VSLINX_PIPE).

Five optional inputs, one output, no widgets to set.

When to reach for it

• A sampler's inputs live on one side of the canvas and its loaders on the other - pack model/VAE/conditionings once, drag one pipe over.
• You're building a reusable subgraph and want a tidy single "inputs" port.
• Decluttering a workflow you're about to share, where readability matters more than the four pixels of wire you saved.

It's the same instinct as rgthree's Context nodes, just with a plain any-type bundle instead of named slots - simpler, and fine for most "these five things travel together" cases.

Install

Part of the vsLinx pack. ComfyUI Manager → search "ComfyUI vsLinx Nodes", or:

cd ComfyUI/custom_nodes
git clone https://github.com/vslinx/ComfyUI-vslinx-nodes.git comfyui-vslinx-nodes

Restart, look under vsLinx/utility. No extra dependencies.

The honest take

It's pure housekeeping - if you never build a graph big enough to tangle, skip it. If you do, it's one of those "why didn't I do this sooner" nodes. The one trap is the positional contract: reorder what you pack and you must reorder what you unpack, or a model quietly lands in a conditioning slot. Keep the same slot map across the pair and it's genuinely zero-friction. Worth noting it pairs naturally with the boolean and bypass utilities in the same pack - bundle your state with your data and a big graph starts to behave like a small one.