Asaf Krenzler

Hi Shawna,

I'd like to ask if there is any update regarding this issue.

Thanks in advanced :)

Agreed with the use case as well, I mentioned it as well here. 

Hi, let me use the product feedback template to explain my issue.

Please give a quick overview of your product feature request or feedback and note who in your org is affected by this issue [ex. agents, admins, customers, etc.]. (2-3 sentences)

I wold like to push out of zendesk, through webhook, the entire ticket data as it is fetched in the search endpoint.

What problem do you see this solving? (1-2 sentences) 

Currently all operation (BI, Production) use fetch requests for tickets, and in cases of huge amount of ticket the BI operation may block prod due to rate limit. Hence, using webhook to write the ticket data to a queue for example, for BI usage, won't affect the rate limit of Zendesk,

When was the last time you were affected by this lack of functionality, or specific tool? What happened? How often does this problem occur and how does this impact your business? (3-4 sentences)

In some cases, when there is a production issue in the company systems, a huge amount of Zendesk tickets are being created, and when BI and Prod operations are fetching tickets, we quickly reach the rate limit, and all our programmatic usage in Zendesk is down.

Are you currently using a workaround to solve this problem? (If yes, please explain) (1-2 sentences)

No. 

What would be your ideal solution to this problem? How would it work or function? (1-2 sentences)

To easily be able to push the entire ticket data, by using syntax like {{ticket}} or {{ticket.json}} in the trigger activating the webhook expecting the ticket body. The alternative is to manually write all the special syntax items ({{ticket.custom_field_value_xxx}} for example), which is not convenient at all.

Hi,

I'd like to know if there is any way, or if one can be created by your end, to monitor our api activity and alert when we are getting close to the limit, in order to proactively react to the issue, and not just after we receive a lot of 429 api errors.

Thanks.

Hi,

I have a use-case where I need to store all of the ticket data on every update.

I'd like to do it using a trigger which activates a webhook that receives the fully ticket json object, as it is fetched in the search endpoint for example. I'd like to have an option to use something like {{ticket}} or {{ticket.json}} as a simple command when building the request body,  that encapsulate the entire ticket object.

Thanks in advanced :)