Forks split your workflow path into multiple parallel paths so that you can run several actions at once—rather than waiting for a subscriber to complete a step before moving on to another.
In this article:
Forks allow you to run multiple concurrent paths in Workflows. Each branch of the fork can contain actions, goals, delays, exits, and decisions. Forks look very similar to decisions but require no logic to run and they apply to every subscriber in its path.
Here’s a basic fork example:
Once the subscriber hits the fork, they will travel down both sides of it simultaneously. They immediately get subscribed to one campaign on the right side and another campaign on the left. This allows you to easily send multiple campaigns to your subscribers at the same time. If these campaign actions were set up vertically, the subscriber would have to finish one campaign before they can start the other.
You can add additional branches to a fork by clicking the + icon to the right of it.
Using Goals in Forks
It might not be obvious at first how goals work in forks. If you will be setting up goals in your forks, we recommend reading up on this article so that you understand how goals behave in those types of situations.
To add a fork, click the + icon wherever you would like it to be placed in the workflow.
When the modal appears, click to select the Decision step.
Once in place, you'll be able to add additional actions and other workflow steps on both branches of the fork.