In a process automation workflow, a Merge node combines multiple parallel branches back into a single execution path. Merge nodes are typically used after a Split node to synchronize tasks that run concurrently.

When you add a merge node to a process workflow, it behaves as follows:
  • Each parallel branch created by a split node must eventually connect to a merge node.
  • The process instance waits at the merge node until all incoming paths that were executed are complete.
  • Once the required branches finish, the workflow resumes as a single sequential flow.
This ensures that subsequent set of tasks do not begin until all necessary parallel tasks have completed.

Loan processing example

Consider a loan-processing workflow where multiple verification activities occur in parallel:
  • After a loan application is submitted, two tasks run simultaneously: Credit check and Document verification.
  • Once both tasks are completed, the merge node consolidates the paths.
  • The process then continues to the next step, such as Generate risk score or Proceed to final approval.
This example explains how the merge node ensures that decision-making steps occur only after all prerequisite validations are completed.

Loan processing workflow

Configure merge node

When you drag a Split node into the workflow, the corresponding Merge node is automatically added. To configure the merge node, follow these steps:
  1. (Optional): Add a description in the Description field to document the purpose of the merge.
  2. (Optional): Enter a custom title in the Update request title field to update the request name when this node is reached.
  3. (Optional): Provide a message in the Display message field.
  4. In the Request attributes field, click Add attribute and provide the following details:
    • Label: Provide a label (name) for the attribute. After you add the label, an ID is automatically generated.
    • Visibility: Choose the attribute type (Visible, Hidden).
    • Type: Choose the data type (String, Number, Boolean, Datetime).
    • Value : You can either assign a hard-coded value to the selected data type or provide a value through a variable.

    Attributes are created and checked in along with the process. You can customize the columns in the Request and Task view pages and select the attributes to view them as separate columns. Attributes are shared across processes.