# Merge Paths node

The **Merge Paths** node is used to rejoin the split paths in a workflow into one main path (for example, if a workflow contains a [Split Path node](/docs/automation/flow-control/split-path-node)). By default, the **Merge Paths** node is processed every time a profile arrives at this node. If you don't want the node to be processed more than once, set a [limit](/docs/automation/automation-capping#flow-control-limits) for this node.

## Node usage in workflow
---

The following instructions explain how to add the **Merge Paths** node to a workflow diagram. Once added, this node does not require any additional configuration.

1. Click **THEN** on the node after which you want to place the **Merge Paths** node.  
**Result**: A dropdown list opens.
2. From the dropdown list, select **Merge Paths**.  
3. Connect the paths from the preceding nodes to the **Merge Paths** node.

## Example of use
---

<figure>
 <img src="/api/docs/image/54176ad07f146575310749eba44b7c2f42c1b327/docs/automation/_gfx/merge-example.png" alt="Example of Merge" class="full">
<figcaption>Example of a workflow that uses the Merge node</figcaption>
</figure>

The purpose of this automation is to divide the recipients into two groups to compare the effectiveness of email templates. Group A receives a standard version of the newsletter, whereas Group B receives an experimental version. At the end of the process, customers are assigned a tag. 

1. Start the workflow with the **Audience** trigger node. In the trigger settings, define the recipients of the email.
2. Add the **ABx Test** condition. In the settings of the condition, divide the audience. Group A consists of 80% of the whole audience, whereas Group B consists of the remaining 20% and receives the experimental version.
3. After an email is sent to customers, the two paths are joined with the **Merge Paths** node. 
4. Recipients of the email are tagged. 
5. When the tag is assigned, the workflow ends.