Fork fork
You can use the Fork activity to create multiple outbound transitions and to run several activities independently within the same workflow.
To configure a Fork activity and its related activities, follow these steps:
-
Open the Fork activity and define the name and the label of the outbound transitions.
-
Open each outbound transition and configure it.
-
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 workflow comprises these activities:
-
Query activity
Two population groups are selected: women and Parisians.
-
Intersection activity
The intersection of the query results, that is, Parisian women, is selected.
-
Fork activity
The calculated population is saved and, in parallel, segmented into two groups:
- Parisian women who are aged between 18 and 40
- Parisian women over 40
-
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.
Use case: automate content with a workflow
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.