In a process automation workflow, a split node enables you to divide a single process flow into multiple execution paths that can run in parallel, either unconditionally or based on specified conditions.

Splits are commonly used to perform independent tasks at the same time or to route work based on business conditions.

Add Split and Merge to the canvas

Split

When you add a split node to the process workflow, it behaves as follows:
  • It accepts one incoming flow and creates two branches by default. You can add more branches as needed.
  • You can add nested Split and Merge nodes to the process workflow.
  • Each branch can run independently or simultaneously, depending on the logic configured.
  • You can assign separate tasks (such as bots, sub-processes, or human approvals) to each branch.
  • The process engine executes them in parallel, so each runs independently.
    Note: Parallelism is achieved only when the device pool has a sufficient number of available devices. For more details, click About device pools Create device pools, and Run a parallel process with split and merge .
  • A split node can be used to perform the following tasks at the same time, such as:
    • Send approval requests to multiple stakeholders at the same time.
    • Process different datasets simultaneously.
    • Trigger multiple independent activities during workflow execution.

Branch Start

A Branch start marks the beginning of each path that originates from a split node.

Purpose
  • Clearly identifies where a branch begins.
  • Helps the process engine map tasks to the correct branch.
  • Improves readability, especially in complex workflows.

Branch Exit

A Branch exit marks the point where a branch ends before joining back into a merge node.

Purpose
  • Clearly defines the endpoint of each branch.
  • Ensures downstream tasks do not proceed until the required branch is complete.

Employee onboarding example

The video demonstrates how split and merge brings parallel execution to process automation, enabling workflows to scale across departments, systems, or parallel workstreams.

Sue works in an HR department. Every time a new employee joins, Sue triggers an onboarding process where multiple departments need to act simultaneously.
  • HR must create a profile for the new hire.
  • IT must create a system account.
  • Finance must set up payroll.
  • Security must provision badges.

All these tasks need to run in parallel. By executing these tasks simultaneously, organizations can reduce onboarding time significantly. Parallel execution minimizes waiting periods and ensures that all departments can work independently yet efficiently within the same process.

Sue can add a split and merge node from the left panel or through Quick Add. The framework includes a Split with Branch Start, and Branch Exit to help her structure parallel execution.

In the example, Finance, IT, and HR each have their own branch. Each branch can be configured with conditions and actions specific to its requirements.

At the merge node, even if one branch finishes early, the process waits for all branches to complete before moving to the next step, such as sending an email and then finalizing the workflow. When Sue run the process, all branches execute in parallel before continuing sequentially.

If a department, such as HR, must perform multiple tasks concurrently, Sue can add nested split and merge nodes. The canvas automatically adjusts the layout and spacing to keep the process readable and easy to understand.

Configure split node

Perform these steps to configure a split node and its branches:
  1. Add a Split node.
    1. From the Elements panel, drag the split node into the workflow.

      Two branches are added automatically.

    2. (Optional): Add a description in the Description field to document the purpose of the split.
  2. Configure Branch Start. For each branch, enter the following values:
    1. Enter a meaningful name in the Branch name field.
    2. Choose an option from the Branch type field:
      • Always run:: Executes every time.
      • Condition: Executes only when specific conditions are met.
      • Fallback: Executes only if all other conditional branches fail.
    Perform the following steps if you select Condition:
    1. Specify the Condition type ((Boolean, String, Number, or Datetime).
      Note: If using a String condition, enable Match case to apply case-sensitive filtering.
    2. Specify the Source. The value specified in the Source field triggers a conditional rule when its value meets a specified condition.
    3. Select Operator (based on condition type):
      • Equal to
      • Not equal to
      • Less than
      • Greater than
      • Less than or equal
      • Greater than or equal
    4. Specify the Target. The value specified in the Target field is affected by a conditional rule, whose visibility or value changes based on the source field’s state.
    5. You can add multiple conditions using AND or OR logic.
  3. Configure Branch Exit. Add a meaningful description to the Branch Exit field.
  4. After configuring all branches, save your changes. The branches will execute concurrently or conditionally during process runtime.