How to Set Up Slack Notifications
Stay informed about your workflow executions by receiving real-time notifications directly in your Slack channels. Follow these steps to connect CloudCruise with your Slack workspace.Step 1: Go to Workspace Settings
Navigate to Workspace Settings in your CloudCruise dashboard.Step 2: Connect Your Slack Workspace
Click the “Connect to Slack” button and follow the authorization steps to connect your Slack workspace. This will grant CloudCruise permission to send messages to your Slack channels.Step 3: Add Our Slackbot to a Channel
In Slack, invite our CloudCruise Bot to any channel where you want to receive notifications:You must add the bot to channels in order to see them in the notification
settings dropdown.
Step 4: Write Notification Routing Rules
After connecting, head to the Notifications tab in Workspace Settings. A rule decides which run events reach which Slack channels. A workspace can have as many rules as it needs, each identified by a name. Rules are shared: anyone with edit access to the workspace can change any of them, whoever wrote it. Each rule has four parts:- Workflows — All workflows, or a fixed list. All workflows covers anything created later; a fixed list does not.
- Events — All events, or a fixed list (table below). All events covers any event we add later; a fixed list does not.
- Channels and mentions — where it delivers, and who gets @-mentioned. Mentions can be individual people or Slack user groups.
- Advanced — the failure-class filter.
Mentions require a recent Slack connection. If the picker prompts you to reconnect, disconnect and reconnect Slack from the Integrations page — user groups in particular need the
usergroups:read scope, which older connections do not carry.
Both Workflows and Events work the same way: picking the “all” option means “whatever exists at delivery time”, so the rule keeps up as the platform grows. Listing items instead freezes the rule to exactly those items.
Narrowing failures by class
Under Advanced, failure notifications can be narrowed by error class (service unavailable, account logged out, incorrect form inputs, …):- All failure classes — every failure delivers, including classes we add later and failures delivered before a class has been worked out.
- Naming specific classes — only those deliver. This freezes the set: a class we add later will not reach the rule until you add it, and a failure with no class yet does not reach it either.
When several rules match
Rules are additive, and delivery collapses per channel. If two rules both point at#alerts, that channel gets one message per event carrying the union of the mentions each attaches to it — never two. Two rules pointing at different channels produce one message each.
Expanding a rule on the Notifications page shows exactly what it covers and where it delivers.
Seeing a single workflow’s notifications
A workflow’s General settings page lists the rules that currently cover it, each linking back to the rule that produces it.Troubleshooting
I don’t see my channel in the dropdown
Make sure you’ve invited the CloudCruise Bot to the channel using/invite @CloudCruise Bot in Slack.
A channel shows in red on the rules table
The channel was renamed in Slack after the rule was written. Routing still works — rules match on the channel’s id, not its name. Open and re-save the rule to refresh the label.A rule shows “deleted workflow”
The rule names a workflow that no longer exists. It is harmless; edit the rule to drop the reference.Notifications aren’t being delivered
- Verify the bot is still in the channel
- Check the rule’s events — e.g. failures only notify if Run failed is checked
- Check the Advanced class filter — an
Onlylist, or the unclassified toggle, can suppress specific failures - Ensure your Slack workspace connection is still active in the integrations tab