How does “if/then” logic work in flows?

Still have a question, spotted an error, or have a better explanation or a source we should cite?

Think about the last time you sent a follow-up email only to people who opened the first one. That right there is if/then logic in action. It's the engine behind almost every smart automation flow you'll build.

The structure is simple. IF a condition is true, take one path. If it's not, take another. That's it. What makes it powerful is what you do with it.

Here's a practical example. You send a promotional email from captain@deepcurrent.io. Your flow then asks: did this person open it? If yes, send a follow-up with more detail. If no, resend the same offer with a fresh subject line two days later. Two different experiences, one decision point.

Another one: IF a subscriber's cart total is over $100, show them a premium upgrade offer. ELSE show the standard offer. You're not writing two separate campaigns. You're writing one flow that adapts to what you already know about the person.

One thing worth knowing about timing: conditions are evaluated at the moment someone reaches that decision point in the flow, not when they first entered it. So if someone joined your list last week but only just reached the branching step today, the flow checks their data right now. That means the logic stays current, which is actually really useful for things like engagement status or recent purchases.

Where it gets interesting is when you chain these decisions together. One if/then narrows the path. Two if/then steps narrow it further. By the third or fourth decision point, you can be sending very specific content to a very specific type of subscriber (without writing a novel of rules). This is what people mean when they talk about conditional branching. Each branch is just a series of if/then decisions stacked in sequence.

Tools like Klaviyo, ActiveCampaign, and Customer.io all build their flow builders around this logic. The visual canvas just makes the if/then branching easier to see and manage.

But if you're just getting started with flows or want to pressure-test your logic before sending, our SOS hotline is free. Sometimes a second pair of eyes on a branching structure catches things the builder doesn't flag.

Contributors

Who worked on this answer

Every name links to their profile. Every company links to their site. Real people, real accountability.

Ask an AI · tailored to your setup

Map my flow logic

I'm building an automation flow for [your use case, e.g. post-purchase, welcome series, cart abandonment]. Help me map out the if/then logic I need. My subscribers are brief description. I want different paths based on condition 1, e.g. opened email and condition 2, e.g. purchase value. What should my branches look like, and what happens to people who don't meet any condition?

Edit the yellow boxes, then send to the AI of your choice.