- Auto-create a dedicated channel for each incident
- Mirror Slack messages into the Obsy incident timeline
- DM you when a test message is sent or when you’re assigned an incident role
- Post incident notifications to a general
#incidentschannel
Connecting Slack
- Go to Integrations in the sidebar.
- Click Connect Slack in the Slack card.
- You are redirected to Slack’s OAuth page — authorize the Obsy app for your workspace.
- You are redirected back to Obsy’s Integrations page with a confirmation toast.
Only one Slack workspace can be connected per Obsy organization. If you need to switch workspaces, disconnect the current one and reconnect with the new workspace.
Required bot scopes
The Obsy Slack app requests these OAuth scopes:| Scope | Purpose |
|---|---|
channels:manage | Create and archive public channels |
channels:read | List channels the bot can see |
channels:join | Join public channels to post messages |
chat:write | Post messages in channels and DMs |
groups:read | List private channels the bot is a member of |
groups:write | Create and manage private channels |
im:read | Read direct message history |
im:write | Open DM conversations |
users:read | Look up users by ID |
users:read.email | Look up users by email (for role assignments) |
Sending a test message
- Go to Integrations → Slack card.
- Click Send test message.
- Optionally pick a specific channel, or leave blank to receive a DM.
- Click Send.
/invite @obsy in Slack.
Two-way message sync
Messages you type in an incident’s Slack channel are synced back into the Obsy incident timeline in real time. Setup required:- In your Slack App settings (api.slack.com/apps), go to Event Subscriptions.
- Enable events and set the Request URL to:
- Under Subscribe to bot events, add:
message.channels— for public channelsmessage.groups— for private channels
- Save and reinstall the app if prompted.
- Type a message in the incident Slack channel.
- Open the incident in Obsy — the message should appear in the timeline within a few seconds.
- If no messages appear and you set up Events correctly, check that the Slack app was reinstalled after adding the event subscriptions.
Disconnecting Slack
Go to Integrations → Slack card and click Disconnect. This removes the workspace connection and the stored bot token. Existing incident channels in Slack are not affected.Troubleshooting
'not_in_channel' error when posting to a channel
'not_in_channel' error when posting to a channel
The bot needs to be a member of the channel. Run
/invite @obsy in the target channel. For incident channels, Obsy joins automatically when creating the channel.Test DM fails
Test DM fails
Ensure your Obsy account email matches your Slack email. Obsy uses your email to look up your Slack user ID for DMs. If they differ, the lookup fails.
Incident messages not appearing in the Obsy timeline
Incident messages not appearing in the Obsy timeline
Check that Event Subscriptions are enabled and the
message.channels event is subscribed. The Slack app must be reinstalled after adding new event subscriptions for them to take effect.