Skip to main content
Slack destinations post incident alerts in a Slack channel. A war room destination goes further: it creates a private channel for each new incident and posts every update there. You can also ask the Squasher Agent questions in Slack.

Connect a Slack workspace

  1. Open your project and select Settings in the sidebar, then the Integrations tab.
  2. On the Slack card, select Connect.
  3. In Slack, choose the workspace and select Allow.
Squasher returns you to Integrations and shows a “Slack connected” message The workspace then appears in Connected Slack workspace when you add a destination. To use another workspace, select Disconnect on the Slack card and connect again. The project’s Slack destinations then use the new connection. If you change to another workspace, edit each destination so its channel is in that workspace.

What you need

  • A Slack workspace that is connected to the project. See Connect a Slack workspace.
  • The ID of the Slack channel, for example C0123456789. In Slack, open the channel details: the channel ID is at the bottom.
  • The owner, admin, or security admin role in the Squasher organization.

Post alerts in a channel

  1. Open your project and select Settings in the sidebar, then the Notifications tab.
  2. Under Add destination, choose Slack channel in Channel, and enter a Name.
  3. Choose the workspace in Connected Slack workspace, and enter the Channel ID and the Channel name.
  4. Select Add destination, then select Send test.
For a private channel, invite the Squasher app to the channel first. Each project can post to as many channels as you add destinations for.

Open a war room for each incident

  1. Under Add destination, choose Slack war room in Channel, and enter a Name.
  2. Choose the workspace in Connected Slack workspace.
  3. Optional: enter a New channel prefix (optional). The default is inc-. Use lowercase letters, digits, -, and _, up to 16 characters.
  4. Select Add destination.
To invite people to each new war room, create the destination with the Notifications API and set inviteUserIds to Slack user IDs. To keep war rooms after the incident resolves, set archiveOnResolve to false. The dashboard has no fields for these options.

What Squasher sends

To leave out the root cause and the recommended action, set behavior.includeAiSummary to false on the route. See Add a route with filters.

Ask the Squasher Agent

Agent requests are limited to the Slack user who connected the project. Other Slack users must not use that connection to read or change project data. If an older connection stops answering, disconnect it and connect it again to record the authorized user. Mention @Squasher in a channel, or send the app a direct message, to ask about your project. The agent answers in the thread. You can also open Squasher in the Slack assistant pane, from the AI apps entry in the Slack top bar or sidebar, and select a suggested prompt. The agent stays quiet in other messages, and it posts its own alerts only when it confirms a problem that affects users. React with :-1: on an agent alert to mark it as noise. See Squasher Agent.

Limits

  • You cannot edit a destination. To change the channel, remove the destination and add it again.
  • A war room posts updates only for incidents whose opened event it received. Incidents that were open before you added the destination get no war room.
  • Comment mentions go to a Slack channel only through a route with comment_mentioned. See Comment mentions.

Next steps

Notifications

Routes, events, and delivery rules for every destination.

Read AI triage

Learn what the triage result in the thread tells you.