How to use custom fields in automation and triggers
Custom fields can drive automations and action listeners — reacting when a field is filled, changes value, or meets a condition. Understanding when to use each system helps you build reliable, efficient workflows.
TL;DR
Automations run every ~60s, support complex conditions (field + status + timing), and multi-step flows. Action listeners fire instantly when a field changes, ideal for real-time reactions. Use slug values (not labels) for select field logic. Always check "Max. fires per order" if an automation doesn't re-trigger.
4 things to know
Automations — field-based conditions
Add field conditions to automation rules: "field equals X", "field changed", "field contains value", "field is not empty". Runs every ~60 seconds. Combines multiple conditions (field + status + date). Good for: send email when checkbox set, assign user when select changes, move status when number exceeds threshold.
Action listeners — instant reactions
Fire the moment a field value is saved. Ideal for: real-time notifications, triggering integrations, updating related data. No delays. Cannot combine multi-step logic. Best for simple, focused actions — move complexity to automations.
Always use slugs for select fields
In automation conditions and @if logic, compare select fields using their slug value (not the label). Example in @if: @if(@select[customer-type,slug] == commercial). Labels can change; slugs should stay stable.
Common issues
Automation doesn't re-trigger: check "Max. fires per order" — increase it if the same lead should trigger again. Field change not detected: the change must come from a save event (preview/editing without saving does not trigger). Large JSON fields: use helper flag fields for reliable triggering.
Read more⌄
Patterns for complex logic
- Helper select field: convert multiple conditions into a single select that triggers actions
- Listener + automation combo: listener fires immediately and sets a marker field; automation evaluates the full rule on schedule
- Status as trigger: status changes are universally supported and easy to chain
- JSON + flag field: store complex data in JSON, use a simple checkbox or text field as the trigger flag
Common searches
field trigger automation • custom field automation • field change listener • trigger when field changes • action on field update
Was this article helpful?
That’s Great!
Thank you for your feedback
Sorry! We couldn't be helpful
Thank you for your feedback
Feedback sent
We appreciate your effort and will try to fix the article