A webhook sends an HTTPS POST to your server each time something happens in your workspace, such as a new message, a contact update or a paid order. You create an endpoint (your URL), choose the event types it listens to, and verify each delivery with the endpoint's signing secret.
Where to find it
Settings → App → Developers. This opens Webhooks, with these pages in its own sidebar: Endpoints, Event types, Events, Deliveries and Health.
You need the Manage Webhooks permission. Managers have it; other staff can be given it.
Before you start
Webhooks must be included in your plan. There is no separate switch in Settings: when your plan includes webhooks, the Developers entry appears for people with Manage Webhooks; when it does not, the entry is hidden.
Have an HTTPS URL on a public host that accepts POST requests and answers within 30 seconds.
Decide which events you need. The Event types page lists the live catalog with a sample payload for each.
Steps
Create an endpoint
Open Settings → App → Developers
On Endpoints, click Add endpoint
Enter the Endpoint URL
It must start with https://.
Optional: add a description (up to 500 characters), for example "Production order events endpoint"
Under Event types, click Select event types and tick at least one
Optional: under Custom headers, click Add header to send your own header (for example an auth header your server expects)
Click Create endpoint
In Endpoint created — save your signing secret, click Copy and store the secret on your server
Tick I have saved this signing secret. I understand it will not be shown again. and click Continue to endpoint
Send a test event
Open Event types and pick an event type
Click Send test event
Choose the Target endpoint and send
A synthetic event is delivered, signed with the endpoint's current secret.
Check the result under Deliveries
Change what an endpoint listens to
Open the endpoint and go to Subscriptions
Add or remove event types
Click Save changes
An endpoint with no event types receives nothing.
Disable, rotate the secret or delete
On the endpoint, open Settings:
Status: click Disable endpoint or Enable endpoint. While disabled, no events are delivered ("This endpoint is disabled. No events will be delivered.").
Rotate signing secret → Rotate secret: makes a new signing secret. The old one keeps working for 24 hours, so update your server within that time. Copy the new secret from New signing secret — save it now.
Delete endpoint: removes the endpoint and all its subscriptions after you confirm in Delete this endpoint?. This cannot be undone.
Event catalog
Events are named <resource>.<action> with a version, for example contact.created/1. Categories include:
This list is a snapshot. The Event types page in the panel and the portal's Event catalog show the current catalog, with payloads.
Limits and plans
Webhooks depend on your plan (webhook). Check Billing → Current Plan.
Your plan can also set how many endpoints you may have (webhook.endpoints) and how many deliveries per second are sent (webhook.rate_per_sec). When it does, both appear on Billing → Current Plan under Plan Usage, in the AI agents & webhooks card: Webhook endpoints as used / limit, Webhook deliveries per second as a plan value. Over the endpoint limit the card says "You're over your plan — existing items keep working; you can't add more." See Plan limits.
Your server must answer with a 2xx within 30 seconds.
Endpoints made in the panel receive only the event's data object as the body; the event id, type and time come in headers. Endpoints made through the API get a full envelope by default. The signature always covers the exact body you receive.
Some header names are reserved and cannot be used as custom headers: names starting Webhook-, Wc- or Proxy-, and Content-Type, Content-Length, Content-Encoding, Host, User-Agent, Idempotency-Key and hop-by-hop headers.
The URL must be a public host. Deliveries to private or internal addresses are blocked.
You can add the same URL twice; the form warns you, but allows it.
Subscribe to endpoint.disabled on a second endpoint so you are told if the first one is switched off.
For simple jobs (send a template or start a chatbot when an event arrives) you may not need your own server. Tip: an automation or an AI agent with a webhook trigger can do it inside the platform.