> For the complete documentation index, see [llms.txt](https://docs.getantidote.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.getantidote.com/welcome-to-antidote/integrations/slack.md).

# Slack

Get Antidote findings posted to the Slack channels your team already uses.

<figure><img src="https://1135428273-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F2rbi6bEnpVLUQHudgXDV%2Fuploads%2FsAHSe5RHxNZrNdS29gks%2F24-slack__cover.png?alt=media&amp;token=b1de6a34-02bc-48ef-9094-be98a9b64c76" alt=""><figcaption></figcaption></figure>

### Slack notifications overview

Duku posts a message to Slack when it finds a new issue, when an exploration finishes, or when a scheduled exploration is skipped. Each message links directly to the issue or run in Duku.

Notifications are set up once for your organisation. Connect your Slack workspace, then add a channel for each place you want messages to go. Each channel has its own events and products.

{% hint style="info" %}
Notifications are switched on per organisation. If you don't see a **Notifications** section under **Organisation settings → Integrations**, contact Duku to enable it.
{% endhint %}

### Prerequisites

* You are an organisation admin in Duku.
* You can install apps in your Slack workspace.
* You configure notifications per organisation, not per product.

### Connect Slack

{% stepper %}
{% step %}

#### Add a channel

<figure><img src="https://1135428273-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F2rbi6bEnpVLUQHudgXDV%2Fuploads%2FcUkR3gjLEdkjWEc8QyTW%2F25-slack__01-settings-notifications.png?alt=media&amp;token=1dd80bcf-f7f5-444a-8b68-cd20996a4786" alt=""><figcaption></figcaption></figure>

Open **Organisation settings → Integrations**. In the **Notifications** section, select **+ Add channel**.
{% endstep %}

{% step %}

#### Add Duku to Slack

<figure><img src="https://1135428273-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F2rbi6bEnpVLUQHudgXDV%2Fuploads%2F4faE81F8pmB88OZHCjSv%2F26-slack__02-add-to-slack.png?alt=media&amp;token=6a052859-fe2c-414b-b61d-31f56d491e83" alt=""><figcaption></figcaption></figure>

Under **Send to**, choose **Slack**. Select **Add to Slack**. In the Slack popup, check the workspace in the top right and select **Allow**.

The popup closes and returns you to Duku.
{% endstep %}

{% step %}

#### Pick a channel

<figure><img src="https://1135428273-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F2rbi6bEnpVLUQHudgXDV%2Fuploads%2FsdEUdEMJ5VyxXrNCxMHq%2F27-slack__03-pick-channel.png?alt=media&amp;token=626ab1f4-f501-482e-9210-6e27c4cca611" alt=""><figcaption></figcaption></figure>

Under **Channel in your workspace**, choose the channel Duku should post to.

Duku can post to any public channel without being invited. For a private channel, invite the Duku app to it in Slack first. Then paste the channel ID into **Or enter a channel ID**. For example, `C0123456789`.

The **Name** field fills in with the channel name. You can change it. It only labels the channel in Duku.
{% endstep %}

{% step %}

#### Pick events and products

<figure><img src="https://1135428273-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F2rbi6bEnpVLUQHudgXDV%2Fuploads%2F4A5m1MA4qBKTvqOHsD5e%2F28-slack__04-events-and-products.png?alt=media&amp;token=3230df11-5b82-43d9-aff0-19b3e054fc4b" alt=""><figcaption></figcaption></figure>

Under **Events**, tick what this channel should receive. Under **Products**, tick the products this channel covers. Leave everything unticked to hear about every product. Then select **Add channel**.

| Event                     | When Duku posts                                                                                 |
| ------------------------- | ----------------------------------------------------------------------------------------------- |
| New issue                 | Duku finds a new issue.                                                                         |
| Exploration completed     | An exploration finishes and all its runs have settled.                                          |
| Schedule skipped          | A scheduled exploration didn't run, for example because the previous run was still in progress. |
| Integration needs re-auth | A connected issue tracker, such as Linear, needs reconnecting.                                  |

If a product uses environments, you can also choose which environments the channel covers. Environment choices apply to **Exploration completed** and **Schedule skipped**.
{% endstep %}

{% step %}

#### Send a test

<figure><img src="https://1135428273-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F2rbi6bEnpVLUQHudgXDV%2Fuploads%2FVo9vGCISc0OnLpfKBBf4%2F29-slack__05-channel-added.png?alt=media&amp;token=4a59802b-07a1-48bc-8e22-8e63732b0ca3" alt=""><figcaption></figcaption></figure>

On the channel row, select **Test**.

Duku posts a test message to the channel, and the row shows **Test delivered.**
{% endstep %}
{% endstepper %}

### What ends up in Slack

<figure><img src="https://1135428273-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F2rbi6bEnpVLUQHudgXDV%2Fuploads%2F1JNSKzSRsVt4jQvoQtJP%2F30-slack__06-messages-in-slack.png?alt=media&amp;token=f07885c5-4d20-43d5-b077-5f771b31cc87" alt=""><figcaption></figcaption></figure>

* **New issue:** the severity, product, and issue title, with a **View issue** button.
* **Severity** is colour-coded: 🔴 **critical**, 🟠 **high**, 🔵 **medium**, and 🟢 **low**. Incidents are marked 🚨.
* **Several new issues at once:** when several new issues for one product arrive together, Duku sends one message. It lists issues with the most severe first, plus a **View issues** button.
* **Exploration completed:** the product and how many runs completed, with a **View runs** button.
* **Schedule skipped:** the schedule name and why it did not run.
* **Integration needs re-auth:** which issue tracker needs reconnecting.

### Managing channels

Each channel row in the Notifications section has these actions:

* **Edit:** change the name, events, products, or environments. You can also pause the channel.
* **Test:** send a test message.
* **History:** see recent deliveries and their status.
* **Delete:** stop sending to this channel.

Add more channels to send different events to different places. For example, send new issues to engineering and completed explorations to QA.

### Disconnecting

Select **Disconnect** on the Slack workspace row. This removes the workspace and every Slack channel that posts through it. Your existing messages stay in Slack.