> For the complete documentation index, see [llms.txt](https://docs.docontrol.io/docontrol-user-guide/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.docontrol.io/docontrol-user-guide/system-management/settings/connectors/settings-webhooks.md).

# Webhooks

DoControl webhooks enable you to send notifications to other apps in your organization via workflows.&#x20;

The advantage of a webhook is that it sends a notification in real time, whenever a specific event happens as defined in a workflow. Having information in real time is essential to addressing the security and compliance requirements of your organization.&#x20;

<figure><img src="https://3236294211-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-MesrnyDMZGYg1V-tOBo%2Fuploads%2FRyIwMBomMBECPX0MYhP3%2Fusing%20webhooks.png?alt=media&amp;token=ea3a1b2a-4aef-4443-aa3e-391fff4778ab" alt=""><figcaption></figcaption></figure>

Using webhooks in DoControl is a 3-step process:

1. **Generate a webhook URL** - In your external app, such as Slack or Teams, you need to [generate a unique URL](#generate-webhook-urls) for your webhook.
2. **Add a webhook** - You can [configure webhooks](#add-a-webhook) with Slack, Teams, or another third-party platform, such as SIEM or SOAR support platforms.
3. **Set up workflow** - Add the [Notify by webhook](/docontrol-user-guide/workflows/define-workflow-settings/action-settings/notify.md#notify-by-webhook) step to your workflow. DoControl will send a notification message via the selected webhook whenever a specific event triggers the workflow.

## Generate webhook URLs

Before you add webhooks in DoControl, you need to generate the webhook URL in Slack, Microsoft Teams, or another third-party platform, such as SIEM or SOAR support platforms.

{% hint style="warning" %}
DoControl provides generic instructions for generating webhook URLs in external apps. Since these apps are external, we cannot commit to updates in third-party instructions.&#x20;
{% endhint %}

### &#x20;Generate a webhook URL for Slack

1. Go to the [Incoming webhooks](https://slack.com/apps/A0F7XDUAZ-incoming-webhooks) page in the Slack app directory.
2. Click **Add to Slack**.
3. Select the relevant Slack channel.
4. Click **Add incoming webhooks integration**.
5. Copy the generated URL for use in the [next step](#add-a-webhook).

{% hint style="info" %}
If the Slack setting **Require App approval** is **On**, either the admin or designated member might need to approve.
{% endhint %}

### Generate a webhook URL for Teams

1. From [Microsoft Teams](https://teams.microsoft.com/), click the <img src="https://3236294211-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-MesrnyDMZGYg1V-tOBo%2Fuploads%2Ft3PCSf4Ij3YSSz5iB4lz%2FMS%20settings.png?alt=media&amp;token=73ce6e22-afde-4664-ad2b-716ab5c226e1" alt="" data-size="line"> **Settings** button in the right corner.
2. Select **Connectors**.&#x20;
3. Click **Add** to add a new connector.
4. Click **Configure** to set up an existing connector.
5. Copy the generated URL for use in the [next step](#add-a-webhook).

{% hint style="info" %}
For more information about configuring webhooks, see [Slack webhooks](https://docontrolworkspace.slack.com/apps/A0F7XDUAZ-incoming-webhooks?tab=more_info) or [Microsoft Teams](https://learn.microsoft.com/en-us/microsoftteams/platform/webhooks-and-connectors/how-to/add-incoming-webhook) webhooks.
{% endhint %}

## Add a webhook&#x20;

It's relatively easy to add a webhook. You only need to set up a webhook once, and then it sends a notification whenever a particular event occurs as defined in a workflow.

<figure><img src="https://3236294211-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-MesrnyDMZGYg1V-tOBo%2Fuploads%2FJVpNCl96Oyj4HEYrx4dr%2Fwebhooks.png?alt=media&amp;token=463bfd54-f91d-446a-90a1-9498ecaa2ed9" alt=""><figcaption></figcaption></figure>

1. In DoControl, click **Settings** <img src="https://3236294211-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-MesrnyDMZGYg1V-tOBo%2Fuploads%2FWkfN1O2BKZBlrnVXQ5Wu%2Fsettings%20icon.png?alt=media&amp;token=9336f06e-7a3c-4651-97c7-a1ccd2cbface" alt="" data-size="line"> from the top-right corner in any screen.
2. Navigate to **Connectors >** **Webhooks**.
3. Click **Add webhook**, and select the webhook type: **Slack**, **Teams**, or **Custom.**&#x20;
4. Enter the required fields:&#x20;
   * **Channel name** - Name of the webhook channel.
   * **Webhook URL** - Paste the URL that was [generated](#generate-webhook-urls) in the external app.<br>
5. Click **Save**. The webhook is added.
6. Click **Edit** <img src="https://3236294211-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-MesrnyDMZGYg1V-tOBo%2Fuploads%2Fc6VTTWoE7BkhXBkjJTz1%2Fedit%20icon.png?alt=media&amp;token=f098a875-7003-4414-8717-d827269b7b20" alt="" data-size="line"> to change the webhook name or URL.&#x20;
7. Click **Delete** <img src="https://3236294211-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-MesrnyDMZGYg1V-tOBo%2Fuploads%2FAF9AKGMaSZ82Kwl280Sb%2Fbin%20icon2.png?alt=media&amp;token=c1145873-a84e-44c6-a75a-4187db2f4b34" alt="" data-size="line">to remove the webhook.

## **Set up workflows with webhooks**&#x20;

Add the [Notify by webhook](/docontrol-user-guide/workflows/define-workflow-settings/action-settings/notify.md#notify-by-webhook) step to your workflow. DoControl will send a notification message via the selected webhook whenever a specific event triggers the workflow.

{% hint style="info" %}
Learn more about setting up webhooks with [DoControl videos](/docontrol-user-guide/help/videos.md#how-to-set-up-a-slack-webhook-in-docontrol).
{% endhint %}


---

# 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 by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.docontrol.io/docontrol-user-guide/system-management/settings/connectors/settings-webhooks.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

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.
