Slack integration

The Slack app is the most-used channel in DevFlow. It supports per-channel routing, alert acknowledgement from the thread, and rich message formatting.

install

Settings → Integrations → Slack → Install. The OAuth flow asks for the workspace and the Slack scopes channels:read, chat:write, chat:write.public, and commands.

creating a channel

devflow channels add payments-oncall   --type slack   --slack-channel "#payments-oncall"

Or in the dashboard. The bot needs to be in the channel — invite @DevFlow first.

what gets posted

A failing monitor produces a thread:

:redcircle: **payments-api-charge** failing in us-east-1, eu-west-1 Latency 4,213 ms · status 503 Assertion: `latencylt_ms(800)` failed [View incident in DevFlow]

The on-call can:

• Acknowledge with /devflow ack in the thread.
• Mute the monitor for 30m with /devflow mute 30m (see notification-throttling).
• Resolve manually with /devflow resolve once fixed.

thread vs new message

Subsequent failures of the same incident go to the same thread — they do not create new top-level messages. This is the dedup behaviour described in incident-management.

auto-resolve message

When the monitor recovers, DevFlow posts an auto-resolve message in the same thread:

:green_check: payments-api-charge recovered after 19m. SLO impact 47% of error budget.

attaching to a monitor

alert_channels:
  - slack:#payments-oncall

For severity routing across multiple Slack channels, see alert-routing.

removing the app

Slack admins can remove the app at any time. DevFlow detects the disconnect within 60s and surfaces a yellow banner in the dashboard pointing to the reinstall flow.