When a Datadog monitor changes state, you can push that status directly into Alert24 so your services and status page reflect the real state without manual intervention. This uses Alert24's incoming webhook receiver.

Step 1: Create a webhook receiver in Alert24

Go to Settings → Webhook Receivers → Add receiver
Name it (e.g., "Datadog — Checkout Service")
Link it to the Alert24 Service you want to update
Set Status field path to alert_status (the Datadog template variable that carries the state)

Set Status mapping:

operational → Recovered, OK
degraded → Warn, Warning
down → Alert, Alerting, No Data

Enable Auto-create incidents if desired

Save and copy the webhook URL:

https://app.alert24.net/api/webhooks/incoming/YOUR_TOKEN

Step 2: Create a Datadog webhook

In Datadog, go to Integrations → Webhooks → + New
Set Name to alert24-status-SERVICENAME
Set URL to your Alert24 incoming webhook URL

Set Payload to:

{
  "alert_status": "$ALERT_STATUS",
  "monitor_name": "$MONITOR_NAME",
  "hostname": "$HOSTNAME",
  "event_title": "$EVENT_TITLE",
  "source": "datadog"
}

No custom headers needed — Alert24's incoming webhook URL is token-authenticated
Click Save

Step 3: Add to your monitors

In each Datadog monitor's Notify your team section:

@webhook-alert24-status-SERVICENAME

To send on both alert AND recovery:

{{#is_alert}}@webhook-alert24-status-SERVICENAME{{/is_alert}}
{{#is_recovery}}@webhook-alert24-status-SERVICENAME{{/is_recovery}}

Tips

One receiver per service: Create a separate Alert24 webhook receiver for each service you want to track. Each has its own token and service mapping.
$ALERT_STATUS values: Datadog sends Alert, Recovered, Warn, No Data. Map these to Alert24's operational, degraded, and down in the receiver's status mapping configuration.
vs. incident creation: The webhook receiver updates service status. The incident ingest guide creates incidents. You can use both together — the webhook receiver keeps the status page current while the incident ingest creates a trackable incident.