> For the complete documentation index, see [llms.txt](https://help.sipgate.de/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.sipgate.de/cloud-telefonanlage/en/using-sipgate/die-sipgate-app/wie-richte-ich-den-sipgate-ai-assist-webhook-ein.md).

# How do I set up the sipgate AI Assist webhook?

With the AI Assist Webhook, you can automatically send the AI Assist results of a channel – such as transcript, summary, to-dos and smart answers – to an external destination URL, for example to transfer them to a CRM or other tools with Zapier.

{% hint style="info" %}
The AI Assist Webhook is to be distinguished from the [CI Webhooks](/cloud-telefonanlage/en/using-sipgate/sipgate-ai-agents/wie-kann-ich-ci-webhooks-fur-sipgate-conversational-intelligence-einrichten.md) and the AI Assist Webhook is set up in the **Desktop App** and transmits the AI Assist results of a single channel. CI Webhooks, on the other hand, are configured in the **App Web** and transmit Conversation Intelligence data account-wide.
{% endhint %}

#### Prerequisites

* The webhook can only be set up by administrators of the sipgate account.
* It only applies to channels – so a channel with a phone number is required.
* Currently, this feature is in beta status in the app and can be found under **Labs** in the settings, provided you are one of the beta testers. After the full release, the feature will be listed under **AI Assist** listed.

#### Where do I set up the webhook?

1. As an admin, open the sipgate Desktop App.
2. Open the section **Labs ➔ AI Assist Webhook**.
3. Enter the desired destination URL.
4. Select the desired data format: standard JSON or **VCON**.
5. Save the setting.

After every call through a channel, the AI Assist results are automatically transferred as a bundle to the stored URL as soon as all content is available.

#### Payload format

**Standard JSON** contains, among other things, the following fields:

```json
{
  "callHeadline": "...",
  "call": {
    "id": "...",
    "caller": "...",
    "callee": "...",
    "startTime": 0,
    "endTime": 0,
    "duration": 0,
    "direction": "inbound"
  },
  "channel": {
    "id": "...",
    "name": "..."
  },
  "transcriptions": [
    { "speaker": "caller", "startTime": 0, "endTime": 0, "text": "..." }
  ],
  "summary": "...",
  "actionItems": [{ "id": "...", "text": "..." }],
  "smallTalkItems": [{ "id": "...", "topic": "...", "description": "..." }],
  "smartAnswers": [{ "id": "...", "question": "...", "answer": "..." }]
}
```

Alternatively, the format **VCON** ("Virtualized Conversations") can be selected – a standard format for storing and sharing conversation data such as transcripts and recordings. More on this in the [vCon specification](https://ietf-wg-vcon.github.io/draft-ietf-vcon-vcon-container/draft-ietf-vcon-vcon-container.html).

You can find a practical application of the AI Assist Webhook with Zapier, HubSpot, Slack and Google Sheets in the article [How do I use sipgate AI Assist in combination with HubSpot, Slack & Google Sheet?](/cloud-telefonanlage/en/connections-and-integrations/integrationen-fur-die-sipgate-app/wie-nutze-ich-den-sipgate-ai-assist-in-verbindung-mit-hubspot-slack-google-sheet.md)


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://help.sipgate.de/cloud-telefonanlage/en/using-sipgate/die-sipgate-app/wie-richte-ich-den-sipgate-ai-assist-webhook-ein.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.