Question
I want to update tickets using a trigger or automation. The ticket attributes I want to update are not accessible using business rules. I can make the update successfully using the Support API. Can I have the trigger or automation notify a target that updates the ticket through the API?
Answer
No, this workflow is not recommended or supported. When a ticket is updated by business rules and the API simultaneously, errors are likely to occur. When this happens, it is called a race condition.
Every time a ticket is created or updated, all your business rules run in a cycle against that ticket. For instance, triggers fire and update the ticket if their conditions are met during the cycle. A cycle is the entire process of a ticket being checked against all your triggers. For more information, see the article: How do triggers run according to theirs position on the trigger page?
When a trigger updates a ticket using the API, the update occurs at some indeterminate point in the cycle. Results can vary based on when the ticket update occurs in the cycle. The ticket update can affect whether other business rules fire.
5 Comments
Seems to me like it should be OK to try these practices (as there is no safe, built in functionality), and if there are issues, just cancel the trigger or automation.
Hi David,
You are correct and it's OK to try using a trigger and target to update your ticket. In some cases it will work and others it will not. We just set the expectation that if any issues should occur it's most likely due to this unsupported workflow. As you stated you can just disable the trigger/automation if any issues should come up.
Cheers!
Hi All,
I am fairly new to Zendesk, and i am vastly disappointed in seeing small functions not implemented in Zendesk, especially for the customers. Most of the applications we looked at had basic functionality that Zendesk does not provide and has not over the years by what i am reading. Simple things like, the order the messages are laid out in the ticket, extra fields (custom), sorting, exporting, reporting, etc.
We resort to implement whatever we can to make our customers happy since we rely on the SLA from our customers contract. Basically, we are forced to use like the target triggers to resolve something Zendesk should be providing in the first place.
For me, the target triggers work wonderfully, i use it to capture the 1st SLA - Customer Acknowledgement in the public reply of the ticket. Most of our customers are Airlines, and you could imagine the million emails received by them. This is where they go to ensure that an email was sent acknowledging their issue.
I believe, criticism on what we are doing does not help us find a solution to the inadequacy functions of Zendesk. We understand there are limitations, but then push for a better Zendesk Customer Experience!
Thanks,
Yami
Hello Christopher,
I want to use trigger to add value in text ticket fields but it is impossible.
It's only possible if you have a list ticket field but not "text" ticket field.
Will you add it ?
Thanks,
Hello Corentin D,
Appreciate the insight you shared on this product limitation. I would recommend posting your request in our product feedback forums so our developers can consider your use case for future updates.
Best regards.
Please sign in to leave a comment.