Overview

Send Site Qwality alerts to Callgoose SQIBS. A webhook integration posts each check result to your SQIBS API endpoint. SQIBS opens an incident when a check fails and resolves it when the next check succeeds.

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

How it works

Site Qwality
Alert fires
An HTTP check fails.
Site Qwality
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
Status failed opens it, success 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 Site Qwality. It fills in these filter values:
Part Payload JSON key Key value contains What it does
Trigger "data"."status" failed Opens an incident.
Resolve "data"."status" success Resolves the open incident.
Match "data"."http_job_id" Ties the resolve message to the incident it opened.
Title from "data"."request_headers"."user-agent" Becomes the incident title.
  1. Choose the Priority for these incidents and click Save.

SQIBS lists two identical Site Qwality templates; either one fills in these values. The template takes the title from the request user agent, which is the same for every check. Change Incident title from to "data"."final_uri" and set Incident description from to "data"."failure_reason".

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 integration in Site Qwality

  1. In Site Qwality, go to Integrations, click Add Integration and choose Webhook. Give it a name.
  2. In URL, enter your SQIBS endpoint:
https://<your-endpoint>/sqibs-api/v1/process?from=siteqwality&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. Click Add.

Step 3: Use it in notifications and monitors

  1. In Notifications, click + next to the notification settings (or a group you created), choose Webhook and pick the integration. Click Add.
  2. On the Dashboard, click Add Monitor, configure the check, select that notification group and click Submit.

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. Monitor an address that returns an error.
  2. In SQIBS, a new incident opens. Site Qwality's payload looks like this (shortened):
{
  "data": {
    "http_job_id": "4b8e1f0a-2c3d-4e5f-8a9b-0c1d2e3f4a5b",
    "final_uri": "https://shop.example.com",
    "failure_reason": "status",
    "response_http_code": 503,
    "request_duration_ms": 18,
    "status": "failed",
    "created_at": "2026-11-22T04:42:50Z"
  }
}
  1. When the next check succeeds, Site Qwality sends "status": "success" for the same http_job_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 Site Qwality 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 Site Qwality reports the shop returning 503, SQIBS can run a workflow that restarts the application server and checks the page 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: