Skip to main content

​
Overview

The Merge step rejoins parallel branches of a flow into a single path. Use it after a split (following a Condition step) so downstream steps can use the combined outputs.

​
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 — a clear name for the merged data
  • Type — the data type (File, User, Text, etc.) to match your sources
  • Source — the specific outputs from your branched steps
  • Default Value — a fallback when no source has a value (not supported for all field types)

​
How It Works at Runtime

The Merge step automatically identifies which branch was taken and carries that data forward. Steps after the Merge only “see” the data from the active path.
Merge rules are optional — without them, all path outputs are available downstream. Where rules do apply, source order matters: the first source with a value wins. The Merge step itself doesn’t create a task or output document.