Op. To Basic Pipe

This node bundles a model, CLIP, VAE, and positive/negative conditioning into a single BASIC_PIPE wire - and every input is optional. It's the pack's own pipe constructor, the node you use to start building a pipe-based workflow so all those connections travel down one cable instead of five.

Why you'd reach for it

BASIC_PIPE is the de-facto standard bundle in ComfyUI - Impact Pack introduced it, and a whole class of nodes (including this pack's own pipe samplers) read model/CLIP/VAE/conditioning out of one. To use those, you first have to make a pipe. That's this node's job. Wire your checkpoint's model, CLIP, and VAE plus your two conditionings in, and it emits a BASIC_PIPE you can route anywhere.

The "optional" in the name is the real feature. Impact Pack's own ToBasicPipe wants everything. This one lets you build a partial pipe - say, model and VAE now, conditioning added later downstream with a node like this pack's Concat Conditioning (PIPE) or Bus Pipe. That flexibility matters when you're assembling a pipe in stages, or when a branch genuinely doesn't have a value for every slot yet. It's the low-friction on-ramp to pipe-based building.

How it works

It takes whatever inputs you connect and packs them into a BASIC_PIPE in the standard slot order (model, CLIP, VAE, positive, negative). Slots you leave unconnected are simply empty in the resulting pipe - no error, no placeholder you have to supply. The output is a normal BASIC_PIPE, interoperable with Impact Pack's pipe nodes and this pack's pipe samplers alike.

The inputs and outputs

All inputs are optional:

• model - a MODEL.
• clip - a CLIP.
• vae - a VAE.
• positive / negative - CONDITIONING.

The single output is pipe, a BASIC_PIPE carrying whatever you connected.

Installing it

ComfyUI Manager → search antrobots ComfyUI Nodepack, install, restart. Or:

cd ComfyUI/custom_nodes
git clone https://github.com/antrobot1234/antrobots-comfyUI-nodepack

No downloads. Because it produces the standard BASIC_PIPE, it plays nicely with Impact Pack if you have it, but it doesn't require it.

Common issues

The trap with optional slots is building an incomplete pipe by accident, then feeding it to a node that needs the missing piece. A sampler pulling model out of your pipe will fail if you never connected the model - and the error surfaces at the sampler, not here, which can be confusing. If a downstream pipe node complains about a missing value, trace back and check this constructor actually has that slot wired.

Second, order and completeness matter when a consumer expects a full pipe. If you're handing this straight to a pipe sampler, populate all five slots (or fill the gaps downstream with a Bus Pipe / conditioning-concat node) so nothing arrives empty.

Otherwise it's a clean, dependable little builder - the natural first node in any pipe workflow you assemble with this pack.