Post a confirmed outage
The alert goes out once enough independent EU locations fail the check often enough in a row, not on the first failed request; both thresholds sit in your package.
Use Uptimeify with Slack.
One incoming webhook, and every confirmed outage lands in the channel your team already has open. No second tool to check.
What lands in Slack
Everything the alert pipeline sends into Slack is on this list, and nothing beyond it. Read it once and you know what your team will see.
Post the recovery
The same channel gets the all-clear as soon as the check is green again.
Format with Block Kit
A header block and mrkdwn sections, with a fallback to plain text when the message would exceed Slack's block limits.
A channel per monitor
Each channel is its own webhook, so a client's outage reaches the people who look after that client instead of everyone.
Escalate in stages
Slack can be the first step and something louder the second, on the delay you set per channel.
Warn before the certificate expires
Expiring TLS certificates and domains reach the same channel, early enough to renew them without a rush.
Send a test message
The dashboard posts a test into the channel while you set it up, so the first real alert is not the first delivery attempt.
Retry a failed delivery
A rejected or timed-out request is retried on its own ladder, with every attempt recorded under History & Logs → Alerts.
Keep the webhook URL encrypted
The webhook URL is stored encrypted rather than as plain text in the channel configuration.
Teams that run their monitoring on Uptimeify
Minutes to set up. Then it runs on its own.
- manifest.ymldisplay_information:name: Uptimeifyfeatures:incoming_webhooks: truebot_user: false
1. Create the Slack app
On api.slack.com/apps, choose the manifest option and pick your workspace.
Webhook URL
hooks.slack.com/services/T0/B0/xxxxStored encrypted
2. Activate the incoming webhook
Turn on Incoming Webhooks, pick the channel the alerts should land in, and copy the URL Slack generates.
Uptimeify 09:41
shop.customer.com is offline
3 NodesHTTP 5033. Paste it into Uptimeify
Add the URL as a Slack channel, assign the monitors it covers, and send the test message.
Before you connect Slack.
An incoming webhook is enough, and that is what the setup creates. Uptimeify posts to the channel behind that webhook; it does not read your messages and needs no bot user.
Yes. Every channel is its own webhook, and you assign monitors and clients to it. A client's outage then reaches the people who look after that client, not everyone.
No. Your quota covers monitors and the monthly SMS and voice allowance. Alerts over email, webhook, Slack or Discord do not draw on it.
The delivery is retried on its own ladder, and each attempt lands under History & Logs → Alerts, so a channel that silently stopped working is visible instead of just quiet.
As soon as the outage is confirmed. How many re-checks that takes is yours to set per package, which is the same setting that keeps a single slow response from paging anyone.
Every alert, where your team already works.
Connect Slack once, and every confirmed outage reaches the channel that is already open.