Integrations

OpenClaw Integration

DeadPing integrates with OpenClaw in two ways: alert notifications routed to an AI agent when a monitor goes down, and a skill that lets your OpenClaw agent query monitor status, anomalies, and ping history on demand.

OpenClaw is an AI agent platform. Instead of sending a Slack message or paging an on-call engineer when a monitor fails, DeadPing can trigger your OpenClaw agent — which can investigate the failure, run recovery scripts, notify your team, or open a ticket automatically. Pro plan required.

Alert Channel Setup

Configure OpenClaw as an alert channel so DeadPing triggers your AI agent when a monitor goes down, recovers, or detects an anomaly.

Go to Settings → Integrations
Click OpenClaw to expand the card
Enter your Webhook URL — the hooks endpoint on your OpenClaw instance (e.g. https://your-openclaw.com/hooks)
Enter your Hook Token — the shared secret configured in your OpenClaw hooks settings
Optionally enter an Agent ID to route alerts to a specific agent. Leave blank to use your default agent.
Click Save

Once configured, DeadPing sends a POST to your webhook URL whenever a monitor changes state.

Payload Format

Alerts are sent as JSON with Authorization: Bearer <token>:

Down alert payload

POST https://your-openclaw.com/hooks
Authorization: Bearer <hook-token>
Content-Type: application/json

{
  "message": "ALERT: Monitor \"nightly-backup\" is DOWN. Expected every 60m — last ping: Mon, 09 Mar 2026 03:00:12 GMT. Grace period: 300s. View: https://deadping.io/dashboard/abc123",
  "agentId": "your-agent-id"   // omitted if not configured
}

Recovery alert payload

{
  "message": "RECOVERED: Monitor \"nightly-backup\" is back up after ~14 minutes of downtime. View: https://deadping.io/dashboard/abc123"
}

Anomaly alert payload

{
  "message": "ANOMALY: Monitor \"billing-sync\" — Duration spike: 12340ms actual vs 3100ms baseline (4.2x deviation). View: https://deadping.io/dashboard/def456"
}

OpenClaw Skill

Install the DeadPing skill in OpenClaw so your agent can query monitor status, list anomalies, and acknowledge issues on demand — without waiting for an alert to be triggered.

Install the Skill

In OpenClaw, navigate to Skills and add a new skill
Point it at: https://deadping.io/openclaw-skill.md
Create a DeadPing API key at Settings → API Keys
Set the API key as the Bearer token for the skill

Available Tools

Tool	Description	Plan
`list_monitors`	List all monitors with current status, last ping time, and expected interval	All
`get_monitor`	Get full details and recent ping history for a specific monitor	All
`create_monitor`	Create a new monitor with name, interval, grace period, and optional cron schedule	All
`update_monitor`	Rename, reschedule, or pause/resume a monitor	All
`delete_monitor`	Delete a monitor and all its associated data	All
`list_anomalies`	List open anomaly events (duration spikes, frequency deviations, error surges)	Pro+
`acknowledge_anomaly`	Dismiss an anomaly event after reviewing it	Pro+

Example Interactions

Check status

"Which of my monitors are currently down?"

→ Agent calls list_monitors, filters by status: "down"
  Response: "2 monitors are down: 'nightly-backup' (missed 3 hours ago)
  and 'billing-sync' (missed 12 minutes ago)."

Investigate a failure

"What happened with the nightly-backup monitor last night?"

→ Agent calls get_monitor, inspects ping history and exit codes
  Response: "The last successful ping was at 03:01 UTC. The 03:05 ping
  returned exit code 1 with output: 'ERROR: No space left on device'.
  No ping received after that."

Review anomalies

"Do I have any open anomalies?"

→ Agent calls list_anomalies
  Response: "1 open anomaly: 'billing-sync' took 12.3s on the last run,
  which is 4.2x above its 3.1s baseline. Detected 2 hours ago."

Acknowledge after review

"Acknowledge the billing-sync anomaly, I already looked into it."

→ Agent calls acknowledge_anomaly with the event ID
  Response: "Done. The billing-sync anomaly has been acknowledged."

Authentication

The skill uses your DeadPing API key as a Bearer token. Create one at Settings → API Keys. API keys have read/write access to your monitors and anomaly events. Treat them like passwords.

Plan Requirements

Alert channel (down/recovery/anomaly alerts sent to OpenClaw) — Pro plan required
Skill tools list_monitors, get_monitor, create_monitor, update_monitor, and delete_monitor — available on all plans with an API key
Skill tools list_anomalies and acknowledge_anomaly — Pro+ plan required