Kulea's Quick Guide to Conditional Logic

Whether you're an experienced marketing automation user or just getting started, you'll quickly need to get your head around conditional logic. Simply put, it's a system of rules expressed as "if this, then that" - the condition (the "this") dictates the response (the "that"). Conditional logic is everywhere in daily life: if it's cold, put on a jumper; if you're hungry, eat something; if you're tired, go to bed. It's also the foundation behind pretty much every marketing automation journey ever built.

The OR Condition

OR is inclusive - it widens your net. "If you're tired OR it's late, go to bed" applies in either scenario: even wide awake, lateness alone sends you to bed; even at 3pm, tiredness alone does the same.

The AND Condition

AND is the opposite - exclusive, narrowing your criteria. "If you're tired AND it's late, go to bed" only applies when both are true - no early naps. AND can feel counterintuitive, since everyday "and" usually means getting more ("I want that and that"), but in conditional logic it does the reverse.

The NOT Condition

NOT flips the condition entirely, and a careless one can be expensive. Imagine a 10,000-contact database with the rule "if a contact lives in London, send direct mail" - that correctly reaches 1,000 London-based contacts. Introduce a careless NOT - "if contact NOT lives in London, send direct mail" - and you've just mailed the remaining 9,000, wherever in the world they happen to be. Treat NOTs with respect.

The ELSE Statement (and Time Restrictions)

ELSE - or "otherwise" - gives an alternative response, branching in a different direction (in Zapier, this is what "paths" do). Extending the London example: "if contact lives in London, send direct mail, ELSE send an email" saves a fortune on stamps. ELSE is often paired with a time condition for real-time triggers - "if I get to a club and I'm let straight in, I enter; ELSE I wait up to 15 minutes, then go to a different club." Common time-condition variants are: don't wait at all, wait forever, wait a fixed duration, or wait until a specific date/time before falling through to the ELSE branch.

Nesting

A nested condition sits within another branch, and conditions can be nested indefinitely to build logic that handles almost any scenario. You can nest an OR within an AND, for example: "speak to people with red hair wearing either blue OR green shirts" - the shirt-colour criteria only applies once the hair-colour criteria is already satisfied.

How This Applies to Marketing Automation

Marketing automation isn't as smart as it sometimes gets credited for - like the rest of us, it needs clear rules to follow, and conditional logic is how those rules get built. Every platform's interface looks different, but the underlying logic is the same: in Zapier, rules are built from triggers (the "if") and actions (the "then"). Kulea's drag-and-drop journey builder takes that further, letting you build advanced rules visually, and conditional logic shows up throughout the platform - including in CRM filters, where nested OR conditions inside an AND condition might read as "include all directors, except those with finance in their job title, based in England, Ireland, Scotland or Wales."

If you're struggling to translate an idea into a working condition - whether in a rules-based tool like Zapier or a visual builder like Kulea's - write down what you're trying to achieve in plain English first, then translate it into if/then/and/or/else language. It almost always makes the build itself far easier.

Frequently Asked Questions