
Post Better Uptime incidents to the incidents channel
Each incident appears with the monitor name, cause and status, so engineering and support see the same outage notice at the same time.
Incident NotificationSend Channel Message

When a site or API goes down, the people who fix it and the people who answer customers both need to hear. FlowMattic takes Better Uptime incident, on-call and monitor events and turns them into Slack posts, incident channels, on-call topics and handover messages, running from your WordPress site.
3 triggers 23 actions 7 example workflows 1 ready-made template Unlimited runs
When this happens in Better Uptime3 triggers
Do this in Slack14 actions
When Better Uptime fires Incident Notification, 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.

Each incident appears with the monitor name, cause and status, so engineering and support see the same outage notice at the same time.
Incident NotificationSend Channel Message

A Router reads the incident status. New incidents go to the on-call channel, resolutions go to the customer support channel so agents can tell customers the service is back.
Incident NotificationRouterSend Channel Message

A Filter passes only newly started incidents. FlowMattic creates a channel named after the monitor and sets the topic to the incident cause, keeping outage chatter out of general channels.
Incident NotificationFilterCreate ChannelSet Channel Topic

When the rota moves, the topic of the ops channel changes to the new on-call name, so anyone with an urgent question knows who to ping.
On-call Contact ChangeSet Channel Topic

The incoming engineer is found in Slack by email and gets a direct message that their shift has started, a quiet check that the handover happened.
On-call Contact ChangeFind User by EmailSend Direct Message

Monitor changes go to a private channel. A paused monitor that nobody unpaused is a blind spot, and the lead can spot it in the log.
Monitor NotificationSend Private Channel Message

Each Monday a Schedule fetches all monitors, CSV Creator writes them to a file and Slack uploads it, so the team can review what is watched and what is missing.
ScheduleGet All MonitorsCSV CreatorUpload File
At the end, every Better Uptime incident posts its monitor, cause and status to your Slack incidents channel.
Under Connects in FlowMattic, add a Slack connection with an account in the incidents channel.
Create a workflow with the Better Uptime Incident Notification trigger and follow its instructions to send Better Uptime events to the workflow.
Create a test incident or pause a test monitor so FlowMattic captures the incident fields.
Add Send Channel Message, choose the channel and build the text from the monitor name, cause, status and incident link. Test it and switch on.
1. Trigger in Better Uptime
Incident Notification
2. Action in Slack
Send Channel Message
Fields mapped from the earlier steps (a typical setup)
| From Better Uptime | To Slack |
|---|---|
| Monitor name | Message: service |
| Cause | Message: what failed |
| Status | Message: status |
| Started at | Message: since |
| Incident URL | Message: link |
A trigger starts a workflow. An action is something FlowMattic does in the app as a step.
Better Uptime and Slack connect through FlowMattic on your own site, with no separate automation account in the middle and no charge per run.
Customer-facing teams get the same incident and resolution posts as engineers, so they can answer customers without asking in the engineering channel.
On-call changes update a channel topic and message the incoming engineer, which removes the question of who is on duty today.
FlowMattic runs on your WordPress site with unlimited runs, so a noisy week of incidents does not change what you pay.
Add a Slack connection, create a workflow with the Better Uptime Incident Notification trigger and add Send Channel Message. Map the monitor, cause and status into the text, test with one incident and switch it on.
Yes. Add a Filter after the trigger that passes only the started or created status. Acknowledged and resolved events stop there, or go down another Router path.
Yes. Use Create Channel after a Filter for new incidents, with a name built from the monitor and the date, then Set Channel Topic with the cause. Invite the on-call engineer with Invite User To Channel.
Not from a Slack message with these workflows, which only post to Slack. Create Incident can run from a Webhook or another app's trigger, for example a customer report form.
No. FlowMattic runs on your WordPress site, so if that site is offline the workflow cannot run. Monitor other services this way and keep Better Uptime's own alerts for the site that hosts FlowMattic.
Did not find your answer? You can browse the help center or ask us directly.
Install 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. Better Uptime integration 1.0, Slack integration 1.0.