Zendesk Workflow Examples
Individually, triggers, automations and macros are easy. A Zendesk workflow is four of them cooperating on one ticket without arguing, and that's the hard part.
The four parts of a Zendesk workflow
Before the examples, a quick map, because most broken workflows are the right logic in the wrong component.
The full comparison lives in triggers versus automations. One rule covers most decisions: if it depends on time passing, it's an automation, and if it depends on a judgement call, it is a macro.
Workflow one: intake and routing
The foundation. Every new ticket ends up in exactly one queue within a second of arriving.
A trigger on create sets the group from the ticket form, with an ALL block of ticket is created and form is X. One trigger per form, each adding a routing tag so you can audit it later. A final catch-all trigger, ordered last, assigns anything still without a group to a triage queue.
The catch-all is the part people skip and the part that matters. Without it, a ticket that matches no rule sits with no group, appears in no queue, and is discovered nine days later by an unhappy customer.
Then an SLA policy per group, so the clock reflects what that team promises. Details on the SLA side, and remember the policy needs a schedule attached or it runs on calendar hours.
Workflow two: pending chase and auto-close
The one that saves the most agent time, and it is three components.
A macro the agent clicks when they ask a customer a question: sets status to Pending, inserts the question template, adds tag awaiting_customer. One click instead of three actions.
An automation that fires after three days in Pending with that tag: sends a polite nudge, adds tag chased_once. Note the tag, because without it the automation would nudge every day forever.
A second automation after another four days with both tags: sets the ticket to Solved with a message saying you're closing it and they can reply any time. Which they can, and if the ticket has since closed, that reply arrives as a follow-up ticket carrying the history.
Use Liquid in the nudge so it addresses the person by name and references their actual question. A generic chase reads as automated and gets ignored.
Workflow three: escalation that doesn't shout
The requirement: a ticket at risk gets senior attention before the customer notices, without the team lead drowning in alerts.
Start with the SLA policy providing the breach target. Then a trigger with an ALL block of status isn't Solved, priority is Urgent, and an ANY block covering your escalation signals: tags contain escalate, or the requester organization is tagged enterprise. Actions: reassign to the escalation group, add an internal note explaining why, notify the group rather than a person.
Notify the group. This is the difference between a system people trust and one they mute. Named-person notifications create single points of failure and go unread on holidays.
Add an automation for the slow burn: still not Solved, priority high or urgent, hours since assignment greater than eight, business hours. Nudge internally, once, with a tag guard. Escalation that fires twice trains people to ignore it.
Workflow four: VIP handling
Small, high value, easy to get wrong.
Tag the organization, not the individual contacts. People change jobs and contact records multiply. An organization tag survives all of it, and every ticket from anyone at that company inherits the treatment automatically.
A trigger on create, ALL block of ticket is created and organization tags contain vip, sets priority, assigns the dedicated group and adds a tag your reporting can use. An SLA policy conditioned on that tag gives the tighter target. A restricted set of macros, scoped to that group, keeps the tone consistent.
What to avoid: a customer-visible field or a form option that lets anybody self-select as a VIP. It will be selected, constantly, and by the wrong people.
Testing and documenting
Two habits separate a workflow that survives from one that decays.
Test with real tickets in a sandbox if you have one, and always end to end rather than component by component. Create a ticket, let it route, let it sit until the automation fires, click the macro. Then read the ticket events to see exactly what ran in what order. Half of all workflow bugs are two rules fighting, and the events log shows you that in seconds.
Document it in one place, outside Zendesk. A short page per workflow naming the components, the tags they depend on and the person who owns it. Tags are the connective tissue in every example above, and an undocumented tag is a landmine for whoever inherits your account.
Frequently asked questions
What does a complete Zendesk ticket workflow look like?
Intake and routing, a pending chase, an escalation path and an auto-close. A Zendesk ticket workflow that covers those four, and nothing else, will outlast most of what teams build in year one.
Should this be a trigger, an automation or a macro?
A trigger if it reacts to something happening. An automation if it depends on time passing with nothing happening. A macro if a human needs to judge whether it applies.
How do I stop an automation firing repeatedly?
Have it add a tag, then include "tags do not contain that tag" in its conditions. Without a guard, a time-based automation will keep matching on every cycle.
What is the most common Zendesk workflow mistake?
No catch-all routing rule. Tickets that match nothing end up with no group, appear in no queue and go unnoticed until somebody complains.
How do I debug a workflow that misbehaves?
Open the ticket, switch the feed to show all events, and read which rules fired in which order. Most problems are two rules fighting over the same field.
How many triggers is too many?
When nobody can predict the outcome of a change, you have too many. Consolidate with tags, order them deliberately and name them so related rules sit together.
The step no workflow can automate
No trigger can see that two tickets are the same request. Ticket Merger runs that check on every ticket, before it reaches your queue.
Start free trial14-day free trial. No credit card required.