Overview

Send Loadster monitor results to Callgoose SQIBS. Loadster runs your browser or protocol scripts on a schedule and posts each monitor event to a webhook. SQIBS opens an incident when a monitor run fails and resolves it when a later run passes.

You need
A Loadster account with a monitor, and a SQIBS API token
Setup time
About 10 minutes
Result
Failed monitor runs open SQIBS incidents; passes resolve them

How it works

Loadster
Alert fires
A monitor run fails.
Loadster
Sends a webhook
Through the account webhook, as JSON.
SQIBS
API filter matches
The filter decides whether to open or resolve, and the priority.
SQIBS
Incident opens
FAIL opens it, PASS 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 Loadster. It fills in these filter values:
Part Payload JSON key Key value contains What it does
Trigger "cycle"."status" FAIL Opens an incident.
Resolve "cycle"."status" PASS Resolves the open incident.
Match "monitor"."id" Ties the resolve message to the incident it opened.
Title from "cycle"."status" Becomes the incident title.
  1. Choose the Priority for these incidents and click Save.

The template matches the resolve message on "monitor"."id", which Loadster can send empty. Change Map incident with (trigger and resolve) to "monitor"."name", and Incident title from to "monitor"."name" too, so the title names the monitor instead of just FAIL.

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: Turn on webhooks in Loadster

  1. In Loadster, click your profile icon and choose Integrations. Scroll to Webhooks and turn them on.
  2. For the monitor events, enter your SQIBS endpoint:
https://<your-endpoint>/sqibs-api/v1/process?from=loadster&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 Save.

Step 3: Create a monitor

In your project, add a New Monitor that runs one of your scripts on a schedule, and click Create Monitor.

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. Break the script's target for a test, for example by pointing a step at a page that does not exist.
  2. In SQIBS, a new incident opens. Loadster's payload looks like this (shortened):
{
  "id": "66976184-3589-4c0d-b591-f9d242cd374d",
  "monitor": {
    "id": "",
    "name": "Checkout journey"
  },
  "cycle": {
    "status": "FAIL",
    "responseTimeAvg": 5151,
    "dateFinished": "2026-11-22T04:10:26.000Z"
  },
  "url": "https://loadster.app/"
}
  1. When a later run passes, Loadster sends "status": "PASS" for the same monitor, 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 Loadster webhook.

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 checkout journey fails, SQIBS can run a workflow that checks the payment and cart services and restarts the one that is not healthy.

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: