Skip to main content
The Slack integration lets sureops create dedicated incident channels, post real-time stage updates to your team, and deliver Human-in-the-Loop (HITL) approval requests directly in Slack. Responders can review and approve or reject recommendations without opening the sureops UI.

​
What this integration enables

  • Incident channels — creates a Slack channel per incident (e.g. #inc-2026-payment-timeout) as a war room for the response team. This is severity-gated, not automatic for every incident: by default only P1/P2 incidents get a war-room channel, governed by the “Proactively notify for severity” setting (Settings → Organization, default P2; overridable per environment).
  • Stage notifications — posts updates as an incident progresses through detection, diagnosis, and resolution, in the incident’s war-room channel
  • HITL approval delivery — pending approval requests post to the incident’s war-room channel with Approve and Reject buttons, so responders can act without opening the sureops UI
There is no Slack escalation message. When an approval window times out and an incident escalates to human takeover, sureops sends an email notification — not a Slack message — and only to users who have opted in to escalation emails (off by default per user).

​
Prerequisites

  • An environment selected in the top-right context switcher — Settings → Environment → Integrations is scoped to that environment and stays disabled until one is selected
  • A Slack workspace where you have permission to install apps
  • Admin access to the workspace (required to authorize the sureops Slack app)
Integration connections are per-environment. Connecting Slack here only applies to the environment that was selected in the context switcher at the time — it does not carry over to your other environments. Repeat this connect flow for each environment that needs Slack.

​
Setup

1

Click Connect

In sureops, go to Settings → Environment → Integrations and click Connect next to Slack.You will be redirected to Slack to authorize the sureops app on your workspace.
2

Authorize

Review the permissions sureops is requesting — primarily: create channels, post messages, and read channel membership. Click Allow to complete the authorization.You’ll be redirected back to sureops with the connection confirmed.

​
After connecting

Settings → Environment → Integrations → Slack has no configuration options after connecting — the connect flow above (Click Connect → Authorize) is the whole setup. Channel behavior — which channel notifications land in, whether an incident channel is auto-created, and what prefix it uses — is configured separately, not on the Slack integration screen itself:
  • Settings → Organization — sets the org-wide default incident channel behavior
  • Settings → Environment → Channels — overrides the org default for a specific environment
The Slack connect screen shows a hosting-model choice (“Use Slack’s MCP endpoint” vs. “Use my own MCP server”) like several other integrations — but MCP is not the recommended or supported path for Slack. sureops’ actual Slack integration connects via Slack’s Web API directly, using the bot token issued during app install, because Slack’s vendor-hosted MCP endpoint requires user-token auth that would undermine per-action audit attribution. Use the standard Click Connect → Authorize flow above rather than the MCP-hosting option. See How integrations work for the full hosting model.

​
Official documentation