Overview

Send UptimeRobot monitor alerts to Callgoose SQIBS. A webhook alert contact posts each down and up change to your SQIBS API endpoint. SQIBS opens an incident when a monitor goes down and resolves it when it is up again.

You need
An UptimeRobot plan with webhook alerts, and a SQIBS API token
Setup time
About 10 minutes
Result
UptimeRobot monitors open and resolve SQIBS incidents

How it works

UptimeRobot
Alert fires
A monitor goes down.
UptimeRobot
Sends a webhook
A webhook alert contact posts JSON.
SQIBS
API filter matches
The filter decides whether to open or resolve, and the priority.
SQIBS
Incident opens
alertType 1 (down) opens it, 2 (up) closes it.

Want SQIBS to fix known issues before anyone is paged? See Fix known issues automatically.

Step 1: Add the API filter in SQIBS

  1. In SQIBS, open Services, choose the service that should receive these incidents, and click Add Or Update API Integration.
  2. Add a filter with these values (there is no built-in UptimeRobot template yet, so enter them by hand):
Part Payload JSON key Key value contains What it does
Trigger "alertType" 1 Opens an incident when the monitor is down.
Resolve "alertType" 2 Resolves the open incident when it is up.
Match "monitorID" Ties the up alert to the incident it opened.
Title from "monitorName" Becomes the incident title.
Description from "alertDetails" The reason, for example a timeout.
  1. Choose the Priority for these incidents and click Save.

Not sure of a key? Send one test message first (step below), then build the filter from the real payload.

Find the right key with the JSON key creator
In the API Integration window, click the round {} button at the bottom right. Paste a payload that SQIBS received (copy it from the API log). SQIBS lists every key with its value, each with a copy button. Copy the key into Payload JSON key and the value into Key value contains. No need to read the JSON by hand.

Step 2: Add a webhook alert contact

  1. In UptimeRobot, open Integrations (or My Settings > Alert Contacts in the classic dashboard) and add a Webhook.
  2. Set Friendly Name to Callgoose SQIBS and URL to notify to your SQIBS endpoint:
https://<your-endpoint>/sqibs-api/v1/process?from=uptimerobot&token=<your-token>

Replace <your-endpoint> and <your-token> with the values from your SQIBS account. See how to get the endpoint URL and API tokens.

  1. Choose POST, send the value as JSON, and use this body. UptimeRobot replaces each *variable*:
{
  "monitorID": "*monitorID*",
  "monitorName": "*monitorFriendlyName*",
  "monitorURL": "*monitorURL*",
  "alertType": "*alertType*",
  "alertTypeName": "*alertTypeFriendlyName*",
  "alertDetails": "*alertDetails*",
  "alertDateTime": "*alertDateTime*"
}
  1. Turn on notifications for both down and up events, and save.
  2. Edit each monitor you want in SQIBS and tick the Callgoose SQIBS alert contact.

Step 3: Test it

The API log saves payloads only while API Tracking is on for the token. Turn it on under API Tokens before you test; it switches itself off after 48 hours.

  1. Pause a test monitor's target, or point it at an address that does not answer.
  2. In SQIBS, a new incident opens, titled with the monitor name.
  3. When the monitor is up again, UptimeRobot sends "alertType": "2" for the same monitorID, and SQIBS resolves the incident.

No incident? Open the API log (with API Tracking on). If the payload is there, the filter did not match it: paste it into the JSON key creator and check the keys. If it is not there, check the URL and token in the UptimeRobot alert contact.

Fix known issues automatically

Many alerts have a known fix: restart a service, clear a full disk, run a health check. SQIBS can run that fix for you the moment the incident opens. This is event-driven auto remediation. For example, when UptimeRobot reports an API down, SQIBS can run a workflow that restarts the API service and rechecks the health endpoint.

Incident opens
Workflow starts
SQIBS runs the automation workflow linked to the filter.
Fixed
Incident resolved
The issue is fixed before anyone has to step in.
Not fixed
Escalated to the engineer
After the waiting time you set, the escalation policy pages on-call as usual.

Safe by design. SQIBS runs only workflows your own engineers wrote and approved for your environment. Nothing is guessed or generated: the same steps an engineer would run by hand, run sooner. If the workflow does not fix the issue, the engineer is paged as usual.

To set it up, in the same API filter:

  1. Select Workflow: choose the automation workflow to run when this filter opens an incident.
  2. If success then make incident resolved: turn on to resolve the incident when the workflow succeeds.
  3. Waiting time for escalate to escalation policies: how many minutes to give the workflow before paging the on-call engineer.

Start with low-risk workflows, such as a health check, and add fixes as you come to trust them.

Learn more: