Webhooks Failure


  • Zach Anthony
    Zendesk Product Manager

    Hey there! While it is not possible today, these are problems that we are considering for future development. Some things we are interested in understanding is who should be notified of a failure (e.g. all admins, just the account owner etc.) and what types of failures are worth alerting on.

    We would love to hear more about if you have any thoughts about what you would expect for your use cases.

  • Admin Zendesk

    Hello, I think an admin or end user can be alerted. On my side, we have technical admin that take in charge complex triggers, html format, routing, Webhooks, integration... and production admin that take care of views, workflow.

    I think technical admins need to be alerted, and maybe a end user as webhhoks is used on our side to send information from Zendesk to other tools. This other tools admin can be put in Zendesk as end user to be alerted.

    I think a message can be sent for each failure with the error code detected.


  • Nathan Purcell

    Weighing in here as I'm about to cross the webhook bridge too. 

    Notifiable users should be definable on the individual webhook. It should not be a global setting as it's perfectly feasible for webhooks to be related to completely different departments. I'd suggest a free-text box allowing the creator to enter comma-separated email addresses (which also allows us to notify monitoring systems etc. )

    I'm also interested to know how a fail webhook call affects subsequent triggers? 
    What happens if I have a trigger with two actions: 1 to call a webhooks and 1 to apply a tag. If the webhook fails, is the tag applied? 

  • Zach Anthony
    Zendesk Product Manager

    Thanks for the feedback. This definitely helps us understand what would be most valuable in terms of configuring notifications.

    Nathan Purcell in terms of your question around webhook failures, the scenario you described should result in the tag being applied. This is because when a business rule fires a webhook, it queues the webhook job to be run but doesn't actually run the job immediately. After queueing the webhook job, the business rule (trigger) will continue processing.

    Hope this helps!

  • David

    We need this.

    On multiple clients, we've had to mitigate this with temporary solutions using tagging logic to determine if the webhook was fired successfully or not. But it's not very scaleable. 

  • Greg Clapp

    Upvoting this. I'm currently trying to determine whether my organization can even use webhooks, given that there's no way to be alerted of endpoint failures except for someone to check the activity log of every webhook every day, which is not sustainable. It would be especially useful if webhook failures after the standard 3 retries could be used as a trigger condition, so we can decide how we want to handle the failure...notify someone, log it, etc.

  • Chia-Piyasakul, Karnrawee

    Voting for this feature too. My team would love to have alert of webhook because we realized the webhook failure when we checked by ourselves or someone noticed the behavior changing.

  • Stephen

    This would be incredibly helpful. We had a case recently where a webhook started to fail for several days as a result of a change on another system and we only became alerted to this when internal staff noticed a business critical function stopped working...

    I see this functionality in Hubspot / Jira - Zendesk desperately need this.

  • Molly Katolas
    Zendesk Luminary

    We have several mission-critical integrations with Zendesk and this makes it hard to rely on when I get error notifications from every system except Zendesk. I'd like to be able to set up the notifications on a per-webhook basis. Some I don't need to be notified about, but others I need an email directly (or even better, the option to be notified via another method, like Slack). 


Please sign in to leave a comment.

Powered by Zendesk