Skip to main content

Documentation Index

Fetch the complete documentation index at: https://docs.scaling.cloud/llms.txt

Use this file to discover all available pages before exploring further.

The Slack integration lets your team get paged in Slack — as DMs and channel notifications — and lets on-call responders acknowledge and resolve incidents from Slack with a single click.
Slack incident alert

​
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 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 matches your Slack account to your Scaling account by email address. Both must be:
  • In the same Scaling organization.
  • Using the same email on both sides.
Guests and external Slack users are rejected with an ephemeral “you aren’t a member” message.
If your Slack email differs from your Scaling 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 dashboard, go to Settings → Integrations and click the Slack card.
2

Authorize the Scaling 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 settings

​
Slash commands

The Scaling Slack app exposes one slash command — /scaling — with several subcommands. Type /scaling help in any channel to see the full list.
SubcommandWhat it does
/scaling who-is-oncall [schedule]Show who is currently on call. Optional filter by schedule name.
/scaling incidentsList the currently open incidents in your org.
/scaling create-incidentOpens a modal to file a new incident (title, severity, on-call schedule).
/scaling status <id> <status>Advance an incident through its lifecycle (investigating → identified → monitoring → resolved).
/scaling publish <id>Opens a modal to post a public incident update on a status page.
/scaling helpShow this 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.
Before the modal opens, Scaling runs the same publishing gate the web form does:
RejectionWhyWhat you see
NO_PUBLIC_SURFACEThe incident’s affected components don’t overlap any published Status Page.Ephemeral message with a link to Status Page settings — the modal does not open.
INCIDENT_RESOLVED_NO_FURTHER_UPDATESThe incident is already resolved — no further updates are accepted (you may still redact).Ephemeral message — the modal does not open.
On submit, Scaling 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 users manually.
  • Bot must be invited to private channels — auto-invites only work for channels the Scaling 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> with statusChange: resolved before clicking Resolve, or post the resolution via the Post Incident Update API.

​
Removing the integration

To disconnect Slack:
  1. Go to Settings → Integrations and open the Slack card.
  2. Click Disconnect.
  3. The Scaling app stops posting messages to your workspace immediately. Existing alert messages remain in their channels but their buttons stop working.