Slack
Connect Batida to Slack to receive incident notifications, use slash commands, and automatically create dedicated channels per incident.
Setup
Batida uses Slack OAuth to connect to your workspace.
Go to Settings > Integrations > Slack in the Batida dashboard.
Click Connect Slack. You will be redirected to Slack's OAuth consent screen.
Grant the following bot token scopes:
chat:write-- post messages and create channelschannels:manage-- auto-create incident channelscommands-- register slash commandsusers:read-- resolve responder names
Authorize the app and return to Batida. The connection status should show Connected.
Workspace requirements
You need to be a Slack workspace admin (or have permission to install apps) to complete the OAuth flow.
Incident notifications
Batida sends notifications for every incident lifecycle event:
- Opened -- severity, title, assigned responder, and a link to the incident timeline.
- Updated -- status changes, severity changes, and new timeline comments.
- Resolved -- resolution summary and total duration.
Notifications include action buttons for acknowledging, escalating, and resolving directly from Slack.
Slash commands
| Command | Description |
|---|---|
/batida open <title> | Open a new incident with the given title. |
/batida list | List active incidents for your team. |
/batida update <id> <message> | Add a timeline comment to an incident. |
Slash commands are available in any channel once the integration is enabled.
Auto-created channels
When an incident is opened, Batida can automatically create a Slack channel named #inc-{id}-{slug}. This channel becomes the coordination hub for that incident.
All responders are automatically invited, and every timeline update is posted to the channel.
Configure auto-creation under Settings > Integrations > Slack > Channel Settings:
- Auto-create: toggle on/off
- Channel naming pattern: defaults to
inc-{{id}}-{{slug}}
Escalation notifications
When an incident is escalated to a higher severity tier, a special notification is sent to the escalation channel configured in your team settings. This message includes the incident details and a direct link to acknowledge.
Troubleshooting
- "App not found": Ensure the OAuth flow completed successfully. Reconnect from the integration settings.
- Missing slash commands: Slack may take up to a minute to register new commands after authorization. If commands are still missing after a few minutes, disconnect and reconnect the integration.
- Bot cannot create channels: Verify the
channels:managescope was granted during OAuth.