Webhooks alerts for uptime monitoring
Send uptime alerts to your own webhook endpoint. Webhooks are the most flexible integration for internal tools, automation pipelines, and custom incident workflows.
How UpDog + Webhooks works
Webhooks let you send UpDog monitor events to your own systems. When a monitor changes state, UpDog delivers an HTTP request to your endpoint so you can automate incident workflows, tickets, and internal alerts.
Common use cases
- Create or update incidents in internal tooling
- Open tickets and annotate deploys
- Fan out to multiple destinations from one pipeline
Implementation tips
- Return a fast 2xx and queue heavy work
- Deduplicate events (delivery is at-least-once)
- Use HTTPS and validate secrets/signatures if available
What you can do with UpDog + Webhooks
- Send webhook uptime alerts on downtime and recovery to your internal systems.
- Trigger automations: create incidents, open tickets, annotate deploys, or fan out to other channels.
- Build without lock-in: if your service can accept HTTP requests, it can receive UpDog events.
How to set it up (step-by-step)
- Create an HTTPS endpoint in your system that can receive POST requests.
- Create an alert for the monitor you want to route.
- In the alert modal, choose Webhooks as the destination.
- Add your endpoint URL and any configuration UpDog requests.
- Save the alert, then send a test event and verify the payload is received and processed.
Best practices
Keep your webhook fast
Return a quick 2xx response and enqueue the heavy work. Slow endpoints cause retries, timeouts, and duplicate processing.
Deduplicate events
Store an event ID or a (monitor, timestamp, state) key so your system doesn’t create duplicate incidents when retries happen.
Secure the endpoint
Use HTTPS, validate secrets/signatures when available, and restrict access at the network layer where possible.
Troubleshooting
- Webhook not firing: confirm the integration is enabled and the monitor is assigned to the webhook target.
- Non-200 responses: your endpoint should return a 2xx quickly; log and inspect failures server-side.
- Timeouts: enqueue processing and respond immediately.
- Receiving duplicates: implement deduplication and treat webhook delivery as “at least once.”
- Network blocks: ensure your infrastructure allows inbound traffic from UpDog and that DNS resolves correctly.
FAQ
Related features
Other integrations
Build your alert stack:
Start monitoring for free
Connect a webhook endpoint and automate your incident workflow in minutes.
Start free