UptimeRobot Phone Alerts: Send UptimeRobot Alerts to a Phone

Send UptimeRobot alerts to a phone

UptimeRobot can notify you when a monitor goes down or comes back up. For critical availability alerts, you can route those notifications to WakeUp Dev as an HTTP webhook.

WakeUp Dev accepts the webhook, turns the incoming alert into a phone call to the configured on-call responder, and continues the cascade if nobody acknowledges.

Basic architecture

1. UptimeRobot monitor→
2. Webhook alert→
3. WakeUp Dev→
4. Phone call→
5. Human ACK→
6. On-call escalation

How the UptimeRobot integration works

1. Create or use an UptimeRobot monitor

   UptimeRobot detects the availability problem you care about.

2. Configure the webhook

   Configure UptimeRobot to send alert notifications to the WakeUp Dev webhook endpoint.

3. Send the alert

   UptimeRobot sends the HTTP request when the monitor triggers.

4. WakeUp Dev places the call

   WakeUp Dev calls the configured on-call responder.

5. Press 1 to acknowledge

   The responder presses 1 to ACK.

6. Escalate if nobody acknowledges

   If nobody answers or acknowledges, the configured on-call cascade continues.

UptimeRobot webhook configuration

WakeUp Dev uses the same public alert API for every HTTP webhook source. Configure UptimeRobot to POST to WakeUp Dev’s alert endpoint—no WakeUp Dev agent or native UptimeRobot app is required. WakeUp Dev requires the x-api-key header; check that your UptimeRobot webhook configuration supports custom HTTP headers before using this integration.

1. In UptimeRobot, add or edit a webhook alert contact for the monitor you want to escalate by phone.
2. Set the webhook URL to https://api.wakeupdev.com/v1/alert.
3. Use HTTP POST (WakeUp Dev only accepts POST).
4. If your UptimeRobot webhook contact supports custom HTTP headers, add x-api-key with your WakeUp Dev API key from the dashboard. WakeUp Dev rejects requests without a valid x-api-key (HTTP 401).
5. Save the alert contact and attach it to the monitor notification settings that should wake someone.
6. Trigger a test alert from UptimeRobot and confirm a phone call arrives; press 1 to ACK.

What WakeUp Dev expects

• Endpoint: POST https://api.wakeupdev.com/v1/alert
• Required header: x-api-key: YOUR_API_KEY (WakeUp Dev requirement—confirm your UptimeRobot plan/UI can send custom headers)
• Request body: raw alert text or JSON (WakeUp Dev reads the raw body, up to 4000 bytes)
• No native UptimeRobot integration—connection is HTTP webhook only
• On success, the API returns HTTP 202 with accepted: true and starts the on-call cascade

Unlike Grafana contact points, UptimeRobot uses webhook alert contacts on monitors. The WakeUp Dev endpoint and POST method are the same; whether UptimeRobot can attach a custom x-api-key header depends on UptimeRobot’s webhook options for your account.

Examples

Manual test

Use curl to verify WakeUp Dev accepts alerts before wiring UptimeRobot. This is a direct API test—not UptimeRobot’s native payload format.

curl -X POST https://api.wakeupdev.com/v1/alert \
  -H "x-api-key: YOUR_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{"message":"UptimeRobot: production site down"}'

Authentication is via the x-api-key header. The body is treated as alert text for the phone call.

UptimeRobot webhook body

WakeUp Dev does not require a UptimeRobot-specific JSON schema. UptimeRobot’s default webhook payload can be forwarded as-is; WakeUp Dev reads the raw request body and uses it as the alert text for voice synthesis.

A successful acceptance returns HTTP 202 with accepted: true. One alert credit is consumed when the alert is accepted.

Why send UptimeRobot alerts to a phone?

• Availability alerts can fire outside normal working hours when the on-call responder is away from email or chat.
• Push, email, and chat notifications can be missed overnight or in Do Not Disturb.
• A phone call can provide another notification channel when a monitor is down.
• Press-1 ACK asks for explicit human acknowledgement—not only that UptimeRobot delivered a webhook.
• On-call cascade escalation provides a path when the first responder does not acknowledge.

What happens after the alert

When WakeUp Dev accepts the webhook, it starts the configured on-call cascade.

The first responder receives a phone call with a voice summary of the alert body and is prompted to press 1 to acknowledge.

If the call is unanswered, fails, or ends without ACK, WakeUp Dev moves to the next number in the cascade until someone acknowledges or the cascade is exhausted.

Integrations

WakeUp Dev accepts critical alerts from monitors that send HTTP webhooks:

• UptimeRobot
• Grafana
• HTTP webhooks

Grafana phone alerts · On-call escalation · Webhook to phone call · What is WakeUp Dev · Full FAQ

UptimeRobot phone alerts FAQ