UptimeRobot

Developer Tools

Website, API and SSL monitoring with downtime alerts.

Signature verification supported 3 events supported

Why use Hookfire with UptimeRobot?

Instant push notifications

Get notified on your phone the moment a UptimeRobot webhook fires. No more checking dashboards.

Subscribe to what matters

Choose exactly which UptimeRobot events trigger notifications. Filter out the noise.

Team-wide delivery

Control who on your team gets notified and how: push notifications, record only, or both.

Setup in under 2 minutes

Copy a webhook URL, paste it in UptimeRobot, and you're done. No code required.

Supported events

Event	Sample notification
Monitor down `1` 🔴 Acme API is down Connection Timeout - https://api.acme.com/health	🔴 Acme API is down Connection Timeout - https://api.acme.com/health
Monitor back up `2` 🟢 Acme API is back up Down for 420 seconds - https://api.acme.com/health	🟢 Acme API is back up Down for 420 seconds - https://api.acme.com/health
SSL or domain expiring `3` 🔐 Acme API: certificate or domain expiring Check the SSL certificate and domain renewal for https://api.acme.com/health	🔐 Acme API: certificate or domain expiring Check the SSL certificate and domain renewal for https://api.acme.com/health

What people use UptimeRobot alerts for

Hear about the outage before your users do Monitors going down, incidents opening and errors spiking, on the phone you carry.

How to connect UptimeRobot

UptimeRobot webhooks are available on Team and Scale plans.

Step 1: Create an Integration

Go to your organization’s Integrations page.
Click Add Integration and select UptimeRobot.
You’ll receive a unique Webhook URL. Copy it.

Step 2: Add the Webhook in UptimeRobot

In UptimeRobot, click Integrations in the left sidebar, then Add Integration → Webhook.
Paste your Hookfire webhook URL.
Turn off the options that send the default variables in the query string or as POST parameters.
Paste this into POST value and turn on Send as JSON (application/json):

{
  "alert_type": "*alertType*",
  "alert_name": "*alertTypeFriendlyName*",
  "monitor_id": "*monitorID*",
  "monitor": "*monitorFriendlyName*",
  "url": "*monitorURL*",
  "details": "*alertDetails*",
  "duration_seconds": "*alertDuration*",
  "alert_time": "*alertDateTime*",
  "dashboard_url": "*dashboardUrl*",
  "ssl_expiry_date": "*sslExpiryDate*",
  "ssl_days_left": "*sslExpiryDaysLeft*",
  "domain_expire_date": "*domainExpireDate*"
}

Add the custom header from Step 3.
Under Events to notify about, tick Down, Up and/or SSL & Domain expiry, then save.
Attach the integration to the monitors you want alerts for.

Step 3: Signing Secret (custom header)

UptimeRobot does not sign webhooks, so Hookfire checks a secret header instead:

Make up a long random string.
In the webhook’s custom headers, add X-Hookfire-Secret with that string as the value.
Paste the same string into the Signing Secret field on your Hookfire integration page.

UptimeRobot drops every custom header if they add up to more than 10 headers or 4 KB, and the webhook then arrives without the secret and is refused. Keep the header list short.

Step 4: Subscribe to Events

On your Hookfire integration page, toggle on the events you want to receive push notifications for. A monitor going down is a good one to mark high priority.

Step 5: Test

Click the Test button next to an event on your integration page. UptimeRobot sends each alert once and does not retry, so make sure the test reaches your phone before relying on it.

Supported Events

Event	Description
`1`	A monitor went down
`2`	A monitor is back up
`3`	An SSL certificate or domain is about to expire

The event is UptimeRobot’s *alertType* number, which is why the body above sends it as alert_type.

Reference: UptimeRobot webhook integration.