What is a Fork?

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.

Fork example

Here’s a basic fork example:

When a subscriber enters into the fork, they will travel simultaneously down both sides. They immediately get subscribed to a campaign on each side. This allows you to send multiple campaigns 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.

Here's a more complex example:

When a subscriber enters into the fork, they'll receive a one-off email on the left branch and enter into delays for the middle and right branches. Once the email in the left branch has been sent, the subscriber will advance straight to the exit below the fork and never reach the other two actions in the middle and right branches. In order for them to remain active in the workflow after receiving the email in the left branch, the subscriber would need to reach a step allowing them to remain active in the workflow until they can finish the delays and pass through the middle and left branches.

To add additional branches to a fork, click the + icon to the right of the fork you're currently working with.

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.

Setting up Forks

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.