Slack & Integrations

Moneat can keep response work in the tools your team already watches. Install Slack from Settings → Connectors → Slack, then use this guide for the On-call workflow and communication boundaries.

Slack responder workflow

After linking your Slack identity, use the installed Moneat incident command or shortcut to open the incident menu. From an incident channel, the rendered menu supports:

Overview and Refresh to read the current state and severity
Accept, Decline, Resolve, Cancel, and Reopen for lifecycle decisions
Join, Observe, and Leave for responder participation
Update, Actions, and Timeline to open a form and record response work

The declaration shortcut opens a form for title, description, severity, mode, visibility, and any configured declaration fields. The incident-action shortcut opens a form for an action description. The same authorization, optimistic-concurrency, idempotency, and private-incident checks apply in Slack and in the dashboard. If a form reports stale state, refresh the menu and retry against the current incident version.

The incident card in a shared channel can include Accept, Merge, Decline, configured quick actions, response nudges, the incident homepage, an incident call link, and a status-page link. Only actions rendered in the card or menu are actionable; links open the corresponding Moneat surface.

Incident channels and shared announcements

Moneat treats the responder channel and the announcement destination as separate choices:

For a live incident, an enabled Slack installation requests one incident channel per connected workspace when the incident is declared, accepted, or reopened. The channel is named after the incident's reference and title, #inc-12-checkout-latency, and its topic carries the reference and a link back to the incident. Private incidents request private channels.
Test and retrospective incidents remain channelless. A missing or disabled Slack installation, missing channel-management scopes, or a failed outbound delivery leaves the incident intact and records a channel provisioning error for retry or repair.
Moneat announces each active incident automatically and threads subsequent material updates under the announcement. With no announcements configured, it posts in the enabled installation's default channel, and private and test incidents are not announced.
To announce elsewhere, add an announcement under Configuration → Channels & updates. Once any are configured, automatic announcements go to the turned-on announcements that take the incident instead of the default channel. Each announcement sets its minimum severity, incident types, and whether it includes private incidents. A workflow's incident.announcement.post step, such as a response rule's, can post to them too.

Creating an incident channel does not automatically post the incident into a shared channel, and a shared announcement does not replace the responder channel. Configure both destinations when the response process needs both.

On-call usergroup sync

You can link an on-call schedule to a Slack usergroup. When the rotation changes, Moneat automatically updates the Slack usergroup membership so that @on-call always mentions the current responder. Managing restricted user groups may require privileged workspace access.

The Slack integration guide covers OAuth scopes, callback verification, installation health, and the exact controls available for each capability.

Other response integrations

External alert sources are documented in Alerts & alert sources. Status-page incident operations and incident calls are covered in Incidents & postmortems, where their authorization and correlation rules are described.