Overview

Send Uptime.com check alerts to Callgoose SQIBS. A Custom Postback URL integration posts each alert and recovery to your SQIBS API endpoint. SQIBS opens an incident when a check goes down and resolves it when it is up again.

You need
An Uptime.com account with admin access, and a SQIBS API token
Setup time
About 10 minutes
Result
Uptime.com checks open and resolve SQIBS incidents

How it works

Uptime.com
Alert fires
A check fails.
Uptime.com
Sends a webhook
Through a Custom Postback URL integration, as JSON.
SQIBS
API filter matches
The filter decides whether to open or resolve, and the priority.
SQIBS
Incident opens
state_is_up: false opens it, true 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 Uptime.com. It fills in these filter values:
Part Payload JSON key Key value contains What it does
Trigger "state_is_up" false Opens an incident.
Resolve "state_is_up" true Resolves the open incident.
Match "check_id" Ties the resolve message to the incident it opened.
Title from "check_full_name" Becomes the incident title.
Description from "output" Becomes the incident description.
  1. Choose the Priority for these incidents and click Save.

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 Postback URL integration

  1. In Uptime.com, go to Notifications > Integrations and click Add Integration Profile. Choose Custom Postback URL (Webhook).
  2. Give it a name, and under Assign to Contacts choose the contact your checks alert (for example Default).
  3. In URL, enter your SQIBS endpoint:
https://<your-endpoint>/sqibs-api/v1/process?from=uptimecom&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. Tick Legacy Payload for the short payload the template expects, and click Save.
  2. Click Start Test to send a test payload.

Step 3: Alert the contact from your checks

Each check alerts the contacts set on it. Make sure the checks you want in SQIBS use the contact from step 2 (new checks use Default unless you change it).

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. Click Start Test on the integration, or let a check fail.
  2. In SQIBS, a new incident opens, titled with the check name. Uptime.com's payload looks like this (shortened):
{
  "date": "Nov. 22, 2026, 9:50 a.m. UTC",
  "server_name": "shop.example.com",
  "check_name": "Home page",
  "check_full_name": "shop.example.com / Home page",
  "check_type": "HTTP(S)",
  "check_id": 418823,
  "check_url": "https://shop.example.com",
  "state_is_up": false,
  "output": "HTTP CRITICAL: HTTP/2 503 - 189 bytes in 0.161 second response time"
}
  1. When the check is up again, Uptime.com sends "state_is_up": true for the same check_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 Uptime.com 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 Uptime.com reports a 503 from the home page, SQIBS can run a workflow that restarts the web tier 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: