Skip to main content

​
What are Webhooks?

Webhooks are how services notify each other of events in real-time. At their core, they are POST requests sent to a pre-determined endpoint you specify. The endpoint can be whatever you want, and you can just add them from the UI. You can configure one endpoint per service to listen to all event types. In the case of telli, this means that you can receive data about calls and their analysis in real-time and transmit them into your CRM, calendar, or other tools and workflows.

​
Setting Up Webhooks

To start receiving webhook events:
  1. In telli, go to Settings > API & Webhooks and click “Configure”
  2. Click “Add Endpoint” and provide a URL you control (e.g. a Zapier webhook URL)
  3. Enable the events you want to receive (e.g. “call_ended”)
  4. Setup the webhook in the service you want to integrate with (e.g. Zapier)
  5. Make a test call using your telli account
  6. Check if the webhook was triggered in the service you integrated with
The way to indicate that a webhook has been processed is by returning a 2xx (status code 200-299) response to the webhook message within a reasonable time-frame (15s). Find more details about the webhook setup in the add endpoints to webhooks section.

​
Supported Events

We currently support these webhook events:
  • call_ended: Triggered when a call completes, including transcript and analysis
  • contact_status_changed: Triggered when a contact’s status changes (new, pending, closed, reached)
See all our supported events in the webhook events section.

​
Security and Reliability

  • Verify signatures: Use our partner Svix’s libraries to verify webhook authenticity
  • Disable CSRF protection: Ensure your endpoint allows webhook POST requests
  • Automatic retries: Failed webhook deliveries are retried with exponential backoff
  • Manual recovery: Retry failed messages through the webhook portal
Find more info on how to verify webhook requests and how we handle retries in the verify webhook requests section. For implementation details, refer to our documentation on adding endpoints, event payloads, signature verification, and our integration examples using Zapier and Make.
⌘I