Slack Integration
Connect your Slack workspace to OpsBrief and start receiving AI-powered daily digests of important team updates.
Prerequisites
- A Slack workspace where you have admin permissions (or can request app installation)
- An OpsBrief account (sign up free)
- Access to the channels you want to monitor
Step-by-Step Setup
Navigate to Integrations
After creating your account, go to your dashboard and navigate to Settings → Integrations. You'll see a list of available platforms including Slack.
Click Connect Slack
Click the "Connect" button next to Slack. This will redirect you to Slack's OAuth authorization page where you'll grant OpsBrief permission to access your workspace.
Security note: We use OAuth 2.0 and only request for the minimum permissions needed to read messages from your selected channels and write messages to your selected channels. Learn more about our security practices.
Authorize the App
Review the permissions requested and click "Allow" to authorize OpsBrief. OpsBrief installs once at the workspace level — there are no user scopes, so individual workspace members do not have to authorize the app separately. The bot scopes we request are:
channels:history- Read messages from public channelschannels:read- List public channels in your workspacegroups:history- Read messages from private channels the bot has been invited togroups:read- List the private channels the bot has been invited tousers:read- Resolve message authors for digest attributionchannels:join- Auto-join public channels you select for monitoringchat:write- Post your scheduled OpsBrief digest into a single Slack channel that you pick in Settings → Digest Preferences (see Step 6 below). This is the only way OpsBrief writes to Slack.
What triggers OpsBrief to post in Slack?
- Only one trigger: the scheduled digest you turn on in Settings → Digest Preferences. Nothing is posted until you both enable Slack digests and pick a destination channel.
- Where it posts: the single Slack channel you select in that page. The bot must already be a member of that channel — only channels the bot is in appear in the picker.
- When it posts: on the schedule you choose in the same page (hourly, daily, or weekly, at a time and timezone of your choice).
- What it posts: a single summary message containing the digest header, an event-count summary, and up to ten extracted events, each with a link back to the original Slack message. Sample payload.
- What it does not do: the bot does not reply to messages, react to mentions, listen for slash commands, or post in any channel other than the one you selected. There is no event subscription configured for this app.
- How to stop it: toggle "Enable Slack digests" off in Settings → Digest Preferences at any time. Disconnecting the Slack integration on the Connections page also stops all writes.
Select Channels
After authorization, you'll be redirected back to OpsBrief. Navigate to Channels in your dashboard to see all available Slack channels. Select which channels you want to monitor.
For each channel, you can configure which event types to detect.
Engineering teams typically monitor channels like #releases, #incidents, and #deployments.
Product teams typically monitor channels like #product-updates, #feature-launches, and #user-feedback.
Operations teams typically monitor channels like #general, #announcements, and #project-channels.
Configure Event Types
For each selected channel, choose which event types to track. Common configurations include:
#engineering
- ✓ Releases
- ✓ Deployments
- ✓ Incidents
- ✓ Technical decisions
#product
- ✓ Feature launches
- ✓ Experiments
- ✓ User feedback
- ✓ Roadmap updates
Enable Slack Digests in Digest Preferences (Optional — required to use chat:write)
By default, OpsBrief delivers your digest by email only. If you want OpsBrief to also post your digest into Slack (the only place we use the chat:write scope), enable it here. No Slack messages are sent until you complete this step.
Step-by-step
- From your dashboard, click Settings in the sidebar, then open Digest Preferences.
- In the Slack card, flip the "Enable Slack digests" toggle on. The card description reads "Post digest summaries to a Slack channel" — that is the exact feature backed by
chat:write. - If your organization has connected more than one Slack workspace, pick the workspace from the Workspace dropdown.
- Pick the destination channel in the Channel dropdown. Only channels where the OpsBrief bot is already a member are listed. To add the bot to a channel first, type
/invite @OpsBriefin that channel and refresh the picker. - Set your Frequency (hourly, daily, or weekly), Send time, and Timezone on the same page. These determine when the bot posts.
What gets posted
A single message at each scheduled run, containing a header ("OpsBrief Daily Digest", etc.), the date range, an event-count summary by severity, up to ten extracted events with platform and channel attribution, and a link back to the original message for each event. The bot does not post anything else, ever.
Turning it off
Toggle "Enable Slack digests" off in the same page to stop all Slack posts immediately. You can also disconnect the entire integration from Connections, which revokes the bot token with Slack and removes chat:write access entirely.
Troubleshooting
I don't see all my channels
OpsBrief can only access channels where the Slack app has been added. For private channels, you'll need to manually add the OpsBrief app to each channel you want to monitor.
The connection failed
Make sure you have admin permissions in your Slack workspace, or ask your workspace admin to approve the app installation. Check that pop-ups are enabled in your browser.
Messages aren't syncing
Messages sync every few minutes. If you've just connected, wait a few minutes and refresh. For persistent issues, try disconnecting and reconnecting the integration.
Can I monitor private channels?
Yes, but you'll need to invite the OpsBrief bot to each private channel. Go to the channel, type /invite @OpsBrief, and the bot will be added.
Does the OpsBrief bot reply to messages, mentions, or slash commands?
No. The bot does not subscribe to events, does not respond to mentions, does not handle slash commands, and does not react to messages. The chat:write scope is used in exactly one place: posting your scheduled digest into the single channel you select in Settings → Digest Preferences.
I authorized chat:write but I don't see any messages from OpsBrief
That's expected — chat:write is dormant until you turn on Slack digest delivery. Go to Settings → Digest Preferences, flip 'Enable Slack digests' on, pick a channel where the OpsBrief bot is a member, and set a frequency. The first digest will arrive at the next scheduled run.
The channel I want isn't in the digest channel picker
Only channels the OpsBrief bot is already a member of are listed. Open the channel in Slack and type /invite @OpsBrief, then click the refresh button next to the picker on Settings → Digest Preferences.
How do I stop OpsBrief from posting in Slack?
Go to Settings → Digest Preferences and toggle 'Enable Slack digests' off — posting stops immediately. To remove chat:write access entirely, disconnect the integration from the Connections page; that revokes the bot token with Slack.
Related Documentation
OpsBrief uses artificial intelligence to analyze messages and extract key events. AI-generated content may occasionally be inaccurate or incomplete. We recommend reviewing extracted events and verifying important information with the original source.