Skip to main content

Setting Up and Using the Slack App

StatiBeat's Slack app helps teams coordinate incident work where they already communicate.

Slack App Settings setup path for connecting a workspace and choosing routing behavior
Slack App Settings setup path for connecting a workspace and choosing routing behaviorOpen full-size image
tip

Open Slack App, review the connection card, click Add to Slack, and authorize the StatiBeat Slack app for your workspace.

What you can do from Slack​

With the Slack app connected, teams can:

  • send incident and maintenance announcements to selected channels
  • start and update workflows from Slack
  • receive reminders when incidents or maintenance need attention
  • route Beat alerts and Beat review requests to the right channel
  • use AI-assisted drafting when AI is enabled for the page

Slack is an operating surface, not the only source of truth. The StatiBeat admin UI remains the place to review page settings, publish post-incident reports, and make larger configuration changes.

Connect the app​

In the supported hosted flow:

  1. Open the page admin UI.
  2. Go to Slack App.
  3. Click Add to Slack.
  4. Approve the requested Slack permissions.
  5. Return to StatiBeat and confirm the workspace shows as connected.

You do not need to create a separate Slack app or paste Slack client credentials for each page. The connection uses the managed StatiBeat Slack app.

The same settings page lets you disconnect Slack later if you need to rotate ownership or stop Slack workflows for the page.

Choose channels​

After connecting Slack, configure the channels that should receive operational messages.

Common choices include:

  • a shared incident and maintenance channel
  • a synthetic alert channel for Beat failures
  • a synthetic review channel for draft or approval workflows

Channel fields are picker-first when the workspace is connected. Use manual channel IDs only when the channel picker cannot find the channel you need.

Control incident channel behavior​

The Slack app can help avoid duplicate incident work in the same channel.

The channel linking modes are:

  • No Link: any channel can create incidents without linking behavior
  • Soft Limit: warn when a channel already has an open incident
  • Hard Limit: prevent a channel from creating another open incident while one is already linked

Use Soft Limit when teams need flexibility. Use Hard Limit when each incident channel should represent exactly one active incident.

Configure announcements and reminders​

The Slack settings page includes controls for:

  • global incident and maintenance announcements
  • reminder intervals for open incidents
  • maintenance reminders before start, before end, and after overrun
  • per-channel reminder overrides
  • notification behavior for create, update, and resolve events

If your team runs incidents in dedicated Slack channels, configure reminders early. It is easier to set the expected rhythm before the first real incident than to change habits during one.

Use AI-assisted workflows​

AI provider credentials are configured on the AI Settings page, not on the Slack page.

When AI is enabled and the Slack user has the right StatiBeat access, Slack can help draft or plan workflows such as:

  • incident drafts
  • Beat creation
  • hierarchy creation
  • operational answers about current incidents, maintenance, Beats, and recent history

AI-assisted writes are confirmation-first. Slack shows a preview, assumptions, and warnings before anything is created or changed.

Post-incident reports​

Slack can point people toward resolved incidents and indicate when a published Post-Incident Report exists.

Drafting, publishing, revising, or unpublishing a Post-Incident Report stays in the StatiBeat admin UI. That keeps post-incident writing deliberate and separate from live incident chatter.

Good defaults​

For most teams:

  1. Connect the managed StatiBeat Slack app.
  2. Set a shared incident and maintenance channel.
  3. Set separate Beat alert and Beat review channels if Beats are active.
  4. Start with Soft Limit channel linking.
  5. Enable reminders for long-running incidents and maintenance.
  6. Add AI-assisted workflows only after the team understands the manual flow.