Pipe In(pipeIn)

Description

The Pipe In node combines the individual components of a generation workflow into a single PIPE_LINE, making them easy to pass between Easy-Use nodes. It can be used to create a new pipeline from scratch or to update an existing pipeline by providing only the fields you want to change.

Inputs

All inputs are optional. If an existing pipe is provided, any component input that is left unconnected is inherited from that pipe, allowing you to override just the fields you need.

• pipe (PIPE_LINE, optional): An existing pipeline to use as the base. Values from this pipe are used as defaults for any component that is not connected.
• model (MODEL, optional): The model to store in the pipeline.
• pos (CONDITIONING, optional): Positive conditioning to store in the pipeline.
• neg (CONDITIONING, optional): Negative conditioning to store in the pipeline.
• latent (LATENT, optional): Latent image to store in the pipeline.
• vae (VAE, optional): VAE to store in the pipeline.
• clip (CLIP, optional): CLIP model to store in the pipeline.
• image (IMAGE, optional): Image to store in the pipeline.
• xyPlot (XYPLOT, optional): XY plot configuration to store in the pipeline, used for XY plotting workflows.

Outputs

• PIPE_LINE: The assembled or updated pipeline, containing all provided components and any values inherited from the base pipe.

Usage Notes

This node is commonly used together with Pipe Out to pass a full set of workflow components through a single connection. Because every input is optional, you can use Pipe In as a lightweight updater: connect an existing pipe, then only attach the inputs you want to replace. The xyPlot input is specifically useful when you want to carry XY plot settings through the same pipeline mechanism as the other components.