Blog

More Error Details in Webhook Email Notifications

April 3, 2019

Carlyn Manly

1 Min Read

Click To Explore

When an external server is down, all webhooks that tried, but failed, to reach this server are now remembered as ‘offending’ webhooks. This allows Xurrent to include the name and Xurrent account ID of the offending webhooks when it sends out an email notification to the email address specified in the field ‘Mail exceptions to‘ of a webhook to warn the recipient that this webhook is being throttled or has been disabled.

An example of such an email is provided below:

To: account.owner@widget.com
From: noreply@4me.com
Subject: Webhook #179 throttled – Status Update

The webhook is throttled due to too many consecutive failures on the
external server. Could it be that the external server is down?

https://wdc.Xurrent.com/webhooks/179

https://automation.widget.com/webhooks/status-update

Offending webhooks:
Team Updated @wdc #183

This example email indicates that webhook 179 is throttled due to too much errors encountered by webhook 183, which points to the same external server. The recipient of the email notification can then look up the details of the failure by accessing webhook #183.

Partners

A Note From the Road: What SPARK Taught Me About Time

During the second SPARK event in Antwerp, I stood at the back of a training room and watched a customer build a custom integration with our new iPaaS, wiring Xurrent to another system in her stack that had never talked to it before. No services rep doing it for her. No statement of work, no project plan with a kickoff and a go-live date. Just a person with live beta access in her hands, connecting two systems by hand, and finishing it before her coffee went cold. A year ago that would have been a multi-week project with a budget attached. She looked up, a little surprised it had actually worked, and said something I have not stopped thinking about since. She said it just gave her her week back.

3 Mins

July 1, 2026

Service Management

How Long Should ITSM Implementation Really Take in 2026?

Most vendors will tell you ITSM implementation takes six months to a year — but modern, configuration-first platforms have rewritten the math entirely. See what real implementations look like in 2026, and why a long rollout is now a choice, not a given.

8 Mins

May 30, 2026