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, type /moneat or use a Moneat shortcut. Outside an incident
channel, /moneat help lists the commands:
| Command | What it does |
|---|---|
/moneat declare sev2 <title> | Declares a live incident at once, at SEV-3 unless you give a severity. Without a title, or when your declaration form has required fields, it opens the form instead |
/moneat <title> | Opens the declaration form with that title |
/moneat who | Shows who is on call now and when each schedule hands off |
/moneat page <alert ID> <@person> | Pages people, channels, schedules, teams or an escalation path about an alert |
/moneat cover <schedule ID> <@person> <start> <end> | Adds on-call cover. Admins and people on the schedule can add it |
In an incident's channel, /moneat opens that incident's menu, /moneat update <text> posts an
update, and /moneat resolve resolves the incident, posting any text after it as a last update.
Cover times and next hand-offs in replies show in each reader's own Slack time zone.
The menu offers only what the incident's current state allows:
- In triage: Accept, Decline, Merge and Join
- While active: Update, Resolve, Cancel, Merge, Join or Leave, and Status page
- Resolved, cancelled or declined: Reopen
- Open incidents also offer Action and Timeline, and all of these have Overview. A merged incident's menu names the incident it went into and links to it.
Whoever declares an incident, from Slack or the dashboard, joins it as a participant. Merge opens a form listing the open incidents you can see that this one can merge into.
Status page opens a form whose customer headline starts blank, so an internal title never reaches customers by accident. Preview shows exactly what customers will read. Tick the approval under that preview and press Publish to post it; changing anything after previewing shows a new preview to approve.
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.poststep, 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.