Integrations

Send alerts to a webhook

Add your own URL to receive metric alerts as signed JSON messages, test it, and verify each message on your server.

A webhook sends your metric alerts to a URL of yours as a JSON POST, so your own tools can act on them. Every message is signed per Standard Webhooks, so your server can check it came from Flamio.

Before you begin

  • To add, test or delete a webhook you need the Editor, Admin or Owner role.
  • Your server has a public https:// address that answers a POST with a 2xx status. Private and local addresses are refused.

Add the webhook

Click Settings > Integrations and scroll to Webhooks. Click Add webhook, enter a Name and the URL, and click Add.

Keep the signing secret

Webhook added shows the signing secret, starting with whsec_. Store it with your server's other secrets. Show secret shows it again later.

Send a test

Click Send test. Flamio posts a signed test message, and the row shows what your server answered, such as Test delivered with its HTTP status.

Use it in an alert

In Digests > Metric alerts, create or edit an alert and select the webhook under Webhook.

Result

When the alert fires or is resolved, Flamio posts one message to your URL. If your server does not answer with a 2xx, Flamio tries again for about an hour, with the same webhook-id, so you can drop a repeat. Redirects are not followed.

Delete removes the webhook; alerts that posted to it stop posting there.

Verify a message

Each message carries three headers:

HeaderValue
webhook-idThe message's id, the same on every retry
webhook-timestampWhen this attempt was sent, in Unix seconds
webhook-signaturev1, followed by the base64 HMAC-SHA256 signature

Verify it with a Standard Webhooks library, on the raw body as received:

import { Webhook } from 'standardwebhooks';

const webhook = new Webhook(process.env.FLAMIO_WEBHOOK_SECRET); // whsec_…
const message = webhook.verify(rawBody, request.headers); // throws when the signature or the time is wrong

Without a library: sign <webhook-id>.<webhook-timestamp>.<raw body> with HMAC-SHA256, keyed by the base64-decoded secret after whsec_, and compare the base64 result with the signature after v1,. Reject a timestamp more than a few minutes old.

The message

{
  "type": "onlive.alert.fired",
  "timestamp": "2026-11-22T10:06:12.000Z",
  "data": {
    "project": { "id": "…", "name": "Acme" },
    "alert": {
      "id": "…",
      "name": "Checkout visits",
      "kind": "threshold",
      "measure": "visits",
      "measureLabel": "Visits"
    },
    "firing": {
      "id": "…",
      "event": "fired",
      "value": 4,
      "expected": 10,
      "window": {
        "from": "2026-11-22T09:00:00.000Z",
        "to": "2026-11-22T10:00:00.000Z",
        "timezone": "Europe/Kyiv"
      }
    },
    "url": "https://…"
  }
}
FieldMeaning
typeonlive.alert.fired, onlive.alert.resolved, or webhook.test for Send test
data.alert.kindthreshold, anomaly, or traffic_drop for Alert when traffic drops
data.firing.valueThe number in the window
data.firing.expectedThe threshold of a threshold alert, or the usual level of an anomaly
data.firing.windowThe hour or day the alert looked at, with the alert's time zone
data.urlThe chart or metric in Flamio over the days before the window

A test message has type webhook.test and data.endpoint with the webhook's id and name.