Overview

Send Dotcom-Monitor alerts to Callgoose SQIBS. A custom alert template formats each alert as JSON and a webhook posts it to your SQIBS API endpoint. SQIBS opens an incident when a device reports an error and resolves it when the device is OK again.

You need
A Dotcom-Monitor account with admin access, and a SQIBS API token
Setup time
About 20 minutes
Result
Dotcom-Monitor errors open SQIBS incidents; OK resolves them

How it works

Dotcom-Monitor
Alert fires
A device check fails (uptime or threshold).
Dotcom-Monitor
Sends a webhook
A webhook sends the custom JSON alert.
SQIBS
API filter matches
The filter decides whether to open or resolve, and the priority.
SQIBS
Incident opens
Error opens it, Ok 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 Dotcom-Monitor. It fills in these filter values:
Part Payload JSON key Key value contains What it does
Trigger "RecentResponse"."Status" Error Opens an incident.
Resolve "RecentResponse"."Status" Ok Resolves the open incident.
Match "DeviceName" Ties the resolve message to the incident it opened.
Title from "DeviceName" Becomes the incident title.
Description from "ErrorDetails" Becomes the incident description.
  1. Choose the Priority for these incidents and click Save.

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 JSON custom alert template

  1. In Dotcom-Monitor, go to Manage > Custom Alert Templates and click New Template.
  2. Change the format from HTML to JSON and paste this template. It is a shortened version of the old one (no tag list), so it always produces valid JSON:
{
  "MonitorName": "@Model.RootResponse.Monitor.Name",
  "MonitoringTime": "@Model.Monitor_DateTime",
  "ErrorDetails": @if (Model.FirstErrorResponse != null && Model.FirstErrorResponse.AllErrors != null && Model.FirstErrorResponse.AllErrors.Any())
  {
    var error = Model.FirstErrorResponse.AllErrors.FirstOrDefault();
    <text>"Error Type: @error?.ErrorType; Error Code: @error?.ErrorCode; Reason: @error?.Reason"</text>
  }
  else
  {
    <text>"No errors"</text>
  },
  "RecentResponse": {
    "Status": "@(Model.LastXResponses.FirstOrDefault()?.IsFail == true ? "Error" : "Ok")",
    "Start": "@Model.LastXResponses.FirstOrDefault()?.Start"
  },
  "PlatformType": "@Model.RootResponse.Device.PlatformType",
  "DeviceName": "@Model.RootResponse.Device.Name",
  "DeviceReportingUrl": "@Model.OnlineReportLink?CUID=@Model.OnlineReportCUID"
}
  1. Save the template.

Step 3: Send alerts to SQIBS

  1. Add (or edit) an alert group and add a Webhook address with your SQIBS endpoint:
https://<your-endpoint>/sqibs-api/v1/process?from=dotcommonitor&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. Choose the custom template from step 2 for that address.
  2. In each device, open Alert Settings, select the alert group under Select Groups, make sure Uptime Alert is on, and save the device.

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. Make a device fail, for example by lowering its response time threshold below what the site can meet.
  2. In SQIBS, a new incident opens, titled with the device name. The payload looks like this (shortened):
{
  "MonitorName": "Singapore",
  "MonitoringTime": "11/22/2026 2:42:35 PM",
  "ErrorDetails": "Error Type: Validation; Error Code: 300; Reason: Duration exceeded specified threshold",
  "RecentResponse": {
    "Status": "Error",
    "Start": "11/22/2026 2:43:00 PM"
  },
  "PlatformType": "ServerView",
  "DeviceName": "https://shop.example.com"
}
  1. When the device is OK again, Dotcom-Monitor sends "Status": "Ok" for the same device, 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 Dotcom-Monitor alert group.

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 Dotcom-Monitor reports the site slow from every location, SQIBS can run a workflow that checks the web servers and recycles the busiest one.

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: