Overview

Send Xitoring alerts to Callgoose SQIBS. A Xitoring webhook posts each check's status change to your SQIBS API endpoint. SQIBS opens an incident when a check goes into warning, critical or unknown, and resolves it when the check is OK again.

You need
A Xitoring account, and a SQIBS API token
Setup time
About 10 minutes
Result
Xitoring checks open and resolve SQIBS incidents

How it works

Xitoring
Alert fires
A check changes to warning, critical or unknown.
Xitoring
Sends a webhook
Through a webhook, as JSON.
SQIBS
API filter matches
The filter decides whether to open or resolve, and the priority.
SQIBS
Incident opens
Status 1, 2 or 3 opens it, 0 (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. Add a filter with these values (there is no built-in Xitoring template yet, so enter them by hand):
Part Payload JSON key Key value contains What it does
Trigger (filter 1) "status" 1 Opens an incident on warning.
Trigger (filter 2) "status" 2 Opens an incident on critical.
Trigger (filter 3) "status" 3 Opens an incident on unknown.
Resolve "status" 0 Resolves the open incident when the check is OK.
Match "check_id" Ties the recovery to the incident it opened.
Title from "name" Becomes the incident title.
  1. Choose the Priority for these incidents and click Save.

Add each numbered row as its own filter (same Match values). SQIBS needs every value in Key value contains to be present, so several values in one filter would never match.

SQIBS checks the Resolve filter first, so an OK message (0) always resolves and never opens a new 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 the webhook in Xitoring

  1. In Xitoring, open the notification settings and add a Webhook notification channel.
  2. Set the URL to your SQIBS endpoint:
https://<your-endpoint>/sqibs-api/v1/process?from=xitoring&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. Assign the channel to the servers and uptime checks you want in SQIBS, and 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. Lower a check's threshold on a test server so it goes critical.
  2. In SQIBS, a new incident opens. The payload looks like this:
{
  "id": 132,
  "group": "server",
  "sub_group": "service",
  "server_id": 55,
  "check_id": 335,
  "name": "MySQL",
  "type_human_readable": "MySQL",
  "unit": "%",
  "value": 50.55,
  "status": 2,
  "incident_time": "2026-11-22 06:14:25"
}
  1. When the check is OK again, Xitoring sends "status": 0 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 Xitoring webhook.

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 Xitoring reports MySQL critical, SQIBS can run a workflow that checks the MySQL service and restarts it if it is not answering.

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: