Skip to content
LeadPattern
Webhooks & API

Webhooks Overview

LeadPattern webhooks send real-time events, such as new messages, chat assignments and calls, to your own server as signed HTTPS POST requests.

3 min readUpdated Oct 7, 2026

A webhook tells LeadPattern to call your server whenever something happens in your workspace. A customer sends a message, a chat is assigned or a call ends, and LeadPattern sends a POST request with the details to a URL you choose. You can use webhooks to keep a CRM, data warehouse or internal tool in sync without polling the API.

How it works

1

You register an endpoint

On the Webhooks page, give the webhook a name and an endpoint URL, and pick the events it should receive.

2

An event happens

For example, a customer replies on WhatsApp, which fires the Message Received event.

3

LeadPattern delivers it

LeadPattern sends a JSON POST to your URL. If you turned on signing, it carries a signature so you can check that LeadPattern sent it.

4

Your server acknowledges

Return any 2xx status within 10 seconds. Failed deliveries are retried automatically.

Where to find webhooks

Open Webhooks in the left sidebar. The page lists every webhook in the workspace with its URL, how many events it listens to, and its status. If your plan limits webhooks, the page also shows how many you've used, for example 2 of 3 webhooks used. Only active webhooks count toward the limit.

Who can use webhooks

Two permissions on Roles & Permissions control access:

PermissionWhat it allows
View Webhooks & Delivery LogsSee the Webhooks page and open each webhook's delivery logs.
Create / Update / Delete WebhooksCreate, edit, pause, delete and test webhooks, manage signing secrets, and view delivery payloads. Granting it also grants View Webhooks & Delivery Logs.

Owners always have both. See Roles & Permissions.

Good to know

  • At-least-once delivery. An event can occasionally arrive more than once, or out of order. Every delivery carries a unique event id in the X-Webhook-Id header, so you can skip duplicates.
  • Signed by default. New webhooks sign every delivery unless you switch signing off. Always verify signatures in production.
  • Paused when the workspace is restricted. If a workspace is restricted, or blocked for billing, LeadPattern sends no webhook deliveries until it's back in good standing.
  • Full API reference. The request and response formats for managing webhooks through the public API are in the developer API docs.

What's next

Create a webhookRegister an endpoint, choose events and turn on signing.Webhook eventsAll 41 events and the payload envelope.Verify signaturesNode.js and Python examples.Logs & retriesWhat happens when a delivery fails.

Was this article helpful?

Your feedback helps us continuously improve our documentation.

Need more help with this topic?Ask LeadPattern Support

Related Articles

Webhooks & API

Create a Webhook

Register a webhook endpoint in LeadPattern, choose the events it receives, sign deliveries with a secret, and send a test before saving.

Read article
Webhooks & API

Webhook Events

The 41 LeadPattern webhook events (messages, conversations, contacts, notes, flows, calls and WooCommerce) and the envelope every delivery uses.

Read article
Webhooks & API

Verify Webhook Signatures

Why you should sign LeadPattern webhook deliveries, how to turn signing on, and how to verify the HMAC-SHA256 X-Webhook-Signature headers, with Node.js and Python examples that handle secret rotation.

Read article
Webhooks & API

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.

Read article