Overview

Send Uptrends monitor alerts to Callgoose SQIBS. A custom integration posts each alert and each OK message to your SQIBS API endpoint, with a JSON body you define. SQIBS opens an incident when an alert fires and resolves it when Uptrends sends OK for the same incident.

You need
An Uptrends account with permission to manage alerting, and a SQIBS API token
Setup time
About 15 minutes
Result
Uptrends alerts open and resolve SQIBS incidents

How it works

Uptrends
Alert fires
A monitor breaks an error condition.
Uptrends
Sends a webhook
Through a custom integration, as your JSON body.
SQIBS
API filter matches
The filter decides whether to open or resolve, and the priority.
SQIBS
Incident opens
Type Alert opens it, Ok 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. In Select Integration Template, choose Uptrends. It fills in these filter values:
Part Payload JSON key Key value contains What it does
Trigger "alert"."type" alert Opens an incident.
Resolve "alert"."type" ok Resolves the open incident.
Match "incident"."key" Ties the resolve message to the incident it opened.
Title from "alert"."type" Becomes the incident title.
Description from "alert"."description" Becomes the incident description.
  1. Choose the Priority for these incidents and click Save.

The template titles the incident with the alert type (Alert). Set Incident title from to "monitor"."name" so the title says which monitor failed.

The template is a starting point, not a lock-in: every value stays visible and you can change it.

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 custom integration in Uptrends

  1. In Uptrends, go to Alerting > Integrations and click Add integration. Choose Custom integration.
  2. Give it a name, for example CallgooseSQIBS, and set the API URL to your SQIBS endpoint:
https://<your-endpoint>/sqibs-api/v1/process?from=uptrends&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. On the Customizations tab, keep the method POST and set the request body for the alert and OK messages to:
{
  "alert": {
    "alertGuid": "{{@alert.alertGuid}}",
    "type": "{{@alert.type}}",
    "description": "{{@JsonEncode({{@alert.description}})}}",
    "timestampUtc": "{{@alert.timestampUtc}}",
    "firstErrorUtc": "{{@alert.firstErrorUtc}}",
    "firstErrorCheckUrl": "{{@alert.firstErrorCheckUrl}}"
  },
  "incident": {
    "key": "{{@incident.key}}"
  },
  "monitor": {
    "guid": "{{@monitor.monitorGuid}}",
    "name": "{{@monitor.name}}",
    "url": "{{@monitor.url}}"
  }
}
  1. Click Save.

Step 3: Use the integration in an alert definition

  1. Go to Alerting > Alert definitions and open the definition your monitors use (or create one).
  2. On an escalation level, turn on the CallgooseSQIBS integration, and save.

Step 4: 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. Let a monitor break its error condition, for example a page load time threshold.
  2. In SQIBS, a new incident opens. With the body above, the payload looks like this:
{
  "alert": {
    "alertGuid": "c2faab1d-0f5c-49b7-b0fb-1d0b03cbea85",
    "type": "Alert",
    "description": "First Contentful Paint exceeded its threshold of 1600 ms.",
    "timestampUtc": "2026-11-22T04:17:12",
    "firstErrorUtc": "2026-11-22T04:17:12",
    "firstErrorCheckUrl": "https://app.uptrends.com/Report/ProbeLog/Check/163920824567"
  },
  "incident": {
    "key": "9e3528d7-346d-4a8b-b602-d4dcfcbc6f34-0-163920824567"
  },
  "monitor": {
    "guid": "9e3528d7-346d-4a8b-b602-d4dcfcbc6f34",
    "name": "Shop home page",
    "url": "https://shop.example.com"
  }
}
  1. When the monitor is OK again, Uptrends sends "type": "Ok" with the same incident.key, 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 Uptrends integration.

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 Uptrends reports the home page loading slowly, SQIBS can run a workflow that clears the application cache 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: