Overview
Send Status.io status page incidents to Callgoose SQIBS. A webhook subscriber on your status page posts every incident update to your SQIBS API endpoint. SQIBS opens an incident when a status page incident is identified and resolves it when you mark it resolved.
How it works
Identified opens it, Resolved 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
- In SQIBS, open Services, choose the service that should receive these incidents, and click Add Or Update API Integration.
- In Select Integration Template, choose Status.io. It fills in these filter values:
| Part | Payload JSON key | Key value contains | What it does |
|---|---|---|---|
| Trigger | "current_state" |
Identified |
Opens an incident. |
| Resolve | "current_state" |
Resolved |
Resolves the open incident. |
| Match | "id" |
Ties the resolve message to the incident it opened. | |
| Title from | "title" |
Becomes the incident title. | |
| Description from | "details" |
Becomes the incident description. |
- Choose the Priority for these incidents and click Save.
The template opens incidents for the Identified state. If your team posts incidents as Investigating first, add a second filter with the same values and Investigating in Key value contains: the values in one filter must all match, so each state needs its own filter.
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 SQIBS as a webhook subscriber
- In the Status.io dashboard, open your status page and go to Notifications, then Webhook.
- Click Add Subscriber and in the URL field enter your SQIBS endpoint:
https://<your-endpoint>/sqibs-api/v1/process?from=statusio&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.
- Enter an email address for the subscriber (Status.io uses it for delivery problems) and click Add Subscriber.
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.
- Post a test incident on the status page with the state Identified.
- In SQIBS, a new incident opens with the status page incident title. Status.io's payload looks like this (shortened):
{
"id": "67516a65bd8cde119333200b",
"datetime": "2026-11-22T08:55:02.076Z",
"current_status": "Service Disruption",
"current_state": "Identified",
"components": [
{
"name": "Website"
}
],
"containers": [
{
"name": "Primary Data Center"
}
],
"title": "Checkout errors",
"details": "We are seeing errors at checkout and are working on a fix.",
"incident_url": "https://status.io/pages/incident/example/67516a65bd8cde119333200b"
}
- Resolve the status page incident. Status.io sends
"current_state": "Resolved"with the sameid, 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 Status.io subscriber.
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 the status page reports a disruption of the website component, SQIBS can run a workflow that collects health checks from the web servers and adds them to the incident.
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.