Blog · Engineering

Streamlining UptimeRobot Webhook Ingestion with WakeUp Dev Voice Escalation

Streamlining UptimeRobot Webhook Ingestion with WakeUp Dev Voice Escalation

Learn how to ingest UptimeRobot webhooks into WakeUp Dev, trigger voice alerts, and ACK with digit‑1 for efficient on‑call escalation.

· Enrique Drack

WakeUp Dev’s webhook‑first architecture makes it trivial to hook into any monitoring system that can emit an HTTP POST. UptimeRobot is a popular uptime monitoring service that sends a JSON payload to a configured URL whenever a check changes state. By routing that payload straight into WakeUp Dev, teams can eliminate the need for an intermediate alert‑manager or custom code.

Ingesting UptimeRobot Webhooks

  • In UptimeRobot, create or edit a check and add a webhook under *Notifications > Webhooks*.
  • Point the webhook URL to https://api.wakeupdev.com/v1/alert.
  • Add the header x-api-key: YOUR_API_KEY to authenticate.
  • UptimeRobot will POST a payload that looks like this:
{
  "hostname": "db-prod-01",
  "status": "down",
  "checkName": "PostgreSQL DB",
  "lastCheck": 1710000000
}

WakeUp Dev accepts the payload as-is, mapping the status field to an alert severity and the hostname to the target. The service then triggers a voice call to the on‑call roster.

Voice ACK Flow

To keep alert fatigue low, WakeUp Dev uses a simple Twilio Gather that listens for a single digit. The TwiML looks like this:

<?xml version="1.0" encoding="UTF-8"?>
<Response>
  <Gather numDigits="1" action="https://api.wakeupdev.com/v1/ack" method="POST">
    <Say voice="alice">Alert: PostgreSQL DB is down. Press 1 to acknowledge.</Say>
  </Gather>
  <Say>We didn’t receive an ACK. Please call back.</Say>
  <Hangup/>
</Response>

When the on‑caller presses **1**, the action URL receives the digit and marks the alert as acknowledged. Because WakeUp Dev is seat‑agnostic, every team member can receive the call without additional licensing costs.

Pay‑Per‑Alert and Unlimited Seats

Unlike traditional on‑call platforms that bill per seat, WakeUp Dev charges only for the voice minutes used. A single alert that lasts 30 seconds costs a fraction of a cent, regardless of how many users are on the roster. This model scales naturally when adding new teams or rotating schedules.

curl -X POST https://api.wakeupdev.com/v1/alert \
  -H "Content-Type: application/json" \
  -H "x-api-key: YOUR_API_KEY" \
  -d '{
        "hostname": "web-prod-02",
        "status": "up",
        "checkName": "Frontend",
        "lastCheck": 1710001234
      }'

The response includes an alertId that can be used for programmatic ACKs or status queries.

WakeUp Dev’s webhook‑centric design, combined with voice ACKs and a pay‑per‑alert model, gives SREs a lean, cost‑effective way to keep on‑call teams focused on real incidents.

💬 SRE & DevOps Insights

**Peer question:** How would you modify the Twilio Gather to support a multi‑digit confirmation code for high‑severity alerts?

Write to administrador@wakeupdev.com or continue from the FAQ.

Streamlining UptimeRobot Webhook Ingestion with WakeUp Dev Voice Escalation | WakeUp Dev