Setting up webhook alerts

Webhook alerts let you receive clan.me notifications in any system that can accept an HTTP POST request. The same events that trigger email alerts can POST a structured JSON payload to a URL you control.

What webhooks deliver

Every alert type is available via webhook. The payload fires at the same moment as the email, with the same context data. Because the payload is JSON rather than formatted text, it is easier to parse programmatically and forward to other systems.

The payload structure

Each webhook POST sends a JSON body with these fields:

• event: the alert type, for example tps_drop or offline
• server: an object with your server's name, slug, and public url
• triggered_at: ISO 8601 timestamp of when the alert fired
• data: an object with the metric values relevant to this alert, such as TPS, heap percentage, or entity counts
• content: a plain-text summary of the alert, which Discord uses to render the message

{
  "event": "tps_drop",
  "server": {
    "name": "Example SMP",
    "slug": "example-smp",
    "url": "https://clan.me/minecraft/example-smp"
  },
  "triggered_at": "2026-06-15T20:14:00.000Z",
  "data": { "tps_5m": 12.4, "threshold": 14, "player_count": 38 },
  "content": "TPS drop on Example SMP: 12.4 TPS (threshold: 14)"
}

The fields inside data vary by alert type, matching the metrics shown in the equivalent email alert.

Common integrations

Discord: paste a Discord channel webhook URL straight into your alert settings. Every payload includes a content field, which is exactly what Discord needs to render the message, so it works with no extra setup.

Slack: Slack expects a text field rather than content, so point the webhook at a small relay, a Make, Zapier, or Cloudflare Worker step, that copies content into text before forwarding to Slack.

Custom monitoring: if you run Grafana, Datadog, or another monitoring tool with a webhook receiver, the structured payload maps cleanly to custom alert rules and dashboards.