Overview

Send Checkly alerts to Callgoose SQIBS. A webhook alert channel posts each failure and recovery to your SQIBS API endpoint. SQIBS opens an incident when a check fails and resolves it when the check recovers.

You need
A Checkly account with admin access, and a SQIBS API token
Setup time
About 10 minutes
Result
Failing checks open SQIBS incidents; recoveries resolve them

How it works

Checkly
Alert fires
A browser or API check fails.
Checkly
Sends a webhook
Through a webhook alert channel, as JSON.
SQIBS
API filter matches
The filter decides whether to open or resolve, and the priority.
SQIBS
Incident opens
ALERT_FAILURE opens it, ALERT_RECOVERY 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 Checkly. It fills in these filter values:
Part Payload JSON key Key value contains What it does
Trigger "alertType" ALERT_FAILURE Opens an incident.
Resolve "alertType" ALERT_RECOVERY Resolves the open incident.
Match "checkId" Ties the resolve message to the incident it opened.
Title from "message" Becomes the incident title.
Description from "description" Becomes the incident description.
  1. Choose the Priority for these incidents and click Save.

Checkly also sends ALERT_DEGRADED (slow but passing). To open incidents for it too, add ALERT_DEGRADED to the trigger 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 webhook alert channel in Checkly

  1. In Checkly, open Alerts, click Add more channels and choose Webhook.
  2. Give it a name, set Method to POST, and in URL enter your SQIBS endpoint:
https://<your-endpoint>/sqibs-api/v1/process?from=checkly&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. Replace the body with this template, which has every key the SQIBS template uses:
{
  "checkId": "{{CHECK_ID}}",
  "checkType": "{{CHECK_TYPE}}",
  "alertType": "{{ALERT_TYPE}}",
  "message": "{{ALERT_TITLE}}",
  "description": "{{ALERT_TYPE}} {{STARTED_AT}} ({{RESPONSE_TIME}}ms) {{RESULT_LINK}}"
}
  1. Click Test webhook, then save. Subscribe your checks to the channel.

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. Click Test webhook, or make a check fail, for example by pointing it at a URL that returns 500.
  2. In SQIBS, a new incident opens. The payload looks like this:
{
  "checkId": "db8a44a2-971a-47f0-91e3-619fdf9eab15",
  "checkType": "BROWSER",
  "alertType": "ALERT_FAILURE",
  "message": "Check \"Shop home page\" has failed",
  "description": "ALERT_FAILURE 2026-11-22T10:43:22.610Z (4204ms) https://app.checklyhq.com/checks/db8a44a2/check-sessions/1"
}
  1. When the check passes again, Checkly sends ALERT_RECOVERY for the same checkId, 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 Checkly channel.

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 a Checkly browser check finds the login page failing, SQIBS can run a workflow that restarts the authentication service and reruns the check.

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: