Skip to main content
Node ReferenceMerge Node

Merge Node

Combine multiple inputs into a single output.

The Merge node is a planned logic node for combining multiple upstream branches into a single downstream flow. It is designed to take several inputs and present them as one output so the workflow can converge after a split.

Not yet available
The Merge node is part of the planned logic-node set. It appears in the node reference catalog with its intended purpose, but it is not wired into Builder Studio execution yet. There is no Merge node type, canvas node, executor, or schema definition in the current product, so it cannot be added to a canvas or run today. This page documents the intended behavior so the contract is clear before the node ships.

Intended purpose

Merge is meant to combine multiple inputs into a single output, joining branches that were split earlier in the workflow back into one path. It is the natural counterpart to Conditional: where a Conditional node would fan execution out into separate branches, a Merge node would fan those branches back in. It belongs to the logic and control group, alongside Delay and Loop.

How inputs combine today

Builder Studio already lets multiple edges feed into one node, and the execution layer resolves those inputs through its port-binding logic before a node runs. Some content-display nodes also surface a placeholder like Connect inputs to merge when several sources feed one slot. A dedicated Merge node would formalize this into an explicit graph step whose only job is to collect upstream values and emit a single combined output, instead of relying on each consuming node to gather its own inputs.

What to use instead for now
Until the Merge node ships, connect the branches you want to combine directly into the downstream node that consumes them. Builder Studio resolves multiple inbound connections at run time, so you do not need a separate merge step for a node to receive several inputs.

Related pages

Was this page helpful?