What's the Difference Between Automations and Triggers in Zendesk?

Triggers run on events and automations run on time: a Zendesk trigger fires the instant a ticket is created or updated, while an automation runs once every hour on every ticket that isn't closed and acts when a time condition such as "Hours since solved is 96" becomes true. Both are Zendesk business rules and share the same conditions-and-actions builder, which is why they get confused. The mechanics below are checked against Zendesk's own documentation in September 2026, including the limits that decide how far an automation can scale.

What is the core difference between triggers and automations?

In Zendesk's own words, a trigger "runs every time a ticket is created or updated and takes action if the changes in the ticket match the conditions," while automations "run every hour on all your tickets that are not closed." That single difference, event vs. clock, is the thing to internalize.

What is a Zendesk trigger?

A trigger watches for something happening to a ticket and reacts on the spot. The moment a ticket is created or updated (a new email arrives, an agent changes the status, a field is set, a tag is added), Zendesk runs your triggers in order and any whose conditions match fire immediately. There's no waiting and no schedule; the action is effectively instant.

Because they're event-based, triggers are how you handle anything that should happen right now:

• Auto-acknowledge new tickets: send the "we got your request" email the second a ticket is created.
• Route on arrival: if the subject contains "refund," assign to the Billing group and add a refund tag.
• Set priority from signal: if the requester is on a VIP organization, set priority to High immediately.
• Notify on escalation: when priority changes to Urgent, ping the on-call group in Slack/email.

For the full builder walkthrough (conditions, actions, ordering, and the "any vs. all" logic), see Zendesk triggers explained. The one thing to remember here: a trigger only ever runs because the ticket changed. If nothing happens to a ticket, no trigger touches it.

What is a Zendesk automation?

An automation is the time-based cousin. Instead of reacting to a change, it acts when time has passed. Zendesk runs all your automations, first to last, once every hour, checking every non-closed ticket to see whether any now meet a time-based condition. When one does, the automation fires its actions.

That's why every automation must include a time-based condition: something that measures elapsed time, like "Hours since solved (calendar) is 24" or "Hours since created is greater than 8." Without a measure of time, there's nothing for the hourly check to evaluate, and the rule isn't a valid automation. This is the single biggest conceptual difference from triggers: a trigger is started by an event; an automation is started by the clock catching up to a condition you set.

The cleanest example is the one Zendesk ships by default: "Close ticket 4 days after status is set to solved." Its time condition is "Hours since solved is 96" (four days). Every hour, Zendesk looks at solved tickets, finds the ones that have been solved for at least 96 hours, and closes them. Nobody clicks anything; time does the work.

Typical jobs for automations:

• Auto-close solved tickets: the default 4-day close, so resolved work doesn't linger forever.
• Pending reminders: if a ticket has been Pending (waiting on the customer) for 24 hours, send a gentle nudge; after 72 hours with no reply, solve it.
• SLA-style escalation: if a ticket has been Open and unassigned for 8 business hours, bump priority and notify a lead.
• Inactivity follow-ups: if no agent has touched a High-priority ticket in 4 hours, flag it.

Two of those actions, Pending and Solved, depend on ticket statuses, which is why automations and statuses are so tightly linked: most time-based rules key off "how long has this ticket been in this status." Automations are available on every current plan: Suite Team, Growth, Professional, Enterprise and Enterprise Plus, and Support Team, Professional and Enterprise.

When should you use a trigger or an automation?

The decision rule is short:

• Does it need to happen the instant something changes? Use a trigger. New ticket created, status flipped, field set, tag added: anything where "now" matters.
• Does it need to happen after a delay, or only once time has elapsed? Use an automation. Follow-ups, reminders, escalations, and auto-close all live here.

A useful gut check: if your sentence contains the word "when" ("when a ticket is created…"), you probably want a trigger. If it contains "after" or "if it's been X hours/days" ("after 3 days with no reply…"), you want an automation.

How do triggers and automations work together on one ticket?

In practice you rarely choose one; triggers and automations tag-team across a ticket's life. A single Pending-reminder workflow is the classic pattern:

1. Trigger (event): an agent sets the ticket to Pending and replies asking for more info. The instant they hit submit, a trigger could tag the ticket awaiting-customer.
2. Automation (time): 24 hours later, with the ticket still Pending and no customer reply, an automation sends a polite reminder and adds a reminder-sent tag.
3. Automation (time): 72 hours after that with still no reply, a second automation sets the ticket to Solved.
4. Automation (time): four days after Solved, the default close automation closes it for good.
5. Trigger (event): if the customer does reply at any point, that update is an event: a trigger (or Zendesk's built-in behavior) flips Pending back to Open and the agent picks it up again.

Notice the rhythm: triggers handle the moments of change, automations handle the gaps in between. Together they let a ticket move itself through its lifecycle with no one babysitting it.

What limits and delays apply to automations?

This is where new admins get burned, so it's worth being precise.

Automations are not real-time. Because the cycle runs hourly, an automation can fire up to about an hour after its condition technically becomes true. "Close 4 days after solved" might actually close a ticket 4 days and 40 minutes after it was solved. That's fine for reminders and closes; it's not fine if you need split-second precision. For anything that must happen the instant a ticket changes, use a trigger.

An automation must change something to stop re-running. Since the automation re-checks every non-closed ticket every hour, a rule whose condition stays true would fire over and over, sending the same reminder email hour after hour. Zendesk prevents this by requiring every automation to include at least one action that nullifies one of its own conditions (so the ticket no longer matches next cycle), or a condition that can only ever be true once. The standard pattern is a tag: the reminder automation requires reminder-sent to be absent in its conditions and adds reminder-sent as an action, so after it fires once, the ticket fails the condition and is skipped on every future pass. If you forget this, you'll get a runaway automation that spams customers; if you build it right, it fires exactly once.

Automations ignore closed tickets. The hourly pass only looks at tickets that aren't closed, so don't expect an automation to act on a finalized ticket.

Automations have hard volume limits. Zendesk allows 500 active automations per account, and each automation can act on at most 1,000 tickets per hour. If a rule matches 3,000 tickets at once, say after a bulk import, it takes three hourly cycles to work through them. A single ticket can also be updated by automations at most 100 times, apart from the close action (Zendesk: About automations).

What mistakes do admins make with triggers and automations?

• Building a "trigger" that needs to wait. If your rule is really "after 2 days, do X," a trigger can't do it: there's no event two days from now. It has to be an automation.
• Forgetting the time condition. An automation with no elapsed-time condition won't validate (or won't behave). Every automation needs something like "Hours since…".
• Forgetting the off-switch. No condition-nullifying action (or once-only condition) = the automation re-fires every hour. Add the reminder-sent-style tag.
• Expecting instant results from an automation. It can lag up to about an hour. Don't use one where timing must be exact.
• Confusing automations with macros. A macro is a manual, one-click bundle an agent applies on demand. It isn't automatic at all, despite the name. Automations and triggers run on their own; macros wait for a human.
• Stacking too many overlapping rules. With triggers running on every update and automations sweeping hourly, conflicting rules can fight each other. Keep them few, named clearly, and ordered deliberately.

Where does AI fit alongside triggers and automations?

Triggers and automations are good at the predictable: "if this exact condition, do this exact thing." What they can't do is read a messy customer email, figure out what the person actually wants, and write a useful answer. A trigger can route a ticket containing the word "refund," but it can't tell an angry refund request from a routine one, or draft the reply.

That's the gap an AI agent layer like Macha fills. It sits on top of your existing Zendesk (it's not a help desk and not a replacement for one) and handles the judgment calls your rules can't: reading intent, classifying and triaging nuanced tickets, drafting replies for an agent to approve, and resolving routine requests end to end, while anything ambiguous stays a normal ticket for a human. The honest framing: keep your triggers and automations doing the deterministic plumbing they're great at, and let the AI handle the parts that need understanding rather than a hard-coded condition.

Worth knowing on cost, since it differs from rules (which are free): Macha bills per ticket: one conversation, charged once, whether the agent summarizes, tags, routes, drafts or resolves. It's one plan priced by volume, from $299 a month for 750 tickets, and not per resolution, so the bill never hangs on an outcome definition you don't control. If you want to see where rules end and AI begins, we walk through it in how to automate Zendesk with AI. You can also try it free with $50 of free usage, no credit card required.

Frequently asked questions

What's the difference between automations and triggers in Zendesk? Triggers are event-based: they run the instant a ticket is created or updated and act if the change matches their conditions. Automations are time-based: they run on a schedule (every hour) and act once a time-based condition is met, such as "24 hours since the ticket was solved." Triggers handle instant reactions; automations handle anything that should happen after a delay.

What is a Zendesk automation? A Zendesk automation is a time-based business rule that runs automatically once every hour, checking your non-closed tickets and performing actions when a time condition comes true. The default example is "Close ticket 4 days after status is set to solved." Every automation must include a condition that measures elapsed time.

How often do Zendesk automations run? Zendesk runs all automations, first to last, once every hour on every ticket that isn't closed. This means automations aren't real-time: an action can fire up to about an hour after its condition technically becomes true.

Why does my Zendesk automation keep firing repeatedly? Because its condition stays true on every hourly pass. Every automation needs at least one action that cancels one of its own conditions (or a condition that can only be true once) so the ticket stops matching after it fires. The common fix is to add a tag like reminder-sent as an action and require that tag to be absent in the conditions.

Can a trigger do something after a time delay? No. Triggers only run in response to a ticket event (create or update), so they can't "wait." Anything that must happen after time has passed (a follow-up, an escalation, an auto-close) needs an automation.

Do automations run on closed tickets? No. The hourly automation pass only evaluates tickets that aren't closed, so a closed ticket is never acted on by an automation.

How many automations can a Zendesk account have? Up to 500 active automations. Each one can act on at most 1,000 tickets per hour, and automations can update a single ticket at most 100 times, except for the close action. Go deeper on triggers, macros and ticket statuses to see how the rest of the rules system fits around them.

Mechanics and limits checked against Zendesk's official documentation on 24 September 2026. Zendesk updates its product periodically, so confirm specifics in your own account before relying on them.