Customer.io

Types of branches

Updated August 17, 2026

Flow controls and branches

We offer three types of branching flow controls that you can place anywhere in your workflows:

  • True/False Branches: Send profiles down one path if they match a condition, or down the other path if they don’t.
  • Multi-Split Branches: Send profiles down different paths where each path has its own conditions.
  • Random Cohort Branches: Send profiles down different paths based on a random distribution. This is a great way to test different flows in an automation, like a more robust version of our A/B testing feature for individual messages.
The left hand menu of the workflows step of an automation. Towards the bottom is a list of branches under the section title Flow Control.

You can use JSON dot notation in condition logic

If you store attributes or event data in JSON objects or arrays, you can use JSON dot notation in your branch conditions to evaluate these properties. Use array[] to represent any item in an array or array[0] to represent the first item in the array. See Storing and using JSON for more information about dot notation in Customer.io.

Walkthrough of different branch types

Check out this walkthrough to understand how you could use each branch type:

Moving branches

You can move branches like any other items in the workflow. When you click and drag a branch, you’ll carry everything along its paths. That way, wherever you drop the branch, everything stays together.

Move branch

Moving delays in active automations

If a branch contains a delay that currently has profiles waiting in it, and you move the branch, the profiles in your automation will move with the delay.

Deleting branches

You can’t delete a branch until you’ve removed all items from it. If you need to delete a branch, first delete or move all items out the branch’s path. Then, select the branch and click Delete.

Copying branches

You can copy branches to/from other workflows by clicking Copy from workflow at the top of the Add menu or selecting a branch then Copy to at the bottom.