Overview
Send KIT.domains alerts to Callgoose SQIBS. Each monitored domain can post its notifications (downtime, DNS problems and more) to your SQIBS API endpoint, and SQIBS opens an incident per domain.
How it works
Want SQIBS to fix known issues before anyone is paged? See Fix known issues automatically.
Step 1: Add the API filter in SQIBS
- In SQIBS, open Services, choose the service that should receive these incidents, and click Add Or Update API Integration.
- In Select Integration Template, choose KIT.domains. It fills in these filter values:
| Part | Payload JSON key | Key value contains | What it does |
|---|---|---|---|
| Trigger | (none) | (anything) | No key, so every message opens an incident. |
| Resolve | "details" |
DNS Resolving problem |
Resolves the open incident. |
| Match | "domain" |
Ties the resolve message to the incident it opened. | |
| Title from | "domain" |
Becomes the incident title. | |
| Description from | "details" |
Becomes the incident description. |
- Choose the Priority for these incidents and click Save.
The template's resolve rule matches DNS Resolving problem, which is itself an alert, so a DNS problem would resolve an open downtime incident instead of reporting it. Turn off Auto resolve in the filter and close these incidents in SQIBS when the domain is healthy.
The template is a starting point, not a lock-in: every value stays visible and you can change it.
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 to a domain
- In KIT.domains, open the domain and go to Settings > Notifications.
- In the webhook URL, enter your SQIBS endpoint, with method POST:
https://<your-endpoint>/sqibs-api/v1/process?from=kitdomains&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.
- Choose which notifications to send, and click Update. Repeat for each domain.
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.
- Wait for the next check on a domain that has a problem, or add a test domain that does not resolve.
- In SQIBS, a new incident opens, titled with the domain. The payload looks like this:
{
"domain": "shop.example.com",
"incident_date": "2026-11-22 08:41:39",
"details": "Operation timed out after 5000 milliseconds with 0 bytes received"
}
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 domain's notification settings.
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 KIT.domains reports a site timing out, SQIBS can run a workflow that checks the web server and the DNS records and restarts the server if it is not answering.
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:
- Select Workflow: choose the automation workflow to run when this filter opens an incident.
- If success then make incident resolved: turn on to resolve the incident when the workflow succeeds.
- 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:
- Prometheus: incident auto remediation, a full worked example.
- Automation workflow: build a workflow from actions.
- Run workflows where your systems are: SSH, Bash, PowerShell, Python, Ansible, kubectl, Terraform.