> For the complete documentation index, see [llms.txt](https://docs.enate.net/enate-help/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.enate.net/enate-help/builder/builder-2021.1/case-configuration/merging-branches-in-a-case.md).

# Merging Branches in a Case

## Overview

You can merge branches in your Case workflow processes to help you streamline the creation of your business Case flows. 

Sometimes creating a business process can leave you with many different routes that you want to lead onto the same action depending on the criteria of the step. By using this new merge feature you will be able to choose different Actions to end in the same outcome. 

Watch the following video to find out more:

{% embed url="<https://enate.cdn.spotlightr.com/watch/MTM1Mjg5OQ==>" %}

## How to merge branches

You can choose to merge together parallel branches or conditional branches.&#x20;

To merge multiple Actions together, click on the menu of one of the Actions you want to merge and select 'Merge', then 'Add'.

<figure><img src="/files/hU2tN0WaoMa6y6SwwbpM" alt=""><figcaption></figcaption></figure>

In the following pop-up select the other Actions you want to merge it with from the list of Actions that are available for merging.

<figure><img src="/files/sYSqlpBqIykZtxXiiKsO" alt=""><figcaption></figcaption></figure>

Then select which Action you want them to be merged into - you can either choose from an existing Action type or you can choose to create a brand new Action type for this.

<figure><img src="/files/Wkpk7Ppc9zweOaUSfZsU" alt=""><figcaption></figcaption></figure>

The merged Action will then appear in the flow.

<figure><img src="/files/CqodVjK5rIkaJJoFLyNB" alt=""><figcaption></figcaption></figure>

{% hint style="info" %}
Note that you can only merge together Actions within the same step.
{% endhint %}

## Specifics of merging parallel branches

If you are merging together Actions from parallel branches, the merge Action will wait for **all** of its the predecessor Action to complete before it can start.

<figure><img src="/files/23FallwZixB328Fmakd3" alt=""><figcaption></figcaption></figure>

## Specifics of merging conditional branches

If you are merging together Actions from conditional branches, the merge Action will start when **one** of the conditional branches has been completed.

<figure><img src="/files/nQ0sohaISlbRp3xTjUx7" alt=""><figcaption></figcaption></figure>


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.enate.net/enate-help/builder/builder-2021.1/case-configuration/merging-branches-in-a-case.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.