Webhooks
Push signed HUM events — calls, voicemails, SMS, conversations — into your own systems.
Webhooks deliver HUM events to your systems the moment they happen.
Setting up a webhook
Under Settings, add a webhook endpoint: your URL, the events to subscribe to, and optional custom headers. HUM returns a signing secret — store it like a credential.
Events
Subscribe to the events you care about, including:
- Voice — call completed, outcome captured, flow switched, voicemail received.
- Messaging — SMS received/sent/delivered/failed, opt-out and opt-in, conversation started/assigned/closed.
Each delivery is a JSON payload describing the event and the entities involved.
Verifying deliveries
Every delivery is signed with your endpoint's secret. Verify the signature on the raw request body before trusting the payload, and rotate the secret if it's ever exposed.
Operating webhooks
- Use test deliveries to validate your receiver end to end.
- Delivery history shows each attempt, response code, and timing.
- Failed deliveries retry automatically; you can redeliver manually while debugging.
Templates and inbound triggers
Webhook templates pre-fill common receiver setups. In the other direction, inbound trigger URLs let external systems fire events into HUM to run event-triggered agents — see AI Agents.