/Integrations
v1.2Slack
Validate Slack bot tokens and launch alert channel access.
Integration
Slack
Confirms bot token and channel accessibility.
Launch alerts that never arrive in Slack usually trace to a valid bot token with the wrong scopes, or a channel the bot was never invited to. PreFlight runs auth.test, verifies required scopes, and confirms the target channel is reachable before you wire incident and deploy notifications.
Requirements
- Slack Bot User OAuth Token (`xoxb-...`)
- Target channel ID where alerts should post
- Bot invited to the target channel with read/post permissions
What PreFlight checks
| Probe | What it proves |
|---|---|
| auth.test | The bot token is valid and identifies the expected workspace app. |
| Scope verification | Required read and post scopes are present on the token. |
| Channel access | The bot can reach the configured channel ID. |
| Delivery readiness | Alert messages can be posted without permission errors. |
Failure guidance
| Symptom | Fix |
|---|---|
| Invalid token | Reinstall the Slack app and copy a fresh Bot User OAuth Token. |
| Missing scopes | Add chat:write and channel read scopes, then reinstall the app. |
| Channel not found | Invite the bot to the channel with /invite @YourBot. |
| Wrong workspace | Confirm the token belongs to the workspace where alerts should land. |
Dashboard setup
- Go to Integrations → Slack in your PreFlight project.
- Paste the Bot User OAuth Token from your Slack app settings.
- Enter the channel ID (right-click channel → View channel details → copy ID).
- Run Pre-Flight Check after inviting the bot to the channel.