CFE Flux Out Pipe
Unzipping a FLUX_PIPE when you finally need the parts
- pipe
- pipe
- model
- clip
- vae
- cond
- sampler
- scheduler
CFE Flux Out Pipe is the mirror image of its sibling CFE Flux In Pipe: it takes one FLUX_PIPE wire and unpacks it back into the six individual signals that went in. In, out, done. It exists so the middle of a Flux workflow can be one tidy bus line and the ends can still be ordinary nodes.
Why would you bother? Because a pipe is great for the middle of a graph, but terrible at the edges. A bundled wire is opaque - you can't VAE-decode a tuple, you can't reroute one field of it, you can't swap the conditioning without unwrapping. When the pipe line ends and you need actual MODEL, CONDITIONING, and VAE ports to hand off to stock nodes, this is the node that does the unzipping.
How it works
The mechanism is a straight unpack. The pipe is a Python tuple in a known order - (model, clip, vae, cond, sampler, scheduler) - and the node pulls it apart:
model, clip, vae, cond, sampler, scheduler = pipe
return (pipe, model, clip, vae, cond, sampler, scheduler)
The first output re-emits the whole pipe unchanged, so you can tap the individual parts without consuming the bus. That's the detail that makes it a useful branch point: one CFE Flux Out Pipe can simultaneously feed a VAE Decode with the vae, a text node with the scheduler name, and pass the untouched pipe along to the next stage. Daub a CFE Flux In Pipe downstream and you've got a full detour off the main line.
The one input and the seven outputs
- pipe - required,
FLUX_PIPE. The bus you're unpacking. - Outputs, in order: pipe (passthrough), model, clip, vae, cond, scheduler (the string), and sampler (the SAMPLER object).
Note the scheduler output is a plain string - the same asymmetry this pack uses everywhere. If you grab that string, you can feed it into something that takes a scheduler name, like this pack's CFE FLUX Sampler (Pipe) or a stock scheduler node.
Install and expectations
Same as the rest of the pack - zero dependencies, nothing to download:
cd ComfyUI/custom_nodes
git clone https://github.com/CpreForEver/CFE_comfyui
Restart ComfyUI, and it's in the CFE/flux menu section. Or install via ComfyUI Manager by searching CFE_comfyui.
Honest verdict: this is a utility node, and it's fine at what it does, but it's nothing you can't approximate by re-wiring. If you're not already running the pack's pipe system, you don't need it - the stock way to "bundle" wires in ComfyUI is the reroute node that ships in the box. Where it earns its keep is inside this pack's own convention: In Pipe → sampler → Out Pipe keeps a whole Flux graph readable, and this is the node that lets the bus touch normal ComfyUI at both ends. Just remember the same caveat that applies to the whole pack: it's a personal playground project, no guarantees, and if a "bus" turns into a maintenance headache, that's the author's honesty, not a sales pitch.
Inputs (1)
| Name | Type | Default | Description |
|---|---|---|---|
| pipe | FLUX_PIPE | The bus line carrying the data. |
Outputs (7)
| Name | Type | Description |
|---|---|---|
| pipe | FLUX_PIPE | — |
| model | MODEL | — |
| clip | CLIP | — |
| vae | VAE | — |
| cond | CONDITIONING | — |
| sampler | SAMPLER | — |
| scheduler | STRING | — |