Notification channels
Set up Email, Slack, Discord and webhook notification channels in Servor, test them, and use the cooldown to prevent alert spam.
A notification channel is a destination for your alerts — where Servor sends the message when a monitor changes status. Servor supports Email, Slack, Discord and Webhook channels. This page covers setting each one up, testing it, and the cooldown that keeps a noisy monitor from flooding you.
The channel types
Sends the alert to one or more email addresses. The simplest channel and a good default for a personal or backup route.
Posts the alert into a Slack channel via an incoming webhook URL from your Slack workspace.
Posts the alert into a Discord channel via a channel webhook URL from your Discord server.
Sends a JSON payload to any URL you control, so you can plug alerts into your own tools and automations.
Add a channel
Open notification channels
Go to your notification channel settings — open alert settings in Servor — and choose Add channel. Managing channels requires an admin or owner role — see roles and permissions.
Pick the type and enter its target
- Email — enter the recipient address(es).
- Slack — paste the incoming webhook URL from your Slack workspace.
- Discord — paste the channel webhook URL from Discord.
- Webhook — enter the URL Servor should POST to.
Send a test
Use Send test to fire a sample notification. Confirm it arrives in the right inbox or channel before you depend on it — see testing a channel.
Save
Save the channel. It's now available to select when you create an alert rule.
Getting a Slack webhook URL
In Slack, create an incoming webhook for the channel you want to post to (via a Slack app in your workspace). Slack gives you a URL that looks like https://hooks.slack.com/services/.... Paste that into the Slack channel in Servor.
Getting a Discord webhook URL
In Discord, open the target channel's settings → Integrations → Webhooks → New Webhook, then Copy Webhook URL. It looks like https://discord.com/api/webhooks/.... Paste that into the Discord channel in Servor.
Webhook payload
A webhook channel sends a JSON POST to your URL when an alert fires. Point it at an endpoint you control to trigger your own automations. A payload carries the monitor, its new status, and a timestamp, for example:
{
"monitor": "Marketing site",
"status": "down",
"previous_status": "up",
"timestamp": "2026-08-27T12:34:56Z"
}Test before you trust
Always send a test after creating a channel. A wrong webhook URL or a typo in an email address fails silently exactly when you need the alert most.
Testing a channel
Every channel has a Send test action. It sends a sample notification through the channel right away so you can confirm:
- The message actually arrives (right inbox, right Slack/Discord channel).
- It's routed where the team will see it.
- A webhook endpoint accepts the payload and does what you expect.
Retest after changing a webhook URL, rotating a Slack/Discord integration, or editing recipients.
Cooldown
To stop a flapping monitor from firing dozens of notifications, each channel has a cooldown — a minimum gap between notifications. After a channel sends an alert, it won't send another for that same monitor until the cooldown passes.
This works together with confirmed status changes: the monitor only flips status when a change holds, and the cooldown then caps how often you're re-notified about it. Set a longer cooldown for chatty or low-priority monitors, a shorter one where you need to know immediately.
Channels are shared across alerts
A channel you create can be used by many alert rules. Set it up once, then select it wherever you need it.