PipePass
The pass-through for Impact Pack pipes that keeps graphs tidy
- PIPE_LINE
- PIPE_LINE
PipePass takes a PIPE_LINE and hands it back unchanged. Like the pack's other pass nodes (IntPass, LatentPass, SEGSPass), it does zero processing - it's pure graph hygiene for the Impact Pack's pipe type, which is the bundled-bag object that carries model, clip, vae, conditioning, latent, and a pile of extra fields down a single wire.
Why you'd bother
Impact Pack pipes are the classic case where a pass node earns its keep. A PIPE_LINE bundle is convenient until you need to tap one field, and then you're juggling Pipe Edit and Pipe to Anything nodes and suddenly the wire is crossing the entire canvas again. A pass node gives you a labeled waypoint - a clean place to split, route, or park the bundle - without touching its contents.
In the Flux Continuum workflow specifically, these pass nodes are part of the modular plumbing that lets the front panel stay tidy while the back end does the heavy lifting. If you're rebuilding the workflow yourself, PipePass is what you'd reach for when a pipe needs to thread through a section without being consumed.
Inputs and outputs
- PIPE_LINE - one required pipe input.
Output is one PIPE_LINE, byte-for-byte what went in. No parameters, no options, no description in the schema (the node is as minimal as they come). If you need to actually inspect or modify the pipe's contents, this isn't the node - look for Impact Pack's pipe editing nodes instead.
Installing it
Ships in robertvoy/ComfyUI-Flux-Continuum:
cd ComfyUI/custom_nodes
git clone https://github.com/robertvoy/ComfyUI-Flux-Continuum
or ComfyUI Manager ("Flux Continuum"), restart. One note: the PIPE_LINE type itself comes from Impact Pack, so a workflow using PipePass meaningfully also wants Impact Pack installed - otherwise there's nothing to pass.
Honest take
You will almost certainly never add this node to a graph by hand. It exists so the Flux Continuum workflow's own structure stays modular, and it's there if you fork the workflow and need the same courtesy. That's fine. Utility nodes don't need to be exciting; they need to not break, and this one literally cannot.
Inputs (1)
| Name | Type | Default | Description |
|---|---|---|---|
| PIPE_LINE | PIPE_LINE | — |
Outputs (1)
| Name | Type | Description |
|---|---|---|
| PIPE_LINE | PIPE_LINE | — |