Webhook-based, no bot install
Uses a standard Discord webhook URL — no bot to install, no OAuth, no extra permissions needed on your server.
Webhook-based monitoring alerts for Discord — rich embeds with incident detail, region data, and recovery notifications delivered to any server channel, included on every plan.
Discord's embed format lets Site Qwality send structured, colour-coded alert cards with every relevant field — no parsing a wall of text to understand what failed and where.
Uses a standard Discord webhook URL — no bot to install, no OAuth, no extra permissions needed on your server.
Alerts arrive as Discord embeds with colour-coded severity, affected monitor, region, status code, and a direct link to the incident.
Send different monitors to different Discord channels, keeping critical alerts separate from low-priority warnings.
When a monitor recovers, a follow-up message goes to the same channel so the incident lifecycle is complete and visible.
Connect webhook URLs from different Discord servers — useful for teams that run separate servers per environment or client.
Every webhook delivery includes an HMAC signature so your server can verify the payload came from Site Qwality.
Unlike Slack or Teams, Discord's webhook system requires zero OAuth, zero bot permissions, and zero admin approval. Create a webhook in Discord channel settings, paste the URL into Site Qwality, and alerts flow immediately.
Paste your Discord webhook URL, choose which monitors use it, and optionally fire a test message to confirm. You can also create notification channels via the REST API if you're automating monitor provisioning.
typical Discord delivery after alert fires
bots or server permissions required
Discord integration on every plan, including free
of alerts include full incident detail in the embed
No. The integration uses a standard Discord webhook URL. You create the webhook in Discord channel settings, paste it into Site Qwality, and alerts start flowing — no bot, no OAuth.
Alerts arrive as Discord embeds with a colour bar (red for down, green for recovered), the monitor name, affected regions, HTTP status code, response time, and a link to the incident timeline.
Yes. Each monitor can have its own Discord webhook URL, so you can route critical production monitors to #ops-critical and staging monitors to #dev-alerts.
Yes. When a monitor recovers, a green-bar recovery embed is sent to the same channel, completing the incident record without any manual action.
Yes — all plans, including the free tier, include the Discord integration at no additional cost.
Every product starts free — uptime, cron, synthetic, logs, RUM, incidents, and status pages. No credit card required.