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
AI-generated responses may occasionally be inaccurate or incomplete. Always verify suggested actions before applying them to production systems.
Setup
Prerequisites: A Slack workspace where you have permission to install apps, and at least one alert channel where the bot should operate.1
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.
Add Antimetal to Slack
Connect your Slack workspace from the Antimetal dashboard.
2
Add the bot to your alert channels
Invite You can also invite it from the channel’s member settings.
@Antimetal to your alerts channel:3
Verify the installation
Once added, the bot will post a welcome message in the channel confirming it’s active and ready to investigate alerts.
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.
1
Open Settings > Issues
In the Antimetal dashboard, navigate to Settings > Issues and select the alert you want to automate.
2
Enable auto-investigate
Toggle on Auto-investigate for that alert.
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.
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 run if you want a preview immediately.
Commands
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:
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.