Incident alert with Acknowledge, Resolve, and View Incident buttons in Slack
What you get
- DM pages — when you are on call and a layer fires, you receive a Slack DM with the incident title, severity, escalation layer, and three buttons: Acknowledge (primary), Resolve (danger), View Incident.
- Channel notifications — incident-created notifications post to your configured alerts channel(s) with the same three buttons.
- Incident channels — when an incident is created, scaling.cloud can open a dedicated channel named
inc-<sequentialId>-<slug>(e.g.,inc-42-db-pool-exhausted) and invite the on-call responder. - One-click actions — clicking Acknowledge stops escalation; clicking Resolve transitions the incident through the lifecycle to
resolved. The message updates in place with a footer showing who took the action and when.
How identity is resolved
When you click a Slack button, scaling.cloud matches your Slack account to your scaling.cloud account by email address. Both must be:- In the same scaling.cloud organization.
- Using the same email on both sides.
If your Slack email differs from your scaling.cloud email (work vs. personal account, an alias), the match fails. Update one to match the other, or contact your admin to align identities.
Installation
Slack is connected per organization. Only org admins can install or remove the integration.1
Open Integrations
In the scaling.cloud dashboard, go to Settings → Integrations and click the Slack card.
2
Authorize the scaling.cloud app
Click Connect Slack. You’ll be taken to Slack to approve the workspace permissions the app needs (chat:write, im:write, channels:manage, users:read.email).
3
Choose your alerts channel
Pick the channel where incident-created notifications should post. You can change this later.
4
Done
The integration is live. The next incident created in your org will produce DMs to the on-call responder and a notification in the alerts channel.
Slack integration settings
Slash commands
The scaling.cloud Slack app exposes one slash command —/scaling — with several subcommands. Type /scaling help in any channel to see the full list.
Publishing public updates from Slack
/scaling publish <id> is the muscle-memory path for posting a customer-visible update without leaving Slack. It opens a modal containing:
- A multi-line Update field — what customers will read.
- An optional Change status selector — offers only the next valid lifecycle transition for the incident.
- A read-only Will appear on preview — lists the actual Status Page URL(s) the update will land on, computed server-side before the modal opens.
On submit, scaling.cloud posts the update through
PostIncidentUpdateUseCase exactly as the web form would, then drops a thread reply in the mapped incident channel: “Published update by @you → <body excerpt>” so the rest of the channel knows what went out.
Posting
internal notes from Slack is not yet exposed as a slash subcommand — use the web app or the API for internal updates. The /scaling publish flow is dedicated to the customer-visible path so the verb signals the intent.Limitations
- No explicit user-linking UI — identity matching is purely on email. Future work will add a settings page to map Slack and scaling.cloud users manually.
- Bot must be invited to private channels — auto-invites only work for channels the scaling.cloud bot can already see. For private channels, invite the bot first.
- Resolving from Slack does not collect a resolution note — if you want a public resolution note on the status page, use
/scaling publish <id>withstatusChange: resolvedbefore clicking Resolve, or post the resolution via the Post Incident Update API.
Removing the integration
To disconnect Slack:- Go to Settings → Integrations and open the Slack card.
- Click Disconnect.
- The scaling.cloud app stops posting messages to your workspace immediately. Existing alert messages remain in their channels but their buttons stop working.