Effect of Omitting Created/Updated Conditions in Triggers
What happens if I don't include 'Created' or 'Updated' conditions in a Zendesk trigger?
If you don't include 'Created' or 'Updated' conditions, the trigger will fire for any event, whether a ticket is created or updated.
This means the trigger will activate whenever any change occurs to a ticket, without restriction to the type of event. This can be useful if you want a trigger to apply universally to all ticket changes, but it may not be ideal if you need specific actions for different types of events.
More related questions
What is the difference between 'Ticket | Is | Created' and 'Ticket | Is | Updated' in Zendesk triggers?
The difference lies in when the trigger fires. A trigger with the condition 'Ticket | Is | Created' fires when a new ticket is created in your account. On the other hand, a trigger with the condition 'Ticket | Is | Updated' fires when an existing…
How can I make a Zendesk trigger fire for both created and updated tickets?
To make a trigger fire for both created and updated tickets, include both conditions in the 'Meet ANY of the following conditions' section of your trigger setup. This setup ensures that the trigger will activate whether a ticket is newly created or…
Is it necessary to include both 'Created' and 'Updated' conditions in Zendesk triggers?
No, it is not necessary to include both 'Created' and 'Updated' conditions for a trigger to fire. You can choose to include either one based on your workflow needs. Including both conditions is a way to ensure the trigger fires in both scenarios,…
Can I have multiple 'ANY' sections in a Zendesk trigger?
Currently, Zendesk triggers do not support having multiple 'ANY' sections within a single trigger setup. You can, however, include multiple conditions within a single 'ANY' section. This allows you to specify several conditions that, if any are…
Interested indeflectingover 70% of your Zendesk support tickets?
Zendesk Support Tickets
Zendesk Messaging (live chat)
Join1,000+ companies reducing their support costs and freeing up support agents for more important work
“We needed an AI agent integrated within our current tools. My AskAI was the only solution that wasn't going to disrupt our operations.”
Zeffy
“At the end of last year I was given the challenge - how can we provide the same or better service, without hiring anyone?”
Zinc
“My AskAI blew everybody else out of the water. It made the selection process very easy for us.”
Customer.io($50M+ ARR)
“It now resolves 71% of queries (over 35,000 every month), meaning more time solving complex issues and improving UX.”
Freecash
“We needed an AI agent integrated within our current tools. My AskAI was the only solution that wasn't going to disrupt our operations.”
Zeffy
“At the end of last year I was given the challenge - how can we provide the same or better service, without hiring anyone?”
Zinc
“My AskAI blew everybody else out of the water. It made the selection process very easy for us.”
Customer.io($50M+ ARR)
“It now resolves 71% of queries (over 35,000 every month), meaning more time solving complex issues and improving UX.”
Freecash
Reduce support costs.Spend more time on customer success.
