Antimetal
BlogCareers
Sign InBook a Demo
BlogCareersSign InBook a Demo
Company
  • Careers
  • Blog
Resources
  • Docs
  • Guides
  • Glossary
  • Integrations
Compliance
  • Trust Center
  • Terms
  • Privacy
All Systems NormalBuilt in NYC

The Autonomous System for Production
SOC 2, GDPR, and HIPAA compliant.

IntegrationsChat

Slack

Native

Slack is where most teams find out something is wrong, so it's where Antimetal starts. The Antimetal Slackbot investigates alerts in your channels and posts a root cause analysis with suggested fixes — plus a weekly digest of what actually broke.

Connect SlackRead the docs

Table of contents

  1. What Antimetal does with Slack
  2. Connecting Slack
  3. Permissions and access
On this page
  1. What Antimetal does with Slack
  2. Connecting Slack
  3. Permissions and access

#What Antimetal does with Slack

  • Investigate automatically when an alert fires in a connected channel
  • Investigate on demand when someone replies @Antimetal in an alert thread
  • Post root cause analysis and suggested fixes directly in the thread
  • Deliver a weekly digest every Monday that suppresses noise and groups alerts by root cause

#Connecting Slack

Prerequisites

  • A Slack workspace where you have permission to install apps
  • At least one alert channel where the bot should operate
  1. Connect Slack

    From the Antimetal dashboard, go to Settings > Integrations and click Connect Slack. You'll be redirected to Slack to authorize the app in your workspace.

  2. Add the bot to your alert channels

    Invite the bot with /invite @Antimetal, or add it from the channel's member settings.

  3. Verify the installation

    The bot posts a welcome message in the channel confirming it's active and ready to investigate alerts.

  4. Enable auto-investigations (optional)

    Auto-investigations are enabled per alert, not per channel. In the Antimetal dashboard go to Settings > Issues, select an alert, and toggle on Auto-investigate. When that alert fires, Antimetal investigates and posts results in the thread.

  5. Set up the weekly digest (optional)

    In the channel where you want digests delivered, run /digest setup. Antimetal confirms the delivery channel and schedule; the first digest posts the next Monday at 9 AM Eastern. Run /digest run for an immediate preview, or /digest off to stop the schedule.

#Permissions and access

The bot has no access to channels it hasn't been explicitly invited to. Slack message content is not persisted — lightweight metadata such as alert identifiers and investigation status may be temporarily retained for tracking. AI-generated responses may occasionally be inaccurate or incomplete; always verify suggested actions before applying them to production.

OAuth scopes

ScopeAccess
app_mentions:readRespond when mentioned in channels
channels:historyRead alert messages in public channels
channels:joinJoin public channels when invited
channels:readList available channels
chat:writePost investigation results and remediation steps
commandsRegister the /digest slash command
files:readRead files shared in conversations
groups:historyRead messages in private channels the bot is in
groups:readList private channels the bot is invited to
groups:writeManage private channels the bot is in
im:historyRead direct messages with the bot
im:readView direct message conversations
im:writeSend onboarding DMs
mpim:readView multi-party direct message metadata
reactions:readRead message reactions
reactions:writeAdd reactions to messages
usergroups:readView user groups
users:readView user profiles
users:read.emailView user email addresses

All tenant data is processed in isolated environments. See security and compliance for details.

Need help?

Contact us via Slack or at support@antimetal.com.

Related integrations

  • PagerDuty

    Incident Management
    Native

    Ingest incidents and alerts from PagerDuty.

    DocsConnect
  • Incident.io

    Incident Management
    Native

    Pull incident timelines into investigations.

    DocsConnect
  • GitHub

    Source Control
    Native

    Search your codebase for the root cause.

    DocsConnect
PreviousShortcutNextSnowflake