When you split a workflow with an If/Else action, each branch runs its own steps. Sometimes you want two or more branches to continue into the same next action instead of repeating that action in every branch. Merging branches lets you do exactly that: connect the end of one branch into a step that another branch already leads to, so they converge on a single shared action.

What merging does

A merge creates one shared action that several branches all continue to. Instead of building (and maintaining) the same step separately in each branch, you build it once and point the other branches at it.

Before merging: the same step is duplicated in each branch. Here, both the "GTM - Zoom Pro License" branch and the "None met" branch build and maintain their own "Send Slack Notification" step.

After merging: both branches continue to one shared action. The "Send Slack Notification" step is built once, and both branches lead into it.

The shared action runs once for whichever branch the run follows. Anything you place after it applies to both branches.

Connecting two branches (creating a merge)

You connect branches by dragging from the end of one branch to the action you want it to continue into.

1. Hover over the action (or branch) you want to connect from. A small connector dot appears at the bottom of the card.

2. Click and drag from the connector dot. A line follows your cursor.

3. Drag the line over the action you want to merge into. As you hover a valid destination, that action grows slightly to show it is the target you are about to connect to.

4. Release over the destination. The two branches now converge on that shared action.

Tip: You can only connect to an action that comes after the branch you are dragging from. Workflows always flow forward, so a branch cannot loop back to an earlier step. Destinations that are not valid will not respond while you drag.

You can merge:

• Two branches of the same If/Else into a shared next action.

• A branch into an action that is part of another branch, further down the workflow.

Disconnecting a branch from a merge

When several branches share an action, each incoming connection has a disconnect button on its line. Use it to separate one branch back out from the shared action.

1. Find the merge, the action that several branches point into.

2. Hover the disconnect icon on the connection you want to remove. The line it will disconnect is highlighted, so you can confirm you are removing the right branch.

3. Click the disconnect icon.

The branch you disconnected continues to whatever action came after the shared step, and the other branches stay connected to it. Disconnecting never deletes the shared action or any steps after it: it only separates that one branch's path.

What happens to steps after a merge

Everything after the shared action belongs to all branches that merge into it. If you later move the shared action somewhere else, the branches that were merged into it automatically continue to the next action below it (or finish the workflow if there is nothing after it), so the workflow always stays valid.

Things to keep in mind

• Forward only: a branch can only merge into an action that comes after it. The editor only lets you drop on valid destinations.

• One shared action, many entrances: a merged action can have several branches leading into it. Each entrance has its own disconnect button.

• Validation still applies: the shared action and every step after it must be fully configured for the workflow to run, the same as any other action.

Frequently asked questions

Can I merge branches from different If/Else actions?

Yes. As long as the destination action comes after the branch you are dragging from, you can connect them.

Will merging change what the shared action does?

No. The shared action keeps its configuration. It simply runs for whichever branch the run follows.

What is the difference between disconnecting a branch and deleting the action?

Disconnecting separates one branch from a shared action without changing the action itself. Deleting removes the action entirely. To stop one branch from using a shared action, disconnect it. Do not delete the action, since other branches may still rely on it.

Does the shared action run more than once if multiple branches reach it?

No. A workflow run follows a single path, so only one branch leads to the shared action, and it runs once.