Zendesk automation: triggers, automations, macros and routing

All three tools change tickets, but they start differently. Zendesk's own framing: the difference between triggers and automations is not which actions they can perform, but which conditions set them off. Macros have no conditions at all, because nothing evaluates the ticket automatically. An agent decides when to apply one.

The three combine well. A common pattern is a macro that adds a tag, which then immediately sets off a trigger that looks for that tag. Note that a macro can only do what the current user is permitted to do, so an agent with limited permissions may not be able to apply every change a macro contains.

Every time a ticket is created or updated, all ticket triggers run against it in a cycle, in the order they are listed. If a trigger updates the ticket, the cycle starts over and every trigger runs again, except the ones that have already fired and updated the ticket. So one trigger's change can make another trigger's conditions true, even if they weren't true a moment earlier.

Zendesk's recommended order for ticket triggers:

1. Triggers that change ticket values such as status, priority or other fields.
2. Triggers that assign the ticket.
3. Notification triggers, last, so emails and messages reflect the ticket's final state.

If you use trigger categories, the order of the categories must match the order you want triggers to run in; you change it with Edit order on the triggers list. Use the condition Ticket | Is | Created for rules that should act only on new tickets (routing is the classic case), and Ticket | Is | Updated for things like update notifications. Ticket triggers don't run on closed tickets.

Automations run once every hour on all non-closed tickets. The timing is approximate: an automation starts at some point during the hour, not at a fixed minute. Each automation can act on up to 1,000 tickets per hour, and any overflow waits for later runs.

Because automations re-check the same tickets every hour, Zendesk requires each one to include a condition that is true only once or an action that nullifies at least one condition. Without it, the conditions keep matching and the automation fires in an endless loop. The standard 'close ticket after solved' automation does this naturally: closing the ticket removes it from the 'Status is Solved' condition. For custom automations, the usual fix is to add a tag and exclude that tag in the conditions.

Triggers can route tickets by setting a group, an assignee or skills, but Zendesk also has dedicated routing features:

• Omnichannel routing pushes tickets from email, calls and messaging to agents based on their availability and capacity, and can also consider priority and skills.
• Skills can be added to tickets by triggers and marked required or optional. Required skills limit which agents are eligible; optional skills can time out so the ticket falls back to the normal routing model.
• Standalone skills-based routing is a pull model: tickets are sorted by skill and agents pick work from skill-based views. It can't be used with voice or messaging tickets.

For calls, omnichannel routing is the only way triggers can influence routing, because a ticket is created as soon as a call enters the queue. Routing features differ by plan, so confirm what your plan includes before you design around skills.

When a rule needs to tell another system something, use a webhook. You create it in Admin Center and pick its connection type: Zendesk events, or trigger or automation. A webhook can use one of those, not both, and you can't change the connection method later. In a trigger or automation, add the 'Notify webhook' action, select the webhook and enter the payload. Request bodies can be JSON, XML or form-encoded, and the payload can't exceed 16,000 characters. Each webhook has a Test webhook option for checking the request before it goes live.

When the logic needs to read data, make decisions in code or write back to tickets, use the Ticketing API. Tickets are created with a POST to the tickets endpoint and updated with a PUT to the ticket's own URL, with bulk variants for many tickets at once. Requests can authenticate with an OAuth access token sent in a Bearer header.

Good first candidates for Zendesk automation:

• Routing new tickets to the right group by channel, form, language or keywords.
• Reminders and escalations for tickets that have waited too long for a reply.
• Posting high-priority or VIP tickets to a Slack channel through a webhook.
• Pulling order or account data into a ticket through the API before an agent opens it.

TascaLab works on top of your existing Zendesk account, with no platform switch, using the Zendesk API, webhooks and Make or n8n where they fit. Ticket Routing & Categorization is a one-time project at $775; Custom Automation for flows that span several systems is from $1,200. Every project includes 30 days of post-launch support, basic documentation and no hidden fees, and most setups take 1–3 weeks. You can start with a free 30-minute Health Check call.