Last updated: 2026-07-19
PingWatchdog + Webhooks: Uptime Alerts via Webhooks
Send PingWatchdog alerts to any service that accepts webhooks. Slack, Discord, Teams, custom APIs, your own backend: if it has a URL, it can get alerts.
Send PingWatchdog uptime alerts to any webhook endpoint. Build custom integrations, trigger your own automation, or connect to tools we do not natively support. Set up in 2 minutes.
How it works
Prepare your webhook endpoint
Set up any HTTP server that can receive POST requests. This can be a Slack webhook, a custom API endpoint, a Zapier webhook, or any URL that accepts JSON. Make sure the endpoint is publicly accessible.
Add the webhook in PingWatchdog
In your PingWatchdog dashboard, go to Alert Channels and click Add Channel. Select Webhooks. Paste your endpoint URL and give the channel a name. Optionally add custom headers for authentication.
Assign to monitors
Edit any monitor and add your webhook channel. You can add multiple webhooks per monitor. Each webhook can point to a different service: one for Slack, one for your internal dashboard, one for Zapier automations.
What alerts you will get
Webhook alerts are HTTP POST requests sent to your endpoint with a JSON payload. The payload includes: monitor name, monitor URL, alert type (down, up, degraded), error details, timestamp, and a link to your PingWatchdog dashboard. Use this to trigger CI/CD rollbacks, post to custom dashboards, or integrate with any tool that accepts HTTP requests.
Setup guide
- Step 1: Set up an HTTP server or use an existing webhook URL from Slack, Discord, Zapier, or your own backend.
- Step 2: In PingWatchdog: Alert Channels > Add Channel > Webhooks. Paste the URL and add any auth headers.
- Step 3: Edit your monitors and add the webhook channel. Use the Test button to verify the endpoint receives alerts.
- Step 4: Done. Every alert now triggers an HTTP POST to your endpoint with the full alert payload.
Frequently asked questions
What is the webhook payload format?
The webhook sends a JSON POST with these fields: monitor_name, monitor_url, alert_type (down/up/degraded), error_message, status_code, probe_region, timestamp (ISO 8601), and dashboard_url. You can parse this in any language.
Can I add custom headers for authentication?
Yes. When you create a webhook channel in PingWatchdog, you can add custom HTTP headers. Use this for Bearer tokens, API keys, or any other authentication your endpoint requires.
What happens if my webhook endpoint is down?
PingWatchdog retries failed webhook deliveries up to 3 times with exponential backoff (1 minute, 5 minutes, 15 minutes). If all retries fail, the delivery is logged as failed in your alert history. Consider also adding an email or Slack channel as a backup for critical alerts.