Fork fork

You can use the Fork activity to create multiple outbound transitions and to run several activities independently within the same workflow.

The outbound transitions that you add after a Fork activity do not run simultaneously. This behavior can impact the workflow performance. Use the Fork activity if you need to run several activities independently. Optionally, you can join the outbound activities before the subsequent part of the workflow.

To configure a Fork activity and its related activities, follow these steps:

  1. Open the Fork activity and define the name and the label of the outbound transitions.

  2. Open each outbound transition and configure it.

  3. Optionally, to join outbound transitions, add an AND-join activity. Learn more.

    The subsequent part of the workflow runs only upon completion of the joined outbound transitions.

Example: segmentation

In this example, different emails are sent to different population groups. A Fork activity is used after a query, to perform two actions in parallel:

  • Save the query result

  • Segment the result to send multiple deliveries

    The fork activity follows the intersection of two queries and precedes a list update activity and a split activity.

The workflow comprises these activities:

  1. Query activity

    Two population groups are selected: women and Parisians.

  2. Intersection activity

    The intersection of the query results, that is, Parisian women, is selected.

  3. Fork activity

    The calculated population is saved and, in parallel, segmented into two groups:

    1. Parisian women who are aged between 18 and 40
    2. Parisian women over 40
  4. Delivery activity

    A different email is sent to each population group.

Use case: send a birthday email

A recurring email is sent to a list of recipients on their birthday. A Fork activity is used to include recipients who were born on February 29 on a leap year. Learn more about this use case.

The fork activity follows a test activity and precedes two query activities.

Use case: automate content with a workflow

The creation and the delivery of a content block is automated. A Fork activity is used to calculate the target and, in parallel, to create the content. Learn more about this use case.

The fork activity follows a delivery activity and precedes a query activity and a content management activity, which are both joined through an AND-join activity.

You can then configure each outbound transitions, then join them together using an AND-join activity, if needed. This way, the rest of the workflow will execute only once the Fork activity’s outbound transitions are finished.