The Fork activity allows you to create multiple outbound transitions, in order to carry out several activities independently within the same workflow.

For example, you can use the activity after a query, in order to perform two actions in parallel:

  • Save the result of the query into an audience,
  • Execute a segmentation on the result in order to send multiple deliveries.

You can also use the activity in the context of content creation and delivery sending automation, in order to launch the target calculation and the content creation in parallel. A dedicated use case is available in this section.


Outbound transitions added after a Fork activity will not execute simultaneously. This behaviour can impact the workflow’s performances. Use this activity if you need to execute several activities independentely, and eventually join them together before executing the rest of the worklow.

To configure the Fork activity, open it define the number and label of the outbound transitions.

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.

On this page