Zendesk triggers vs automations: choose event or time-based ticket actions

SOURCE-BASED ANALYSIS · NO HANDS-ON RATING

Choose the rule family from the event

Zendesk describes ticket triggers as business rules evaluated immediately after a ticket is created or updated. Automations are time-based rules that run hourly on non-closed tickets whose conditions are met. Start with the event your process actually needs. “When priority changes to urgent” and “when a solved ticket has waited for a defined period” are different contracts.

Write conditions and actions as a state transition

For each rule, record the starting state, qualifying event, conditions, actions and the state that prevents another unintended run. Zendesk requires an automation to contain a condition that is true only once or an action that nullifies at least one condition. Apply the same discipline to triggers even when the product does not express it with the same requirement.

A fictional escalation example

Suppose urgent tickets should notify a duty lead immediately, while a pending ticket waiting too long should return to an active queue. The immediate notification belongs in an event-based trigger. The elapsed-time review belongs in an automation. Add a field or status transition that shows the action occurred and prevents repeated notifications unless repetition is explicitly required.

The markers are design examples; choose fields compatible with your workflow.

Test interaction and order

Zendesk notes that actions from one ticket trigger can affect later trigger behavior, and changes made by automations can cause triggers to run. Use a sandbox or isolated test tickets. Record the audit trail after each update and confirm the final state rather than checking only whether an email arrived.

1. Create a ticket that misses all conditions.
2. Change exactly one field so the intended trigger qualifies.
3. Confirm its actions and any subsequent trigger effects.
4. Prepare an automation test with a controlled time condition and a nullifying action.
5. Verify the next hourly evaluation does not repeat the action unexpectedly.

Plan for hourly processing

Zendesk says automations run during the hour, not necessarily at the top of the hour, and documents processing limits. Do not promise an exact minute from an hourly rule. If the process requires immediate action, revisit whether a trigger or another supported mechanism is a better fit.

Keep a rule inventory

For each active rule, retain its owner, purpose, conditions, actions, dependencies and last acceptance test. Review overlapping conditions together. A disabled or reordered rule can change a later outcome even when the later rule itself was not edited.