Merge

Combine several upstream values into one payload for the next step.

Overview#

Merge joins multiple data streams before a single downstream block runs. It is the compact way to feed several answers or branches into one prompt, model call, or output.

Common pattern: several Workflow Input blocks → Merge → one LLM Chat block.

Workflow Preview

Merge

Read-only builder graph

Ports#

Inputs , in 1, in 2, in 3 (and more): Connect the values you want combined. At least one connection is required.
Output , Data: One combined value passed to the next block.

Inspector#

Merge has no inspector settings. What you connect defines the result.

Tips#

Connect inputs that belong together semantically , not unrelated leftovers.
If the graph is hard to read, split merging into stages instead of one crowded merge.
Use Merge when several cues should feed one prompt, not as a catch-all for messy wiring.
Label upstream blocks clearly so merged data stays easy to reason about.

Workflow Studio

More blocks

Workflow Input

Ask the customer one clear question and turn their answer into data your workflow can use.

Workflow Form

Collect several run-modal fields in one grouped form, each with a stable key for downstream steps.

Workflow Output

Define what the customer receives when the workflow finishes.

Block reference

Merge

Combine several upstream values into one payload for the next step.

Overview#

Merge joins multiple data streams before a single downstream block runs. It is the compact way to feed several answers or branches into one prompt, model call, or output.

Common pattern: several Workflow Input blocks → Merge → one LLM Chat block.

Workflow Preview

Merge

Read-only builder graph

Ports#

Inputs , in 1, in 2, in 3 (and more): Connect the values you want combined. At least one connection is required.
Output , Data: One combined value passed to the next block.

Inspector#

Merge has no inspector settings. What you connect defines the result.

Tips#

Connect inputs that belong together semantically , not unrelated leftovers.
If the graph is hard to read, split merging into stages instead of one crowded merge.
Use Merge when several cues should feed one prompt, not as a catch-all for messy wiring.
Label upstream blocks clearly so merged data stays easy to reason about.