UptimeRobot integration
Turn UptimeRobot DOWN and UP notifications into HowlOps incidents without writing a custom JSON template.
What this brings you
UptimeRobot keeps performing the check; HowlOps receives its state changes, opens an incident on DOWN, and resolves the same incident on UP. The monitor ID is used as the stable correlation key.
Setup
- In HowlOps, open Integrations, select UptimeRobot, and generate an endpoint.
- In UptimeRobot, open Integrations & API > Webhooks and create a webhook.
- Paste the generated HowlOps URL.
- Select Send default variables as POST parameters. No custom JSON is required.
- Enable both Down and Up notifications, assign the integration to a monitor, and send a test.
HowlOps also accepts UptimeRobot's custom JSON format. alertType=1 opens an
incident, alertType=2 resolves it, and expiry alerts use a separate fingerprint
so they cannot close an availability incident.
UptimeRobot documents a single delivery attempt for DOWN and UP webhooks. Keep the HowlOps endpoint reachable and use the delivery state shown on the integration card to spot a rejected payload.
Local contract test
From the repository root:
bash scripts/test-integration-contracts.sh
The test replays checked-in firing and resolved fixtures and verifies that both events share a fingerprint. It does not contact UptimeRobot or a running HowlOps stack.
Was this page helpful?