Skip to content

Manage Webhooks

Edit LeadPattern webhooks, rotate or replace signing secrets with a 24-hour grace period, pause and resume deliveries, and understand each status badge.

4 min readUpdated Oct 7, 2026

Everything here needs the Create / Update / Delete Webhooks permission. Members with only View Webhooks & Delivery Logs can see the list and open delivery logs.

Status badges

The Status column shows the state of each webhook:

BadgeMeaning
ActiveDeliveries are being sent.
Paused manuallySomeone paused the webhook. Resume it when you're ready.
Plan limitDisabled because your plan's webhook limit was reached. Delete another webhook or upgrade your plan to re-enable it.
Auto-disabled after failuresDelivery failed for 50 events in a row. The row shows the number of consecutive failed deliveries and the time of the last failure. See Logs & retries.

Next to the name you may also see:

  • Signed: deliveries carry signature headers. A clock icon means a secret was recently rotated and the previous one is still accepted.
  • Not secure: the endpoint uses http://, so deliveries aren't encrypted.

Edit a webhook

Click the Edit (pencil) icon to change the name, URL, events, headers or authorization, then click Update Webhook.

Changing the URL, custom headers, authorization or secret of an active webhook sends a test event before saving. The change is saved only if your endpoint answers with 2xx. Changing just the name or events saves straight away.

Send test works here too. With unsaved changes, it tests the form values and shows the HTTP result immediately. With no changes, it queues a test event using the saved settings, and the result appears in the delivery logs.

Signing secret

In the edit form, the Sign deliveries section shows whether the webhook is Signed or Not signed. Changes in this section are saved immediately.

Rotate secret / Generate secret

Rotate secret creates a new secret and shows it once. Copy it. The old secret keeps working for 24 hours. During that time each delivery carries signatures from both secrets: X-Webhook-Signature / X-Webhook-Signature-V2 use the new secret, and X-Webhook-Signature-Previous / X-Webhook-Signature-V2-Previous use the old one. Update your server within that window. If the webhook isn't signed yet, the button reads Generate secret.

Use my own secret…

Enter your own secret (16–128 characters) and click Save secret. It replaces the current secret immediately.

Remove secret

Stops signing. Deliveries no longer include the X-Webhook-Signature headers, so a server that checks signatures will start rejecting them. Switching Sign deliveries off does the same.

Pause, resume and delete

  • Pause / Resume. Click the pause or play icon. A paused webhook shows Paused manually and receives no events. Resuming sends a test event first, and the webhook turns back on only if your endpoint answers with 2xx. Resuming a webhook that was Auto-disabled after failures also resets the failure count, so fix the endpoint first.
  • Delete. Click the trash icon and confirm. The webhook is removed permanently, and its delivery logs are deleted after 30 days.

What's next

Was this article helpful?

Your feedback helps us continuously improve our documentation.

Need more help with this topic?Ask LeadPattern Support

Related Articles