Articles on: CRM Integrations

Webhook Auto-Disabled Email: What it Means and How to Fix It

Understand why LeadTruffle disabled an outgoing webhook after repeated failures, and how to reconnect it and re-enable delivery.

Table of contents



Overview


LeadTruffle sends the webhook auto-disabled email when one of your enabled outgoing webhooks fails repeatedly. The current threshold is 10 failed delivery attempts within 24 hours.

A few things to know about this email:

  • It's sent only when LeadTruffle switches the webhook from enabled to disabled — not for every individual failure.
  • It will not be sent again for a webhook that's already disabled.
  • It goes to everyone subscribed to General Notifications for your company.


The latest error shown in the email usually tells you what went wrong — for example, an HTTP error status, a timeout, a deleted endpoint, or a Zapier-side issue. Keep it handy when troubleshooting.

What counts as a failure


A webhook delivery failure means LeadTruffle tried to send a webhook event to your configured URL, but the destination didn't accept it successfully.

Common causes include:

  • The Zapier Zap connected to the webhook was turned off.
  • The Zap was deleted or rebuilt, so the old webhook URL is no longer valid.
  • Zapier returned an error on the catch-hook step or a later step.
  • The destination returned a non-success status, timed out, or couldn't be reached.
  • The receiving system changed its authentication, rate limits, or request validation rules.


For Zapier-backed webhooks, the first thing to check is almost always whether the Zap is still turned on and whether LeadTruffle is still using the current Zapier webhook URL.

How to fix it


  1. Open the Zapier Zap or destination app connected to the webhook.
  2. Confirm the Zap is turned on.
  3. Check the Zap history (or your destination's logs) for errors around the time the LeadTruffle email was sent.
  4. If the Zap was rebuilt, copy the current webhook URL from Zapier and update the webhook URL in LeadTruffle.
  5. Fix any Zapier step errors, missing account connections, changed fields, or destination-app authentication issues.
  6. In LeadTruffle, go to API & Webhooks, confirm the webhook URL and event type, then re-enable the webhook.
  7. Trigger a new test event — or wait for the next real event — to confirm the webhook now succeeds.


Not sure what failed? Send the support team the latest error shown in the email along with a screenshot of the relevant Zap history entry, and we'll help you pinpoint it.

What this affects


Disabling a webhook only stops outgoing webhook delivery. By itself, it does not disable lead capture, AI follow-up, or your inbox — those keep working normally.


In other words, leads are still coming in and the AI is still responding. The only thing paused is the data being pushed out to your connected destination, until you re-enable the webhook.

Need help? Contact us at support@leadtruffle.com or message the team via the chat on this article or in-app.

Updated on: 09/06/2026

Was this article helpful?

Share your feedback

Cancel

Thank you!