Branch with a condition step

AutomationsUpdated

A yes/no split sends contacts down one of two paths, and the two paths never rejoin.

A Yes / no split step sends different people different ways through the same automation: one path for those who match a condition, another for those who don’t. Add it from the + menu like any other step.

The three condition kinds

Opening the split asks “What decides who goes where?” and offers exactly three options:

  • They opened the last email in this flow: whether the contact opened the email immediately before this split, on the path they took to get here. The hint suggests pairing it with a wait first: “did they open within 3 days?”
  • They clicked it: the same idea, for a click.
  • Who they are (lists, tags, fields): “The same rules segments use”, the same rule builder as Build a segment with the rule builder. You can check engagement with a specific past campaign when building a segment elsewhere, but not here, only with the automation’s own emails.

What happens to each arm

Every contact who reaches the split goes down exactly one arm, each its own chain of steps built like the main flow. Each arm is labelled after the condition you picked: Opened it and Didn’t open, Clicked and Didn’t click, or Matches and Doesn’t match. The two arms never rejoin. An arm can end on its own (“Otherwise they just end here — that’s fine”) or run into more steps, including another split.

Splits can nest, but only 5 levels deep on any single path. Past that, the flow tells you: “Splits can only nest 5 deep — start a second automation instead.”

If the check can’t be answered

A split never guesses. If what it’s checking can no longer be answered (say a tag the rule referenced gets deleted), the contact stops at that step rather than being sent down a random path. They show up as stuck, visible from the “N stuck” badge on the automation’s index row or the report’s step-error count.

Editing a split

  • Removing a step just above a split reconnects the flow automatically.
  • Removing the split itself, when both arms have steps, asks which arm to keep: “Both paths have steps. Keep one — the other path’s steps are removed with the split. Emails that have already sent keep their stats and history.” The two buttons name the arms, so on an opened-check they read Keep the “Opened it” path and Keep the “Didn’t open” path; the kept arm joins the main flow directly, and anyone currently on the dropped arm finishes there. If only one arm has any steps, deleting the split just keeps that arm, no choice needed.

A Yes / no split step, Did they open the last email?, with its two labelled arms side by side: Opened it leading to another email, and Didn’t open where people just end.

Splits are one of five step types: see Automation steps explained for the rest.