A condition tests one piece of trigger data against a value. Conditions narrow which trigger events actually run the actions.
Anatomy of a condition
Field path — a dotted path into the trigger payload, e.g.
content_plain,answers_by_label.Severity,user_displayName.Operator — one of the supported comparison operators below.
Compare value — the value to test against.
Supported operators
Type | Operator |
|---|---|
Equality |
|
Membership |
|
Numeric |
|
Array |
|
Empty |
|
Heads up — There is no regex operator and no built-in AND/OR aggregator. To combine conditions, chain multiple condition nodes (effectively AND) or branch off the trigger more than once (effectively OR). The condition schema supports AND/OR clauses but the builder UI doesn't expose it yet.
Forms-specific helpers
For forms.entry_submitted triggers, the payload includes both answers (keyed by question id) and answers_by_label (keyed by question label). Use whichever is easier — answers_by_label.Severity equals "Critical" reads much better than the equivalent id-based check.