Skip to main content
TalkPilot uses webhooks to notify your systems about events in real-time. There are two webhook types: post-call webhooks and employee status webhooks.

Post-call webhooks

Configured per agent via the post_call_webhook_url field. After every completed call, TalkPilot sends a POST request to this URL with call data.

Configuration

Set the webhook URL on the agent:
Or configure it in the Dashboard under Agenten > [Agent] > Webhook.

Payload

The webhook sends a JSON payload with the call details:

Handling webhooks

Employee status webhooks

Configured in the user’s profile settings (Dashboard > Settings > Webhooks). When an employee’s forwarding rule or status changes in the Dashboard, a webhook notification is sent.

Payload

Best practices

  1. Respond with 200 quickly — Process webhook data asynchronously. TalkPilot expects a response within a few seconds.
  2. Handle duplicates — In rare cases, a webhook may be sent more than once. Use the call.id to deduplicate.
  3. Validate the source — Verify that webhook requests come from TalkPilot by checking the source IP or implementing a shared secret in the URL (e.g., https://your-app.com/webhooks/talkpilot?secret=YOUR_SECRET).
  4. Log request IDs — Store the call ID for troubleshooting and correlation with the TalkPilot Dashboard.
  5. Handle failures gracefully — If your endpoint is down, webhook deliveries are not retried. Use the Calls API to catch up on missed events.