Turn Webhooks Into Phone Calls
WakeUp Dev connects monitoring webhooks to voice calls with human acknowledgement—built for DevOps and SRE on-call workflows.
Monitoring system
HTTP webhook
WakeUp Dev
Phone call
Press 1 to acknowledge
Escalation if unanswered
API example
The public alert endpoint accepts the raw alert body (plain text or JSON). Authentication is via the x-api-key header.
curl -X POST https://api.wakeupdev.com/v1/alert \
-H "x-api-key: YOUR_API_KEY" \
-H "Content-Type: application/json" \
-d '{"message":"API production down - HTTP 503"}'On success the API returns HTTP 202 with accepted: true and starts the cascade asynchronously. One credit is consumed when the alert is accepted.
Why use phone calls for critical alerts?
- Push notifications can be silenced or ignored when the phone is in Do Not Disturb.
- Email may not be read immediately during an overnight incident.
- A phone call can demand attention in a different way than text channels.
- WakeUp Dev adds explicit ACK (press 1) so you know someone confirmed—not just that a notification was sent.
Quick questions
- What is a webhook-to-phone-call alert?
- Your monitor sends HTTP POST to WakeUp Dev; WakeUp Dev places a voice call instead of (or in addition to) passive notifications.
- How does WakeUp Dev acknowledge an alert?
- During the call, the responder presses 1. That digit is captured via Twilio Gather and marks the alert ACKNOWLEDGED.
- What happens if nobody answers?
- WakeUp Dev escalates to the next phone in the cascade—shift roster, team members by order, or your verified emergency number—up to 8 attempts.
- Can I use any monitoring system that supports HTTP webhooks?
- Yes. Grafana, UptimeRobot, and custom scripts that can POST with a custom header are supported. WakeUp Dev requires the x-api-key header—for UptimeRobot, check that your webhook configuration supports custom HTTP headers before using this integration.