Webhooks are not arriving
You have created an alert rule with the Webhook channel, but your server receives nothing. Here is when SilentShield sends a webhook and what can stop it on the way.
When SilentShield sends a webhook
Webhooks are sent only by alert rules of an API key whose channel is Webhook. Once a minute, SilentShield checks every active rule. If its condition is met within the time window, it sends one POST request to the webhook URL saved on the “Notification Settings” page.
Causes
The rule has never fired
On the “Alert Rules” page of the key, the “Last fired” column shows when a rule last fired. If it says “never”, the condition has not been met yet and nothing was sent. Compare the threshold and operator with the figures in your analytics.
The rule is waiting for its time window
A rule fires at most once per time window (5m, 15m, 1h, 24h). After it has fired, it is only checked again once that window has passed: a rule with 24h sends at most once a day.
No webhook URL is saved
The rule only selects the channel; the address itself is saved on the “Notification Settings” page. Without an address the rule fires, but nothing is sent. Saving an address requires a plan that includes webhook integrations.
The address cannot be reached from the internet
SilentShield only delivers to public addresses. Local and internal targets such as localhost, 127.0.0.1, 10.0.0.0/8, 192.168.0.0/16 or 172.16.0.0/12 are rejected when you save and again when connecting, including after a redirect. For local tests, use a tunnel with a public HTTPS address.
Your server responds too slowly
Each attempt waits at most 5 seconds for the complete response. Reply with a 2xx status straight away and process the message afterwards, for example in a queue.
Your server responds with an error or a redirect
Only status codes 200 to 299 count as delivered. After a 5xx, 408 or 429 response, or if the connection fails, SilentShield tries again after 2 and after 8 seconds and then gives up. Other 4xx codes such as 401, 403 or 404 are not retried; a firewall or bot protection in front of your endpoint often answers with 403. After a 301, 302 or 303 redirect the request continues as GET without a body, so enter the final address.
The signature check fails on your server
If you have saved a secret, every request carries the X-Signature-256 header: sha256= followed by the HMAC-SHA256 of the body in hexadecimal. Compute it over the raw body exactly as received, before parsing the JSON; a body that has been parsed and serialised again has a different signature. Without a secret the header is missing.
What arrives at your server
A delivery looks like this. X-Event-ID stays the same for all attempts of one delivery; use it to detect duplicates.
POST /your-webhook HTTP/1.1
Content-Type: application/json
X-Event-ID: 8b1f2c3d-4e5f-4a6b-9c7d-0e1f2a3b4c5d
X-Signature-256: sha256=<hex>
{
"event_id": "8b1f2c3d-4e5f-4a6b-9c7d-0e1f2a3b4c5d",
"alert_rule_id": "2a7c9e1b-3d4f-4b6a-8c0e-1f2a3b4c5d6e",
"alert_name": "bot-rate",
"api_key_id": "5c6d7e8f-9a0b-4c1d-8e2f-3a4b5c6d7e8f",
"metric": "bot_rate",
"operator": "gt",
"threshold": 0.3,
"value": 0.42,
"fired_at": "2026-11-16T10:30:00Z"
}Checking the signature
Example in Node.js; rawBody is the unchanged request body:
const crypto = require("crypto");
function isValidSignature(rawBody, header, secret) {
const expected = "sha256=" +
crypto.createHmac("sha256", secret).update(rawBody).digest("hex");
const received = header || "";
return received.length === expected.length &&
crypto.timingSafeEqual(Buffer.from(received), Buffer.from(expected));
}
// header = req.get("X-Signature-256")How to set up rules and channels: Alert Rules