Overview

Send Monitor.us alerts to Callgoose SQIBS. A webhook notification posts each status change to your SQIBS API endpoint. SQIBS opens an incident when a monitor goes down and resolves it when the monitor is up again.

You need
A Monitor.us account with permission to manage notifications, and a SQIBS API token
Setup time
About 10 minutes
Result
Monitor.us monitors open and resolve SQIBS incidents

How it works

Monitor.us
Alert fires
A website, server or transaction monitor fails.
Monitor.us
Sends a webhook
Through a webhook, as JSON.
SQIBS
API filter matches
The filter decides whether to open or resolve, and the priority.
SQIBS
Incident opens
DOWN opens it, 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 Monitor.us template yet, so enter them by hand):
Part Payload JSON key Key value contains What it does
Resolve "status" UP Resolves the open incident.
Trigger "status" DOWN Opens an incident.
Match "monitor_id" Ties the UP message to the incident it opened.
Title from "monitor_name" Becomes the incident title.
Description from "description" Becomes the incident description.
  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 notification in Monitor.us

  1. In Monitor.us, go to Settings > Notifications and add an alert notification of type Webhook. Name it Callgoose SQIBS.
  2. Set Method to POST, Content Type to application/json, and the URL to your SQIBS endpoint:
https://<your-endpoint>/sqibs-api/v1/process?from=monitorus&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. Turn on recovery alerts, so SQIBS hears when a monitor is up again. Save the webhook.
  2. Open each monitor you want in SQIBS and, under its alert settings, choose the Callgoose SQIBS webhook.

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. Use the test option in the webhook settings, or point a test monitor at an address that does not answer.
  2. In SQIBS, a new incident opens. The payload looks like this (shortened):
{
  "event_type": "alert",
  "monitor_id": "981273",
  "monitor_name": "Website uptime",
  "status": "DOWN",
  "previous_status": "UP",
  "description": "Website is not reachable.",
  "checked_at": "2026-11-22T12:30:00Z"
}
  1. When the monitor recovers, Monitor.us sends "status": "UP" with the same monitor_id, 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 Monitor.us webhook.

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 Monitor.us reports a website down, SQIBS can run a workflow that restarts the web server and rechecks the page.

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: