Overview

Send Atatus alerts to Callgoose SQIBS. A webhook notification channel posts each alert to your SQIBS API endpoint. SQIBS opens an incident when the alert fires and resolves it when Atatus reports it as resolved.

You need
An Atatus project with admin access, and a SQIBS API token
Setup time
About 10 minutes
Result
Atatus alerts open and resolve SQIBS incidents

How it works

Atatus
Alert fires
An alert rule in a policy breaks its threshold.
Atatus
Sends a webhook
Through a webhook channel, as JSON.
SQIBS
API filter matches
The filter decides whether to open or resolve, and the priority.
SQIBS
Incident opens
wasResolved: 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 Atatus. It fills in these filter values:
Part Payload JSON key Key value contains What it does
Trigger "wasResolved" false Opens an incident.
Resolve "wasResolved" true Resolves the open incident.
Match "errorId" Ties the resolve message to the incident it opened.
Description from "message" 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 webhook channel in Atatus

  1. In Atatus, go to Alerting > Notification Channels and create a channel of type Webhook. Give it a name, for example CallgooseSQIBS.
  2. In URL, enter your SQIBS endpoint:
https://<your-endpoint>/sqibs-api/v1/process?from=atatus&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. Save the channel and click its test button to send a test message.

Step 3: Use the channel in an alert policy

  1. Go to Alert Policies and create a policy (or edit one). Set its incident preferences and choose the CallgooseSQIBS webhook channel.
  2. Add alert rules: choose the product (for example Browser or APM), the metric, the project and the threshold.
  3. Save the policy.

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. Break a rule's threshold, or use the channel's test button.
  2. In SQIBS, a new incident opens. Atatus's payload looks like this (shortened):
{
  "projectName": "shop-web",
  "projectType": "browser",
  "message": "TypeError: cart is undefined",
  "errorId": "6703bd645583adbc9c7ff279:5d54bde522ca99c55c35719b3c1a5956",
  "url": "https://shop.example.com/cart",
  "wasResolved": false,
  "occurredAt": "Sun Nov 22 2026, 10:46 am UTC"
}
  1. When the alert resolves, Atatus sends "wasResolved": true with the same errorId, 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 Atatus channel.

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 Atatus reports a spike in API errors, SQIBS can run a workflow that checks the backend health endpoint and restarts the service if it fails.

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: