Overview

Send ServerGuard24 alerts to Callgoose SQIBS. A custom integration posts each check result to your SQIBS API endpoint with a JSON data template. SQIBS opens an incident when a check is critical and resolves it when it is OK again.

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

How it works

ServerGuard24
Alert fires
A check turns critical.
ServerGuard24
Sends a webhook
A custom integration posts JSON.
SQIBS
API filter matches
The filter decides whether to open or resolve, and the priority.
SQIBS
Incident opens
CRITICAL opens it, 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. In Select Integration Template, choose ServerGuard24. It fills in these filter values:
Part Payload JSON key Key value contains What it does
Trigger "status" CRITICAL Opens an incident.
Resolve "status" OK Resolves the open incident.
Match "id" Ties the resolve message to the incident it opened.
Title from "server" Becomes the incident title.
Description from "output" Becomes the incident description.
  1. Choose the Priority for these incidents and click Save.

The template opens incidents for CRITICAL only. To page on warnings too, add a second filter with WARNING and the same Resolve and Match values.

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

  1. In ServerGuard24, go to Settings > System > Integrations and click New Integration.
  2. Set Description to Callgoose SQIBS, Type to Custom and Request Type to POST DATA.
  3. In URL, enter your SQIBS endpoint:
https://<your-endpoint>/sqibs-api/v1/process?from=serverguard24&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. In Additional Header, add Content-Type: application/json.
  2. In Data Template, paste:
{
  "id": "{ID}",
  "status": "{STATUS}",
  "output": "{OUTPUT}",
  "timestamp": "{TIMESTAMP}",
  "check": "{CHECK}",
  "server": "{SERVER}",
  "address": "{ADDRESS}"
}
  1. Tick Standard Integration and Action, and save. With Standard Integration on, every check sends its events to SQIBS.

Step 3: Add the servers to check

In Server, add the server or website and choose the checks (for example HTTP or Ping). They use the integration from step 2.

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. Add a check for an address that does not answer, or stop a test service.
  2. In SQIBS, a new incident opens, titled with the server name and described with the check output. The payload looks like this:
{
  "id": "184512",
  "status": "CRITICAL",
  "output": "HTTP CRITICAL: HTTP/1.1 503 Service Unavailable",
  "timestamp": "2026-11-22 10:15:00",
  "check": "HTTP",
  "server": "web-01",
  "address": "web-01.example.com"
}
  1. When the check is OK again, ServerGuard24 sends "status": "OK" with the same 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 ServerGuard24 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 ServerGuard24 reports the HTTP check critical, SQIBS can run a workflow that restarts the web server and runs the check again.

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: