🇪🇸 Español 🇬🇧 English 🇧🇷 Português

Node: Merge Branches

How to use the Merge Branches node to synchronize parallel paths in a workflow before continuing.

Jul 11, 2026

The Merge Branches node is a synchronization point: it brings two or more parallel paths of the workflow (for example, the ones coming out of "Run in Parallel" or a Switch) back into one, and waits until ALL the branches feeding into it have arrived before continuing.

When to use it

  • After a "Run in Parallel" node, to make sure both branches finished before moving on.
  • When several branches of a Switch need to converge on the same final step.

Configuration

No configurable fields: the node automatically detects how many edges point into it and waits for that many visits before opening the gate.

Example

"Run in Parallel" fires two branches: A) "Send Email to Customer"; B) "HTTP Request" to an external CRM. Both branches end at a Merge Branches node, and only once both have arrived does the flow continue to "Close Conversation" — guaranteeing both tasks finished before closing.

Tips

  • If only one edge points into the node, it behaves as a transparent pass-through (nothing to wait for).
  • The counter resets after the gate opens, so it also works inside a Loop that repeats several times.

Troubleshooting

  • The flow seems "stuck" after Merge Branches: check that ALL the branches that are supposed to arrive are actually wired into the node — an unconnected branch never completes the expected count.
Was this helpful?

Related articles