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 includes a JSON body with the following fields:

• alertType: the event name, for example tps_drop or offline
• serverSlug: your server's URL identifier
• serverName: the display name of your server
• timestamp: ISO 8601 timestamp of when the alert fired
• metrics: an object containing the relevant metric values at the time of the alert, such as TPS, MSPT, heap percentage, and entity count by world
• dashboardUrl: a direct link to your analytics dashboard

The full payload schema for each alert type is documented in the API reference.

Common integrations

Discord: paste your clan.me webhook URL into a Discord channel's webhook settings. clan.me will format the payload as a Discord-compatible embed automatically when it detects a Discord webhook URL.

Slack: use a Slack incoming webhook URL. clan.me will format the payload as a Slack message block when it detects a Slack webhook URL.

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.