For the complete documentation index, see llms.txt. This page is also available as Markdown.

How can I set up CI webhooks for sipgate Conversation Intelligence?

Set up webhooks to automatically send conversation data to CRM or other systems.

CI Webhooks are part of Conversation Intelligence. With CI Webhooks, call data from sipgate calls can be automatically transmitted to external systems such as a CRM. This allows call logs, summaries, and classifications to be integrated directly into existing processes.

CI Webhooks are configured in the Web app and should be distinguished from the separate AI Assist Webhook, which is set up directly in the sipgate Desktop App (see How do I set up the sipgate AI Assist Webhook?).

Requirements

  • You have a target URL to which the data should be sent.

  • Your system is able to process HTTP POST requests with a JSON payload using Transfer-Encoding: chunked.

  • The webhooks only work for shared channels. Conversations conducted over a private channel do not trigger CI webhooks.

Typical use cases

  • CRM integration: Automatic transfer of call notes to customer records.

  • Support systems: Creating tickets after incoming calls.

  • Analytics: Forwarding classifications to a reporting tool.

Store webhook destinations

  1. Log in as an admin in the Web app to.

  2. In Settings, open the Conversation Intelligence section.

  3. Open the CI Webhooks configuration

  4. Enter the desired webhook URL.

How it works

  • After a call ends, sipgate sends the call data via HTTP POST to the stored webhook URL.

  • The data is transmitted as a JSON payload.

  • Your system can then store or further process this payload (e.g. in a CRM, ticket system, or internal databases).

Example: A call ends ➔ a call log is created ➔ data is automatically forwarded to your database ➔ your team has the information available immediately.

Example payload:

Security

To ensure that only requests from sipgate are forwarded to your webhook integration, check the source IP address of incoming requests. Add the following IP address to your allow list: 217.116.118.254

Last updated