Automate actions
Conditions and rules
AND conditions on item fields after the trigger fires.
Conditions decide whether a workflow continues after its trigger. Every condition must match (AND). An empty list matches all events for that trigger (or the latest item on a schedule).
Live example
WHEN tenant.item.created IF category eq top-stories THEN Slack
Fields
| Field | Typical use |
|---|---|
| category | eq or in — e.g. top-stories |
| title | contains a keyword |
| summary | contains / not_contains |
| url | contains a path fragment |
| source_id | Limit to one connector |
Operators
| Operator | Value |
|---|---|
| eq / neq | Exact string (case-insensitive). aliases: equals, not_equals |
| contains / not_contains | Substring |
| in / not_in | Comma-separated list, e.g. tech, markets |
| gt / gte / lt / lte | Numeric compare (optional % suffix) |
| exists | No value — field is non-empty |
Numeric operators need numeric field values. Item category and title are strings — use eq/contains there, not gt, unless the field actually holds a number.
OR groups and product-discount fields are not live. Keep rules as AND over item fields.
32 articles on this site. Engineering notes on GitHub.