Slack
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.
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
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.
Invite the bot with
/invite @Antimetal, or add it from the channel's member settings.The bot posts a welcome message in the channel confirming it's active and ready to investigate alerts.
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.
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 runfor an immediate preview, or/digest offto 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
| Scope | Access |
|---|---|
| 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 |
| 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 onboarding DMs |
| 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 |
All tenant data is processed in isolated environments. See security and compliance for details.
Related integrations
Need help?
Contact us via Slack or at support@antimetal.com.