Blog · Engineering
Streamlining UptimeRobot Webhooks into WakeUp Dev for Zero‑Fatigue On‑Call
Integrate UptimeRobot webhooks with WakeUp Dev’s voice‑first alerts, using POST /v1/alert and unlimited seats to cut noise and keep on‑call teams focused.
· Enrique Drack
Integrating UptimeRobot Webhooks with WakeUp Dev
UptimeRobot gives you a simple HTTP callback whenever a monitored endpoint changes state. By sending that payload straight to WakeUp Dev’s /v1/alert endpoint you can turn a generic uptime check into a voice‑first on‑call alert without any extra plumbing.
How the Flow Works
- UptimeRobot posts a JSON payload to a Cloudflare Worker.
- The Worker validates the payload, extracts the check name and status, and forwards a minimal alert to WakeUp Dev.
- WakeUp Dev routes the alert to all on‑call seats (unlimited seats, no per‑seat cost) and plays a short prompt: “UptimeRobot reports a failure on . Press 1 to acknowledge.”
- The first staff member who presses 1 sends a digit‑1 ACK back to WakeUp Dev, which marks the alert as resolved.
Sample Cloudflare Worker
addEventListener('fetch', event => {
event.respondWith(handleRequest(event.request))
})
async function handleRequest(request) {
if (request.method !== 'POST') return new Response('Method Not Allowed', { status: 405 })
const body = await request.json()
// Basic validation
if (!body.check || !body.status) return new Response('Bad Request', { status: 400 })
const alert = {
message: `UptimeRobot: ${body.check} is ${body.status}`,
severity: body.status === 'down' ? 'critical' : 'warning',
source: 'uptimerobot'
}
const wakeupResponse = await fetch('https://api.wakeupdev.com/v1/alert', {
method: 'POST',
headers: {
'x-api-key': 'YOUR_API_KEY',
'Content-Type': 'application/json'
},
body: JSON.stringify(alert)
})
return new Response('Alert forwarded', { status: wakeupResponse.status })
}Cost‑Effective, Unlimited Seats
Because WakeUp Dev’s pricing is pay‑per‑alert, you pay only for the voice calls that actually reach your team. Unlimited seats mean every on‑call engineer receives the same voice prompt, but only one ACK is required to resolve the alert, keeping the noise down.
Reducing Noise with Filtering
- Use UptimeRobot’s “Only notify on status change” to avoid duplicate alerts.
- In the Worker, drop checks that are marked as “warning” if your team only cares about critical failures.
- Add a simple rate‑limit header to the Worker to prevent accidental spam.
By keeping the webhook payload small and the alert payload minimal, the entire round‑trip stays under 100 ms, which is fast enough for real‑time on‑call escalation.
---
💬 SRE & DevOps Insights
**Peer Question:** How do you currently filter non‑critical alerts before they hit your on‑call system?
Write to administrador@wakeupdev.com or continue from the FAQ.