> ## Documentation Index
> Fetch the complete documentation index at: https://docs.antimetal.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Slack

> Investigate alerts and get weekly digests, directly in Slack

## Overview

The Antimetal Slackbot connects to your Slack workspace and works in two ways:

* **Investigations** — when an alert fires in a connected channel, Antimetal posts a root cause analysis automatically or on demand, with suggested fixes
* **Weekly digest** — every Monday, Antimetal posts a plain-language recap of last week's alerts to a channel of your choice

<Note>
  AI-generated responses may occasionally be inaccurate or incomplete. Always verify suggested actions before applying them to production systems.
</Note>

## Setup

**Prerequisites:** A Slack workspace where you have permission to install apps, and at least one alert channel where the bot should operate.

<Steps>
  <Step title="Connect Slack">
    From the Antimetal dashboard, navigate to **Settings > Integrations** and click **Connect Slack**. You'll be redirected to Slack to authorize the app in your workspace.

    <Card title="Add Antimetal to Slack" icon="slack" href="https://overlook.antimetal.com/integrations/slack">
      Connect your Slack workspace from the Antimetal dashboard.
    </Card>
  </Step>

  <Step title="Add the bot to your alert channels">
    Invite `@Antimetal` to your alerts channel:

    ```bash theme={null}
    /invite @Antimetal
    ```

    You can also invite it from the channel's member settings.
  </Step>

  <Step title="Verify the installation">
    Once added, the bot will post a welcome message in the channel confirming it's active and ready to investigate alerts.
  </Step>
</Steps>

## Investigations

### Auto-investigations

Auto-investigations run automatically when an alert fires in a channel where `@Antimetal` is present. You enable them per alert, not per channel.

<Steps>
  <Step title="Open Settings > Issues">
    In the Antimetal dashboard, navigate to **Settings > Issues** and select the alert you want to automate.
  </Step>

  <Step title="Enable auto-investigate">
    Toggle on **Auto-investigate** for that alert.
  </Step>
</Steps>

When the alert fires, Antimetal will automatically trigger an investigation and post the results in the thread.

### Manual investigations

Reply to any alert thread with `@Antimetal` to trigger an on-demand investigation. The bot detects the mention and runs a root cause analysis on that alert.

```
@Antimetal
```

## Weekly digest

Antimetal turns a week of noisy alerts into a short, prioritized list of what actually broke, delivered to your chosen channel every Monday at 9 AM Eastern.

Most monitoring fires hundreds of alerts a week. Flapping monitors, staging failures, P3 infrastructure warnings, and third-party analytics make up most of them. The digest suppresses that noise and groups the rest by root cause, so security incidents, broken auth, and complete feature failures surface first. Group names and vocabulary adapt to your product using your org's own rules, so the digest reads in terms of what your users were doing instead of the stack that failed underneath.

The digest is driven by the `/digest` slash command. Run it from any channel in your workspace.

### Enabling the digest

In the channel where you want digests delivered, run:

```
/digest setup
```

Antimetal confirms the delivery channel and the recurring schedule. The first digest posts on the next scheduled Monday. Run `/digest run` if you want a preview immediately.

### Commands

| Command         | What it does                                                                                                                                     |
| --------------- | ------------------------------------------------------------------------------------------------------------------------------------------------ |
| `/digest`       | Shows whether the digest is configured and, when it is, lists the commands available to you.                                                     |
| `/digest setup` | Sets the current channel as the delivery destination and turns on the weekly schedule. Run again in a different channel to move the destination. |
| `/digest run`   | Triggers an immediate one-off digest for the past 7 days. Posts to the configured delivery channel.                                              |
| `/digest off`   | Stops the weekly schedule and removes the delivery channel. Run `/digest setup` in any channel to re-enable.                                     |

All responses are ephemeral. Only the user who ran the command sees the acknowledgement. The digest itself posts publicly to the configured delivery channel.

## Permissions

The Antimetal Slackbot requests the following OAuth scopes:

| Scope               | Purpose                                                                            |
| ------------------- | ---------------------------------------------------------------------------------- |
| `app_mentions:read` | Respond when mentioned in channels                                                 |
| `channels:history`  | Read alert messages in public channels                                             |
| `channels:join`     | Join public channels when invited                                                  |
| `channels:read`     | List available channels                                                            |
| `chat:write`        | Post investigation results and remediation steps                                   |
| `commands`          | Register the `/digest` slash command for configuring and triggering weekly digests |
| `files:read`        | Read files shared in conversations                                                 |
| `groups:history`    | Read messages in private channels the bot is in                                    |
| `groups:read`       | List private channels the bot is invited to                                        |
| `groups:write`      | Manage private channels the bot is in                                              |
| `im:history`        | Read direct messages with the bot                                                  |
| `im:read`           | View direct message conversations                                                  |
| `im:write`          | Send direct messages (for onboarding DMs when a user opens the Messages tab)       |
| `mpim:read`         | View multi-party direct message metadata                                           |
| `reactions:read`    | Read message reactions                                                             |
| `reactions:write`   | Add reactions to messages                                                          |
| `usergroups:read`   | View user groups                                                                   |
| `users:read`        | View user profiles                                                                 |
| `users:read.email`  | View user email addresses                                                          |

The bot has no access to channels it hasn't been explicitly invited to. Slack message content is not persisted — lightweight metadata (alert identifiers, investigation status) may be temporarily retained for tracking purposes.

<Snippet file="security-note.mdx" />

## Support

If you run into any issues with the Antimetal Slack integration, contact us directly at [support@antimetal.com](mailto:support@antimetal.com). We're here to help with installation, configuration, or anything else.