Condition

Add a condition

Add a Condition step and click it. For each rule:

1. Choose the source: the trigger event (shown by its name) or Contact.
2. Pick the Property name. Event properties come from the event's definition. Contact properties are email, first_name, last_name, unsubscribed, and properties.<key> for each custom property.
3. Choose the Operator and, where needed, a Value, then click Add.

With more than one rule, choose and (every rule must match) or or (any rule can match). The step then has two paths, True and False.

Operators

is equal to, is not equal to, contains, starts with, and ends with compare text. is greater than, is greater than or equal to, is less than, and is less than or equal to compare numbers and are false when either side is not a number. exists is true when the property has any value; is empty is true when it is missing or an empty string. A missing property makes every other operator false, except is not equal to.

Example

A run triggered by this event takes the True path of a rule plan is equal to "pro":

{"event":"plan.changed","email":"you@example.net","payload":{"plan":"pro"}}

Things to know

• Contact values are read when the step runs, so an earlier Update contact step is taken into account.
• event.* always means the trigger's payload, even after a Wait for event step. The payload of the event that ended a wait is stored in that step's output only.
• A condition can have up to 50 rules.