Checkly runs your API and browser checks and calls a webhook when one fails, recovers or slows down. FlowMattic turns that call into Slack posts that reach the right people: failures to the owning team, recoveries to support, the current state in a channel topic. Developer and SRE teams decide in the workflow who hears about which check.
1 trigger 14 actions 6 example workflows 2 ready-made templates Unlimited runs
When this happens in Checkly1 trigger
Do this in Slack14 actions
1. TriggerWebhook Alert Channel2. ActionSend Channel MessageWhen Checkly fires Webhook Alert Channel, FlowMattic runs Send Channel Message in Slack with the data from that event.
You build this in the FlowMattic workflow builder on your own site. See the setup steps
Each one uses only triggers and actions the two integrations ship today, plus FlowMattic's own tools. Where the library has a ready-made template, import it instead of building from scratch.
Ready-made templateA Filter keeps only failures, so the channel hears when a check breaks and not about every run. The post names the check and links to the result.
Webhook Alert ChannelFilterSend Channel Message
View the template A Router reads the alert type. Failures go to the engineering channel, recoveries to support so they can tell customers, and degraded performance to a watch channel.
Webhook Alert ChannelRouterSend Channel Message
A Lookup Table maps check names to team channels. The checkout check goes to payments, the login check to identity, without one shared channel for everything.
Webhook Alert ChannelLookup TableSend Channel Message
On a failure the topic of your status channel says which check is down, and on recovery it goes back to all clear. Anyone joining the channel sees the state at a glance.
Webhook Alert ChannelRouterSet Channel Topic
When a critical check fails, the engineer named as its owner is found by email and gets a direct message, which is harder to miss than a busy channel.
Webhook Alert ChannelFilterFind User by EmailSend Direct Message
An API request step creates an issue in your own tracker for each failure, and the Slack post includes the issue link, so the fix is tracked from the start.
Webhook Alert ChannelFilterAPI requestSend Channel Message
At the end, every failed Checkly check posts its name, type and result link to your Slack channel.
In FlowMattic, open Connects and add a Slack connection with an account in the alerts channel.
Create a workflow with the Checkly Webhook Alert Channel trigger and copy its URL into a webhook alert channel in Checkly.
Attach the alert channel to the checks you want, then send a test from Checkly so FlowMattic captures the alert fields.
Add a Filter that passes failed alerts, then Send Channel Message with the check name and result link. Test it and switch on.
1. Trigger in Checkly
Webhook Alert Channel
3. Action in Slack
Send Channel Message
Fields mapped from the earlier steps (a typical setup)
| From Checkly | To Slack |
|---|---|
| Check name | Message: check |
| Alert type | Message: state |
| Check type | Message: API or browser |
| Result link | Message: details |
A trigger starts a workflow. An action is something FlowMattic does in the app as a step.
Checkly and Slack connect through FlowMattic on your own site, with no separate automation account in the middle and no charge per run.
Routing by check name puts each failure in front of the people who can fix it instead of in one noisy channel.
Customer-facing teams see when a service is back and can update customers without asking engineering.
FlowMattic has unlimited runs on every plan, so frequent checks and a bad day of alerts do not change what you pay.
Create a workflow with the Checkly Webhook Alert Channel trigger, add its URL as a webhook alert channel in Checkly and subscribe your checks. Add a Filter for failures and Send Channel Message, then switch it on.
Yes. Add a Filter or Router on the alert type so only degraded alerts pass, and post them to a separate performance channel.
Yes. A Lookup Table that maps check names or tags to channels is the simplest, or a Router with one path per team.
Yes. Add an API request step after the Filter to call your issue tracker's API, then include the returned link in the Slack message.
Did not find your answer? You can browse the help center or ask us directly.
Slack and Google Sheets149 shared templates
Slack and Airtable44 shared templates
Slack and Fluent Forms42 shared templates
Slack and FluentCRM35 shared templates
Slack and ClickUp28 shared templates
Slack and Fluent Support21 shared templates
Slack and WooCommerce18 shared templates
Slack and Notion17 shared templatesInstall FlowMattic, connect both accounts and import a template. Every run stays on your own server.
30-day money-back guarantee Unlimited workflows and runs Self-hosted
Reviewed 27 Oct 2026. The example workflows are written with AI from the real triggers and actions of both integrations and checked against them. Checkly integration 1.0.0, Slack integration 1.0.
