Pipe Out

Pipe Out is the mirror image of Pipe In: you feed it one bundled PIPE_LINE and it hands you every piece back out individually - model, conditioning, latent, VAE, CLIP, image, and the seed that was riding along inside the pipe. This is the node you reach for the moment you need to tap just one thing out of a pipe without dismantling the whole workflow.

Why this matters in practice. The point of Easy-Use's pipe pattern is fewer wires on screen - one PIPE_LINE instead of six separate connections. That's great until you hit a node that was never built to understand PIPE_LINE, like a third-party sampler, a custom VAE decode, or literally anything from a different node pack that only speaks the standard ComfyUI types. easy pipeOut is the adapter: drop it in, and suddenly you have plain MODEL, CONDITIONING, LATENT, VAE, CLIP and IMAGE sockets sitting right there to wire into whatever needs them.

Inputs and outputs. One required input - pipe. Nine outputs: pipe (passed straight through unchanged, so you can keep chaining pipe-based nodes after this one too), model, pos, neg, latent, vae, clip, image, and seed (an INT). That seed output is worth calling out - it's not something you set on this node, it's whatever seed value got baked into the pipe further upstream (typically from a loader or a presampling node), surfaced here so you can display it, reuse it in another sampler, or log it alongside your output for reproducibility.

This is also the node that makes the pipe pattern worth trusting in the first place. If bundling model, conditioning, latent, VAE, CLIP and image into one wire meant you were stuck with them bundled forever, most people would reasonably avoid it - nobody wants an all-or-nothing data structure sitting in the middle of their graph. Pipe Out is the guarantee that it isn't: at any point, for any reason, you can drop one in and get every individual piece back, fully compatible with plain ComfyUI nodes that have never heard of PIPE_LINE. That's what makes it safe to build most of a workflow in Easy-Use's pipe style and still freely mix in nodes from other packs wherever you need something the pipe ecosystem doesn't cover.

Install. Through ComfyUI Manager, search "ComfyUI Easy Use," or by hand:

cd ComfyUI/custom_nodes
git clone https://github.com/yolain/ComfyUI-Easy-Use

then restart. No extra dependencies beyond the base pack for this one.

Common issues. Same category of gotcha as the rest of the pipe family: if you pull vae or image out of a pipe that never had one populated, you'll get an empty/None value downstream, and the error will point at whatever node choked on it rather than at Pipe Out itself - so when something after a Pipe Out complains about a missing input, the actual bug is usually further back, at whichever pipeIn or loader built the pipe in the first place. One easy habit: since pipe passes through unchanged, it's safe to sprinkle Pipe Out nodes anywhere in a chain purely to peek at intermediate values (throw a Preview Image on the image output, or a display node on seed) without disturbing the rest of the graph - it's a non-destructive tap, not a consuming one.