Slack Integration
Overview
Connect Slack to receive investigation results, feedback buttons, and daily alert digests directly in your team's Slack channels.
Prerequisites
- Admin access to your Slack workspace (to authorize the OpsWorker app)
- An OpsWorker account with at least one cluster configured
Setup
1. Start the Integration
- In the OpsWorker portal, go to Integrations
- Find Slack and click Install
2. Authorize in Slack
- You'll be redirected to Slack's OAuth authorization page (click Connect to Slack)
- Select the Slack workspace to connect
- Review the permissions OpsWorker requests (posting messages, delivering notifications, and reading channel history so OpsWorker can manage the notifications it posts)
- Click Allow
3. Add Namespace Routing
OpsWorker routes notifications per (cluster + Kubernetes namespace) to a single Slack channel. After authorization:
- Return to the OpsWorker portal and open the Slack integration screen
- Click Add Namespace Routing
- Map each Kubernetes namespace to the channel that should receive its notifications (e.g.,
productionto#prod-incidents,stagingto#staging-alerts)
4. Verify the Connection
There is no manual "test investigation" button. Onboarding verification is automatic: the portal polls agent status and shows the cluster and Slack integration as connected once everything is wired up. To confirm message delivery end to end, wait for a matching alert to fire (or use AI Chat to run an investigation), then check the routed channel. See Validate Slack Output for details.
What Slack Receives
Investigation Results
Each completed investigation posts a message containing:
- Alert summary
- Root cause analysis
- Affected Kubernetes resources
- Recommended actions with kubectl commands
- Feedback buttons (Accurate / Partially Accurate / Needs Improvement)
Daily Alert Digest
A daily summary posted at 09:00 UTC with:
- Total alert count and day-over-day comparison
- Breakdown by severity and namespace
- Trend indicators
Permissions Required
OpsWorker's Slack app requests the OAuth scopes it needs to post and manage notifications. These include reading channel history, which Slack requires for some message-management operations.
| Permission | Purpose |
|---|---|
| Send messages | Post investigation results to channels |
| Post to channels | Deliver notifications to configured channels |
| Read channel history | Manage and update the notifications OpsWorker posts |
OpsWorker reads only what it needs to post and manage its own notifications. It does not mine your team conversations.
Next Steps
- Validate Slack Output: verify the integration works correctly
- Notification Routing: route notifications to different channels