Condition reference
The 5 condition operators, and how field paths resolve.
Each condition checks one field against one value. A rule's conditions are combined with AND only — every condition must match for the rule's actions to run.
Field paths
A condition's field is a dot-path into either:
payload.*— the triggering event's own data (see the trigger reference for what's available per trigger). Example:payload.statusfor adeal.stage_changedtrigger.contact.*— the contact's own record. Example:contact.email,contact.company.
A path that doesn't resolve to anything (e.g. a typo, or a field that's genuinely not
set) is treated as absent — equals/contains compare against an empty string,
exists is false.
Operators
| Operator | Matches when |
|---|---|
equals | The field's value, as a string, equals the condition's value |
notEquals | The field's value, as a string, does not equal the condition's value |
contains | The field's value contains the condition's value — works on strings (substring) and arrays (membership) |
exists | The field resolves to something other than null/undefined |
notExists | The field resolves to null/undefined |
exists/notExists don't take a comparison value — the other three do.
Comparisons are string comparisons. payload.status equals WON works because
status is already a string in the payload — but numeric fields get stringified
before comparing, so exact-match works fine, but there's no "greater than"/"less
than" operator for things like deal value.
Last updated on