Skip to content

Notification channels

Besides email and the bell in the panel, your account can send its alerts to Slack, Discord or your own service. Each destination is a channel. An account can have up to 5 channels.

Only the account owner and super admins can use Notification channels under Integrations.

  1. In the sidebar, open Integrations, then Notification channels.
  2. Click Add channel.
  3. Choose Slack, Discord or Webhook. The dialog shows the steps for that destination.
  4. Enter a Name (up to 60 characters) and the Webhook address.
  5. Under Severity and Topics, choose which alerts this channel gets.
  6. Click Add channel, then click Test on the new channel.
  • Slack: in Slack, open api.slack.com/apps and create an app (or open one) in your Slack. Turn on Incoming Webhooks, choose Add New Webhook to Workspace, pick the channel and copy the Webhook URL. It starts with https://hooks.slack.com/services/.
  • Discord: open the channel’s settings, then Integrations, then Webhooks. Choose New Webhook, name it, pick the channel and copy the Webhook URL. It starts with https://discord.com/api/webhooks/.
  • Webhook: a public https address on your own service that accepts POST requests with a JSON body. It should answer with a 2xx status within 5 seconds.

A webhook address lets anyone post into the channel, so Netkeel stores it encrypted and never shows it again. The channel’s card shows only the host and the last characters. To replace it, click Edit and then Replace the address.

Each channel has its own filter:

  • Severity: Critical, Warning and Notice. New channels start with Critical and Warning.
  • Topics: Servers, Applications, Backups, Operations, Billing and Security. New channels start with all of them.
Topic Examples
Servers A server stopped reporting, low disk space, high memory, a service that is unhealthy or recovered.
Applications An application is down, a certificate needs attention, an update is available, a domain was released.
Backups A backup is overdue, off-site copies are failing.
Operations A background task failed.
Billing A payment failed, no payment method on file, a warning before servers are powered off, servers powered off or switched back on.
Security Notices about access to your account, and known vulnerabilities in a WordPress application’s plugins, themes or WordPress version.

For each alert, a channel gets one message when the alert opens, one if it becomes critical and one when it is resolved. A channel created after an alert opened is not told about it. A server that is offline is reported after five minutes, like the email.

Click Test on a channel’s card. Netkeel sends a message marked as a test straight away and shows whether it was delivered, with the HTTP status. You can send 6 tests an hour for each channel, and 20 an hour across all your channels.

Click Log to see the last 50 deliveries to the channel, kept for 14 days, with their result. The log never contains the address or the secret.

  • A failed delivery is tried up to 3 times: again after 1 minute, then after 10 minutes. A webhook that no longer exists (an error such as 404), a redirect or a refused address is not retried.
  • After 5 failed deliveries in a row the channel shows Failing and stops sending. An address that answers that it no longer exists (404 or 410) shows Failing straight away. Netkeel emails the account owner. This warning is never sent through a channel.
  • For a day after it starts failing, Netkeel checks the channel again by itself, less often each time, and brings it back once a delivery works. After that, a successful Test, or replacing the address, brings it back.
  • Turn a channel off without deleting it by unticking Send alerts to this channel when you edit it. It then shows Switched off.

A channel gets at most 30 messages an hour. If more alerts arrive, Netkeel sends one summary at the end of the hour saying how many were held back.

Netkeel checks the address when you add it and again before every delivery:

  • It must use https on the standard port, with no user name or password.
  • The host must be a public name. IP addresses, localhost and names for private networks, such as names ending in .local or .internal, are refused.
  • A Slack channel must use hooks.slack.com. A Discord channel must use discord.com or discordapp.com. A webhook can use any public host.
  • If the name resolves to a private, loopback or otherwise internal address, the delivery is refused. Netkeel connects only to the address it checked.
  • Redirects are never followed.

Names and messages in alerts come from your own servers and applications, so Netkeel makes them safe before sending: in Slack and Discord, mentions such as @channel and @everyone and clickable links in names do nothing.

Every request to a Webhook channel is signed, so your service can check that it comes from Netkeel. When you add a webhook channel, Netkeel shows a signing secret that starts with whsec_. Copy it then. It is shown once and cannot be read back. To get a new secret, delete the channel and create it again.

Netkeel sends a POST with a JSON body and these headers:

Header Value
Content-Type application/json
User-Agent Netkeel-Webhooks/1
X-Netkeel-Event alert
X-Netkeel-Delivery The delivery id. It is the same on every retry, so use it to ignore duplicates.
X-Netkeel-Timestamp The time of sending, in Unix seconds.
X-Netkeel-Signature v1= followed by the signature, in hexadecimal.

An example body:

{
"id": "6f1c0a52-0000-0000-0000-000000000000",
"type": "low-disk",
"state": "open",
"severity": "critical",
"title": "Disk almost full",
"message": "shop-server disk usage is 96%",
"workspace": { "id": "...", "name": "Acme" },
"target": { "kind": "server", "id": "...", "name": "shop-server" },
"startedAt": "2026-01-01T10:00:00.000Z",
"url": "https://example.com/servers/...",
"test": true
}

state is open or resolved (a resolved alert also has resolvedAt). test is only present on test messages. type is notice for messages that are not alerts and summary for the hourly summary. target can be null.

The signature is an HMAC-SHA256 of the timestamp, a dot and the raw request body, keyed with your signing secret, written in hexadecimal and prefixed with v1=:

v1=hex( HMAC_SHA256( signing_secret, timestamp + "." + raw_body ) )

To verify a request:

  1. Read the raw body exactly as it arrived. Do not parse and re-serialise it.
  2. Reject the request if X-Netkeel-Timestamp is more than 5 minutes away from your clock.
  3. Compute the signature as above and compare it with X-Netkeel-Signature in constant time.
Node.js
import crypto from "node:crypto";
export function verify(rawBody, headers, secret, toleranceSeconds = 300) {
const timestamp = headers["x-netkeel-timestamp"];
if (!timestamp || Math.abs(Date.now() / 1000 - Number(timestamp)) > toleranceSeconds) return false;
const expected = "v1=" + crypto.createHmac("sha256", secret).update(`${timestamp}.${rawBody}`).digest("hex");
const given = String(headers["x-netkeel-signature"] || "");
return given.length === expected.length && crypto.timingSafeEqual(Buffer.from(given), Buffer.from(expected));
}
# Python
import hashlib, hmac, time
def verify(raw_body: bytes, headers: dict, secret: str, tolerance_seconds: int = 300) -> bool:
timestamp = headers.get("X-Netkeel-Timestamp", "")
if not timestamp.isdigit() or abs(time.time() - int(timestamp)) > tolerance_seconds:
return False
signed = timestamp.encode() + b"." + raw_body
expected = "v1=" + hmac.new(secret.encode(), signed, hashlib.sha256).hexdigest()
return hmac.compare_digest(expected, headers.get("X-Netkeel-Signature", ""))

Slack and Discord channels are not signed. Their address is the secret.

Click Delete on the channel’s card and confirm. Alerts stop going to it straight away. The webhook itself is not touched: remove it in Slack, Discord or your own service if you no longer need it.