Outbound webhooks are included on the Agency Plus plan.
Add a webhook
- Enter an Endpoint URL. It must be
https://. - Leave All events (*) on, or turn it off and choose specific events.
- Click Create webhook, then reveal and copy its Secret. It is shown once.
Events
A few worth knowing:
message.classifiedfires once a reply has been read and given an intent (interested,question,not_now,not_interested,ooo,wrong_person,unclear). This is the one to use for “new interested reply”.sequence.stalledandsender.running_dryare the alerts.sequence.recoveredfires when a stall clears.meeting.bookedcarrieslead_id,sender_id,provider,starts_atandbooking_id.sequence.webhookis sent by the Call webhook step inside a sequence.
GET /v1/leads/{id} or GET /v1/threads/{id}.
Verifying requests
Each delivery is a JSONPOST with three headers:
x-delivery-id to drop duplicates.
Retries and failures
- Answer with a 2xx within 10 seconds.
- A failed delivery is retried up to 5 times, with the wait doubling each time (about 2, 4, 8, then 16 minutes).
- A webhook is switched off automatically after 50 failures in a row. Turn it back on from the list; this resets the failure count.
- Recent deliveries shows the last 100 attempts with status code, attempts and last error. Records are kept for 30 days.
Replay a delivery
If your endpoint was down, or you fixed a bug and want the event again, click Replay on any delivery. A replay is a new delivery carrying the same payload plus"replayed": true and "replay_of": <original id>. It goes out within about 30 seconds and is signed like any other.
The same thing through the API: