Question
Can I get specific usage data on macros, triggers, and automations?
Answer
Although it is not possible to pull this kind of usage data for a specific date, you can obtain usage data for macros, triggers, and automations based on the last hour, 24 hours, 7 days, or 30 days through the API. There are two different types of API calls you can make to obtain this usage data.
While managing your triggers, you can view or add columns that display how often the trigger has fired in the last 24 hours, 7 days, or 30 days. Managing macros or automations allows you to view how often they have been executed in the last 7 day period.
Option 1: Filtered API Request
Make a filtered request for each. The parameters described below are supported when filtering this information via the API.
- usage_1h
- usage_24h
- usage_7d
Example:
https://yoursubdomain.zendesk.com/api/v2/macros.json?sort_by=usage_1h,usage_24h,usage_7d
Make sure you're logged in, then select your subdomain from the dropdown below to be redirected directly to this API call in your account.
Option 2: Sideload API Request
Make a sideload request to obtain the usage data for each. Sideloading gives you an option for tracking usage over a larger amount of time by allowing you to add the parameter of 30 days to the request. The sideloading parameters described below are currently supported.
- usage_1h
- usage_24h
- usage_7d
- usage_30d
Example:
https://yoursubdomain.zendesk.com/api/v2/macros.json?include=usage_1h,usage_24h,usage_7d
5 Comments
Hi all!
Does zendesk dev team have plans for adding business rules analysis (triggers, automations ...) to Explore?
This would be useful
Hi all,
Take a look at the advanced Macros Reporting app to get a powerful macro usage analytics tool.
So no way to see what tickets caused what triggers to fire? It would make troubleshooting a whole lot easier.
Agree with you. It will be handy to see what tickets caused what triggers to fire. Unfortunately, the "Triggers" tab doesn't provide information about that.
As a technical alternative, I would like to recommend for you the following workarounds:
- Viewing all events for ticket updates. However, using this method you can check tickets only step-by-step.
- Adding special tags for each trigger into action fields and analysing a special list of what triggers to fire via "Tags" tab:
Hope it helps
Please sign in to leave a comment.