Overview

Send Spectate uptime and performance alerts to Callgoose SQIBS. A webhook integration posts each check failure and recovery to your SQIBS API endpoint. SQIBS opens an incident when a check fails and resolves it when Spectate reports the recovery.

You need
A Spectate account with access to the project, and a SQIBS API token
Setup time
About 10 minutes
Result
Spectate failures open and resolve SQIBS incidents

How it works

Spectate
Alert fires
A monitor check fails, for example a response time threshold.
Spectate
Sends a webhook
Through a webhook integration, as JSON.
SQIBS
API filter matches
The filter decides whether to open or resolve, and the priority.
SQIBS
Incident opens
failed opens it, recovered 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 Spectate template yet, so enter them by hand):
Part Payload JSON key Key value contains What it does
Trigger "status" failed Opens an incident.
Resolve "status" recovered Resolves the open incident.
Match "incident"."id" Ties the resolve message to the incident it opened.
Title from "monitor"."label" Becomes the incident title.
Description from "incident"."cause" Becomes the incident description.
  1. Choose the Priority for these incidents and click Save.

Spectate keeps the same incident.id from failure to recovery, so each Spectate incident has exactly one SQIBS incident.

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 integration in Spectate

  1. In Spectate, go to Integrations and add a Webhook integration named Callgoose SQIBS.
  2. Enter your SQIBS endpoint as the URL:
https://<your-endpoint>/sqibs-api/v1/process?from=spectate&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. Open Projects, choose the project, and link the integration to it (or to individual monitors under Monitors). Save.

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. Make a monitor fail, for example by setting a very low response time threshold.
  2. In SQIBS, a new incident opens, titled with the monitor label. Spectate's payload looks like this (shortened):
{
  "status": "failed",
  "monitor": {
    "id": "9dd0a0df-b76b-46b3-9da6-afc3b512da76",
    "label": "shop.example.com"
  },
  "check": "performance-hard-threshold",
  "incident": {
    "id": "c542efdb-b5dd-4ada-958b-c2cb80e28905",
    "started_at": "2026-11-22 11:48:01",
    "resolved_at": null,
    "severity": "medium",
    "cause": "Hard threshold of 500ms exceeded."
  }
}
  1. Put the threshold back. When Spectate sends "status": "recovered" for the same incident, SQIBS resolves it.

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 Spectate 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 Spectate reports a slow page, SQIBS can run a workflow that purges the CDN cache for the site and rechecks the response time.

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: