Free tools Windows power users keep installed
One-click scans. No signup required.
In Zendesk, a ticket trigger is an event-based rule: it checks a ticket immediately after creation or update and performs configured actions when the ticket matches its conditions. To build one, choose the event and qualifying ticket state, define the outcome, then check its position relative to other triggers and test it against representative tickets.
Choose the right Zendesk workflow mechanism
Triggers, automations, macros, and action flows solve different problems. Choose according to what starts the work and how much the workflow needs to do.
As an Amazon Associate I earn from qualifying purchases.
| Mechanism | What starts it | Best fit | Timing and repeat behavior |
|---|---|---|---|
| Ticket trigger | Ticket creation or update that matches configured conditions | Immediate, single-rule responses such as routing or notifying | Runs immediately after the event. Trigger order and changes made by earlier rules can affect later matches. |
| Automation | An elapsed-time condition on a ticket | Delayed work, such as acting on a solved ticket after a period | Runs hourly on non-closed tickets. Configure a condition that becomes false or an action that nullifies a condition to prevent repeated work. |
| Macro | An agent applies it | A repeatable shortcut that still requires an agent to choose it | Not an automatic reaction to a ticket event or elapsed time. |
| Action flow | A configured flow trigger | Multi-step or branched work, especially when it involves external systems | Can use branches, loops, custom code, and actions. Action-credit allowances depend on the account plan. |
Zendesk’s documentation describes triggers as rules that run immediately after a ticket is created or updated and perform actions when conditions match. For more complex examples of action flows, Zendesk describes a flow that updates a ticket’s priority, creates and links a Jira issue, and sends a Slack message.
How to create a ticket trigger
You need admin permissions or an agent custom role with the required permission. Names and available fields or actions can vary by account, so use the options shown in your Admin Center.
#1 Best Overall
- Open the trigger settings. In Admin Center, go to Objects and rules > Business rules > Triggers, then create a ticket trigger.
- Name and organize the rule. Give it a descriptive name; add a description and category where useful. A consistent naming pattern helps administrators recognize related rules and understand their intended purpose.
- Define when it qualifies. Add conditions for the event and ticket state. Choose whether all conditions or any conditions must match, then set each condition’s field, operator, and value. Be precise: broad conditions can make a rule affect tickets beyond the intended group.
- Choose what happens. Add actions, such as changing ticket properties or sending a notification. Confirm the actual fields and actions available in your account rather than assuming every option is enabled.
- Review the order and interactions. Check the trigger’s position alongside related rules. An earlier trigger can change a ticket field or tag, which may make a later trigger match—or prevent it from matching. Use conditions and actions that make the intended sequence predictable.
- Validate before relying on it. Check representative ticket states that should match and should not match. Observe the resulting changes and notifications before relying on the rule for customer-facing communication.
Build conditions and actions around the outcome
Think of conditions as the “if” and actions as the “then.” Conditions narrow the rule to the intended ticket; actions implement the response. A reliable trigger has a clear event, a specific qualifying state, and an outcome that does not conflict with related rules.
Use all versus any deliberately
Choose all when every condition must be true—for example, when both the ticket’s event and a particular property must match. Choose any when any one of several alternatives should qualify. Review the resulting logic as a whole: a single broad alternative in an “any” group can cause tickets to qualify unexpectedly.
Be careful with ticket text conditions
A community discussion asks how to set up a trigger that considers the body of an incoming email. That question does not by itself establish which text-matching fields are available in every Zendesk account or plan. Inspect the condition fields and operators offered in your trigger editor and confirm behavior using representative incoming messages before deploying a rule based on ticket text.
Do these 3 things before closing this tab:
1Scan for outdated or missing drivers - takes under a minute2Repair Windows errors before they cause bigger problems3Fix the driver behind crashes, sound loss and screen glitchesAccount for trigger order
Triggers do not operate in isolation. If one rule changes a field or adds a tag, a later rule evaluates the ticket after that change. Review related rules together, especially when multiple rules route, prioritize, tag, or notify on similar tickets. Zendesk’s developer documentation discusses trigger order and how triggers are evaluated.
Practical trigger workflows
Notify a requester that a request arrived
Zendesk’s workflow guide describes a standard “Notify requester of received request” trigger: conditions include a created ticket and a status other than Solved, and an action emails the requester. Treat that as a documented example, not a guarantee that every account currently has identical defaults. Inspect the trigger in your account, confirm its conditions and recipient, and ensure related rules do not send duplicate messages.
Route tickets using requester domain or description keywords
Zendesk’s workflow guide identifies requester email domains and keywords in a ticket description as possible bases for automatic assignment. Keep the qualifying conditions focused on the intended organization or issue, and verify that the resulting assignment is correct for examples both inside and outside the match.
Escalate or classify at the event
For an immediate change, use a trigger when ticket creation or an update should cause the change as soon as conditions match. For a process involving several steps, branches, or another system, consider an action flow instead. Zendesk’s documented incident example changes priority, creates and links a Jira issue, and sends a Slack notification.
When a trigger is the wrong tool
Use an automation for elapsed time
If the workflow should run after a ticket has remained in a state for a period, use an automation rather than expecting a trigger to wait. Zendesk says automations run hourly on non-closed tickets. Include a condition that becomes false or an action that nullifies a condition, so the same ticket does not keep qualifying and repeating the work.
Zendesk’s workflow guide gives closing a solved ticket after 96 hours (four days) as an automation example and best estimate. It is an illustrative workflow, not a measured performance result or a required delay.
Use a macro for agent-chosen repetition
If an agent should decide when to apply a repeatable set of changes or response steps, a macro is the better fit. Unlike a trigger or automation, it is not an automatic reaction to an event or the passage of time.
Use an action flow for multi-step work
When work needs branches, loops, custom code, or actions across Zendesk and external systems, action flows provide a more suitable structure than stacking single-purpose triggers. Zendesk documents action-credit allowances as dependent on the account plan; current access and limits are not established here.
Recommended Free Tools
Understand what triggers do with closed tickets
Triggers do not run on already-closed tickets. Zendesk documents an exception while a ticket is being set to closed, apart from automatic closure after 28 days. Design and validate rules with that lifecycle boundary in mind; a trigger should not be treated as a general way to update tickets that are already closed.
Independent reader supportYour contribution helps us test, update, and keep practical guides available for everyone.How to troubleshoot a trigger that does not behave as expected
- It never fires: Recheck the selected event, the all-versus-any setting, and every field, operator, and value. Confirm that the ticket state actually meets all required conditions.
- The wrong tickets qualify: Narrow broad conditions, particularly alternatives in an “any” group. Test both intended matches and near-misses.
- A later rule does not fire: Look for earlier triggers that alter the fields or tags the later rule checks, and review the rules’ order.
- The action is unavailable: Check the fields and actions exposed in your account. Feature availability can vary; the available documentation does not establish plan entitlements.
- A delayed action repeats or never happens: Confirm that an automation—not an immediate trigger—is being used for elapsed time, and that its conditions or actions prevent repeated matching. Automations run hourly on non-closed tickets.
- The ticket is already closed: A trigger does not run on an already-closed ticket, subject to Zendesk’s documented exception while a ticket is being set to closed apart from automatic closure after 28 days.
Sources and version notes
Zendesk’s help-center pages cited here include “About Zendesk triggers and how they work” (edited May 1, 2026) and action-flow documentation edited September 4, 2026. UI labels, available features, and plan access can change; the steps use the documented Admin Center path, while account-specific options should be confirmed in the current interface.
- Zendesk: About Zendesk triggers and how they work
- Zendesk: Creating triggers
- Zendesk: Trigger conditions and actions
- Zendesk: Developer guidance on trigger order
- Zendesk: Automations
- Zendesk: Streamlining workflows with macros, triggers, and automations
- Zendesk: Action flows
Frequently Asked Questions
Do ticket triggers run immediately?
Yes. Zendesk triggers run after a ticket is created or updated when their configured conditions match.
Can a trigger act on a ticket after a delay?
No. Use an automation for elapsed-time conditions; Zendesk says automations run hourly on non-closed tickets.
Do triggers run on closed tickets?
Not on tickets that are already closed. Zendesk documents an exception while a ticket is being set to closed, apart from automatic closure after 28 days.
What is the difference between a trigger and a macro?
A trigger runs automatically when ticket-event conditions match; an agent applies a macro as a shortcut.
Quick Recap
Product prices and availability are accurate as of the date/time indicated and are subject to change. Any price and availability information displayed on Amazon at the time of purchase will apply.
