Post a confirmed outage
The embed 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 Discord.
One channel webhook, no bot and no developer account, and every confirmed outage lands as a rich embed in the channel you picked.
What lands in Discord
Everything the alert pipeline sends into Discord is on this list, and nothing beyond it. Read it once and you know what your team will see.
Post the recovery
A resolved incident always gets the recovery embed, green and marked up, in the same channel that carried the outage.
Format as a rich embed
Every event arrives as an embed whose left border is green for a recovery, orange for a warning and red for an outage.
Attach the screenshot
When the failing check captured a screenshot of the page, it is uploaded with the embed instead of only being linked.
Fill the embed with fields
Site, URL, customer, status, the error with its status code and the start and resolve times become fields, along with your own customer fields.
Warn before certificates and domains expire
Expiring TLS certificates, expiring domains and blocklist hits reach the same channel, early enough to act without a rush.
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.
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.
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.
1. Open the channel settings
Right click the channel the alerts should land in, choose Edit Channel, then Integrations and Webhooks.
Webhook URL
discord.com/api/webhooks/123456/xxxxStored encrypted
2. Create the webhook
Add a new webhook, give it a name your team recognises, and copy the URL Discord generates.
3. Paste it into Uptimeify
Add the URL as a Discord channel, assign the monitors it covers, and send the test message.
Before you connect Discord.
Neither. A webhook created in the channel settings is enough, which is what the setup uses. Uptimeify posts to that webhook and reads nothing in your server.
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, Discord or Slack do not draw on it.
Yes, as an attached file rather than a link, whenever the failing check captured one. Checks that take no screenshot, a port or a DNS check for instance, simply send the embed on its own.
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.
Every alert, where your team already works.
Connect Discord once, and every confirmed outage reaches the channel that is already open.