Merge

Overview

The Merge step rejoins parallel branches of a flow into a single path. Use it after a split (if your flow has a condition step in it) to bring branch outputs together so downstream steps can use them.

Use When

• Your flow splits into parallel branches and needs to continue as one path

• You want outputs from multiple branches available to the same downstream step

Configuration

1.     Merging Paths

Add the steps whose outputs should be available after the merge. Paths that didn't run return empty values — they won't block the flow.

2.     Set Merge Rules

Define how each field should be resolved when the same field exists across multiple paths.

For each rule, set:

• Field Name: Give your merged data a clear name

• Type — Select the data type (e.g., File, User, or Text) to match your sources.

• Source — Add the specific outputs from your branched steps.

Default Value

A fallback used when none of the sources has a value. Not supported for all field types.

How it works at Runtime

At runtime, the Merge step automatically identifies which branch was taken and carries that specific data forward. Steps following the Merge will only "see" the data from the active path.

Notes

• Merge rules are optional — without them, all path outputs are available downstream

• Source order matters: the first source with a value wins

• The Merge step does not create a task or output document