Overview
The Opriven Slackbot connects to your Slack workspace and works in two ways:
Investigations
— when an alert fires in a connected channel, Opriven posts a root cause analysis automatically or on demand, with suggested fixes
Weekly digest
— every Monday, Opriven posts a plain-language recap of last week’s alerts to a channel of your choice
AI-generated responses may occasionally be inaccurate or incomplete. Always verify suggested actions before applying them to production systems.
Setup
Prerequisites:
A Slack workspace where you have permission to install apps, and at least one alert channel where the bot should operate.
1
Connect Slack
From the Opriven dashboard, navigate to
Settings > Integrations
and click
Connect Slack
. You’ll be redirected to Slack to authorize the app in your workspace.
Add Opriven to Slack
Connect your Slack workspace from the Opriven dashboard.
2
Add the bot to your alert channels
Invite
@Opriven
to your alerts channel:
/invite
@Opriven
You can also invite it from the channel’s member settings.
3
Verify the installation
Once added, the bot will post a welcome message in the channel confirming it’s active and ready to investigate alerts.
Investigations
Auto-investigations
Auto-investigations run automatically when an alert fires in a channel where
@Opriven
is present. You enable them per alert, not per channel.
1
Open Settings > Issues
In the Opriven dashboard, navigate to
Settings > Issues
and select the alert you want to automate.
2
Enable auto-investigate
Toggle on
Auto-investigate
for that alert.
When the alert fires, Opriven will automatically trigger an investigation and post the results in the thread.
Manual investigations
Reply to any alert thread with
@Opriven
to trigger an on-demand investigation. The bot detects the mention and runs a root cause analysis on that alert.
@Opriven
Weekly digest
Opriven turns a week of noisy alerts into a short, prioritized list of what actually broke, delivered to your chosen channel every Monday at 9 AM Eastern.
Most monitoring fires hundreds of alerts a week. Flapping monitors, staging failures, P3 infrastructure warnings, and third-party analytics make up most of them. The digest suppresses that noise and groups the rest by root cause, so security incidents, broken auth, and complete feature failures surface first. Group names and vocabulary adapt to your product using your org’s own rules, so the digest reads in terms of what your users were doing instead of the stack that failed underneath.
The digest is driven by the
/digest
slash command. Run it from any channel in your workspace.
Enabling the digest
In the channel where you want digests delivered, run:
/digest setup
Opriven confirms the delivery channel and the recurring schedule. The first digest posts on the next scheduled Monday. Run
/digest run
if you want a preview immediately.
Commands
Command
What it does
/digest
Shows whether the digest is configured and, when it is, lists the commands available to you.
/digest setup
Sets the current channel as the delivery destination and turns on the weekly schedule. Run again in a different channel to move the destination.
/digest run
Triggers an immediate one-off digest for the past 7 days. Posts to the configured delivery channel.
/digest off
Stops the weekly schedule and removes the delivery channel. Run
/digest setup
in any channel to re-enable.
All responses are ephemeral. Only the user who ran the command sees the acknowledgement. The digest itself posts publicly to the configured delivery channel.
Permissions
The Opriven Slackbot requests the following OAuth scopes:
Scope
Purpose
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 for configuring and triggering weekly digests
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 direct messages (for onboarding DMs when a user opens the Messages tab)
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
The bot has no access to channels it hasn’t been explicitly invited to. Slack message content is not persisted — lightweight metadata (alert identifiers, investigation status) may be temporarily retained for tracking purposes.
Support
If you run into any issues with the Opriven Slack integration, contact us directly at
support@opriven.com
. We’re here to help with installation, configuration, or anything else.