- First, install the Checkly Slack App into your Slack Workspace by going to your integrations page and click Connect Slack workspace.
- Then, head to your alert settings, click “Add more channels” and select a new Slack channel.

# or @. For private channels, the Checkly Slack app needs to be explicitly invited to that channel by tagging it like @Checkly.
Checkly doesn’t check # channel names when you save the alert channel. It does match each @ entry to a person in your workspace, and refuses to save an entry it can’t match. Select Test alert channel to send a test message to each entry.
A Checkly account connects one Slack workspace at a time. Your integrations page shows it under Connected workspace. Connecting a different workspace replaces the current one. Alert channels with @ entries then stop sending direct messages until you open each channel and save it again.
To send alerts to a second Slack workspace, or to a workspace whose admins don’t approve the Checkly app, use a Slack incoming webhook with a Webhook alert channel instead.
Example Failed Slack Alert
For each check and / or monitor, the Slack alert message contains key information, a possible root cause analysis and key actions like rerunning the check.
The root cause analysis uses AI to analyze your logs, traces, test source code, error information and other artefacts available to Checkly. Be aware that AI can make mistakes so outputs should be verified independently.
Example Recovered Slack Alert
From the recovered Slack message, you can see the timestamp as well as a link to the check itself.
Migrating from the deprecated Slack webhook alert channels
Checkly previously only had Slack webhook based alert channels. These types of webhooks have been deprecated by Slack and are now also deprecated by Checkly. These webhook channels will keep working; we have not set a hard end-of-life date. You can recognize the deprecated channel in your alert channels list. It is named “Slack webhook” and has an alert icon.

Permissions
Checkly requests these Slack permissions for the Checkly Slack app to work within your workspace:
Connecting a workspace grants all of these permissions together. To send alerts, Checkly posts messages (
chat:write, chat:write.public) and looks up the people you send DMs to (users:read).
Troubleshooting
Test alert channel fails
If a test message can’t be posted, the error names the entry and the error Slack returned, for exampleFailed to post to #alerts (channel_not_found).
The alert channel says the Slack app isn’t installed
If a Slack alert channel shows The Checkly Slack app is not installed, no Slack workspace is connected to your Checkly account, for example because the integration was removed. The alert channel is kept, but Checkly sends no alerts to it until you connect a workspace again on your integrations page.The workspace doesn’t show as connected
Connect Slack workspace opens Slack in a popup. After you approve the app, the popup closes and your integrations page shows the workspace under Connected workspace. Checkly saves the connection only when the popup reports back to the Checkly page that opened it, so keep that page open until the popup closes. If Slack returns an error or you cancel, Checkly reports it, for exampleSlack OAuth denied: access_denied, and nothing is connected. Select Connect Slack workspace to try again.
Alerts don’t arrive
If the test message arrives but alerts don’t, check that:- the check is subscribed to the alert channel, in the channel’s Subscriptions section;
- the alert channel notifies for that event, under Notification events;
- the check changed state and met your alert threshold. Checkly sends alerts when a check changes state, not for every failed run. See Testing your alerts.