The escape hatch from our integrations
You are never limited to the CRMs we happen to support. Anything that accepts an HTTP request can receive the same data.
From October 1, WhatsApp charges for every business reply. Read the migration playbook
Webhooks
When a conversation ends, a lead qualifies or a browser task finishes, your systems should not have to find out by polling. Point a webhook at your endpoint and the event arrives as it happens.
What it does
Your systems, told the moment something happens.
You are never limited to the CRMs we happen to support. Anything that accepts an HTTP request can receive the same data.
Every event type ships with its shape and a sample, so you build against something concrete rather than reverse-engineering a first delivery.
Subscribe each endpoint to only the events it needs, instead of filtering a firehose on your side.
The REST API covers what webhooks do not, so you can reconcile state as well as react to events.
Use cases
Three jobs this does the day you turn it on.
Webhooks
Point it at your URL in Integrations and choose the events it should receive.
Read the documented payload for each event and build your handler against it.
Events start arriving as conversations, leads and tasks happen.
Still wondering? Ask our agent; it answers from these same pages.
Keep exploring