What you get
- A project-specific channel target for notifications.
- Error alerts delivered to that connected project channel without a separate incoming webhook URL.
- Review updates when a hosted fix run opens a pull request.
- Threaded replies when your team mentions Squasher in a connected channel.
- Slack-native search across messages and files when you ask Squasher to find related discussion.
- Incident recaps that combine Squasher incident data with the current Slack channel and thread discussion.
- Follow-up handling in subscribed threads while Squasher is already responding.
- Native Slack cards with dashboard shortcuts for project, errors, logs, incidents, and monitors.
- Slack canvas drafts for incident briefs or handoffs when you explicitly ask for a durable Slack doc.
Setup
- Connect Slack from Integrations.
- Choose the channel Squasher should use for the project.
- Reconnect Slack if prompted so Squasher can use the latest search and canvas scopes.
- Enable the automation rule that sends review notifications.
- Create Slack alert rules from Alerts to route error notifications to the same connected channel.
Notes
- Different Squasher projects can notify different Slack channels.
- Squasher uses the connected project channel as context for Slack replies. If you mention Squasher in a channel that is not connected to a project, it will ask you to connect Slack from project settings first.
- Slack search respects the workspace install and Slack’s available permissions. If search results look incomplete, reconnect Slack and make sure Squasher is in the relevant private channel.
- Slack alert rules use the connected Slack app by default. Incoming webhooks remain available for teams that need a standalone Slack webhook target.
- You can combine Slack notifications with GitHub and Linear.
Agent handoff
squasher integrations connect slack, alert APIs/CLI, or MCP search("alerts") for alert-rule work.