Overview

Send Visualping change alerts to Callgoose SQIBS. A Visualping job checks a web page on a schedule and posts to your SQIBS API endpoint when the page changes. SQIBS opens an incident for each change, described with Visualping's summary of what changed.

You need
A Visualping account, and a SQIBS API token
Setup time
About 5 minutes
Result
Page changes open SQIBS incidents

How it works

Visualping
Alert fires
A watched page changes.
Visualping
Sends a webhook
Through the job's webhook, as JSON.
SQIBS
API filter matches
The filter decides whether to open or resolve, and the priority.
SQIBS
Incident opens
The incident describes the change.

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 Visualping. It fills in these filter values:
Part Payload JSON key Key value contains What it does
Trigger "important" (anything) Opens an incident.
Title from "important" Becomes the incident title.
Description from "summarizer" Becomes the incident description.
  1. Choose the Priority for these incidents and click Save.

The template titles the incident with Visualping's important value, which is often a placeholder. Set Incident title from to "description" (the job name) and keep the description from "summarizer". Changes are not failures, so choose a low Priority unless the page is critical.

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: Create a job with a webhook

  1. In Visualping, click New Job and enter the page URL. Give the job a name and choose how often to check and what to compare (visual or text).
  2. In the job's Notifications section, choose Webhook and enter your SQIBS endpoint:
https://<your-endpoint>/sqibs-api/v1/process?from=visualping&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 Create Job.

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. Change the watched page, or point a job at a page that changes often.
  2. In SQIBS, a new incident opens. Visualping's payload looks like this (shortened):
{
  "job_id": 5999749,
  "url": "https://status.example-vendor.com",
  "description": "Vendor status page",
  "datetime": "Sun Nov 22 2026 05:08:04 GMT+0000",
  "important": "Status changed",
  "summarizer": "The vendor now reports degraded API performance in EU regions.",
  "view_changes": "https://visualping.io/jobs/5999749"
}

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 Visualping job.

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 vendor's status page changes, SQIBS can run a workflow that checks your integration with that vendor and switches to a backup provider if it fails.

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: