Build a webhook workflow

Use a webhook to pass call events into a workflow your business controls. Start with one event and one destination. Do not enable customer messages or downstream writes until the entire route has been tested.

Prepare the receiving endpoint

Your endpoint must receive the raw request body and signature header. Verify the signature before parsing or acting on the payload. Save the delivery ID to prevent repeat actions when a delivery is retried.

If an automation tool’s incoming hook cannot expose raw bytes and headers or verify the signature correctly, put a verified receiver in front of it. A secret-looking hook URL alone does not validate that an event came from Xaller.ai.

Map only what you need

Use the event type, delivery ID, call ID, and dashboard link first. Add optional fields only after checking they exist. Minimal payloads deliberately omit caller details and summaries. Do not require optional fields on every event.

For example, create an internal follow-up task for a completed call requiring a response. Give it the call ID and dashboard link. Do not infer a confirmed booking from an appointment request.

Verify the full route

1. Send a test delivery to a non-customer destination.
2. Confirm valid signatures are accepted and tampered requests are rejected.
3. Replay the same delivery ID and confirm it creates no duplicate action.
4. Test a minimal payload and a missing optional field.
5. Make a controlled call and confirm the expected event reaches the final destination.
6. Disable the workflow and verify no unwanted actions continue.

The webhook reference includes executable Node.js and Python verification examples. Treat tool-specific recipes as unverified until you complete a test delivery in your own account.