Overview

Send Better Stack Uptime incidents to Callgoose SQIBS. An outgoing webhook posts each incident change to your SQIBS API endpoint. SQIBS opens an incident when Better Stack starts one and resolves it when Better Stack resolves it.

You need
A Better Stack Uptime account with admin access, and a SQIBS API token
Setup time
About 10 minutes
Result
Better Stack incidents open and resolve SQIBS incidents

How it works

Better Stack
Alert fires
A monitor fails and Better Stack starts an incident.
Better Stack
Sends a webhook
Through an outgoing webhook, as JSON.
SQIBS
API filter matches
The filter decides whether to open or resolve, and the priority.
SQIBS
Incident opens
Started opens it, Resolved 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 Better Stack template yet, so enter them by hand):
Part Payload JSON key Key value contains What it does
Trigger "data"."attributes"."status" Started Opens an incident.
Resolve "data"."attributes"."status" Resolved Resolves the open incident.
Match "data"."id" The Better Stack incident id ties the resolve to its incident.
Title from "data"."attributes"."name" Becomes the incident title.
Description from "data"."attributes"."cause" 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 an outgoing webhook in Better Stack

  1. In Better Stack Uptime, open Integrations and add a Webhook integration. Name it Callgoose SQIBS.
  2. In the URL, enter your SQIBS endpoint:
https://<your-endpoint>/sqibs-api/v1/process?from=betterstack&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.

The token goes in the URL (or an Authorization: Bearer <your-token> header). SQIBS does not read other custom headers.

  1. Choose the incident events to send: at least started and resolved.
  2. Save, then add the integration to the escalation policy of the monitors you want in SQIBS.

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 send a test from the integration.
  2. In SQIBS, a new incident opens. The payload below shows the shape to expect. Field names can differ between versions, so send one test message first and copy the exact keys from the API log with the JSON key creator.
{
  "data": {
    "id": "391824756",
    "type": "incident",
    "attributes": {
      "name": "shop-web",
      "url": "https://shop.example.com",
      "cause": "Status 503",
      "started_at": "2026-11-22T10:15:00Z",
      "resolved_at": null,
      "status": "Started"
    }
  }
}
  1. When the monitor recovers, Better Stack sends the resolved status for the same incident 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 Better Stack 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 Better Stack reports an API endpoint down, SQIBS can run a workflow that restarts the service and confirms the endpoint answers.

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: