Overview

Send TrackJS error notifications to Callgoose SQIBS. TrackJS channels support email, Slack and Microsoft Teams; a Teams channel posts a JSON message card to any URL, so you give it your SQIBS API endpoint. SQIBS opens an incident for each notification, such as a new error or an error rate increase.

You need
A TrackJS account with admin access, and a SQIBS API token
Setup time
About 5 minutes
Result
TrackJS notifications open SQIBS incidents

How it works

TrackJS
Alert fires
A new error appears, or the error rate rises.
TrackJS
Sends a webhook
Through a Microsoft Teams channel, as a JSON card.
SQIBS
API filter matches
The filter decides whether to open or resolve, and the priority.
SQIBS
Incident opens
The incident shows the error.

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 TrackJS. It fills in these filter values:
Part Payload JSON key Key value contains What it does
Trigger "@type" MessageCard Opens an incident.
Title from "summary" Becomes the incident title.
Description from "sections".[0]."activityTitle" Becomes the incident description.
  1. Choose the Priority for these incidents and click Save.

TrackJS does not send a message when errors stop, so close these incidents in SQIBS when the fix is out.

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 Teams channel in TrackJS

  1. In TrackJS, go to Settings > Notifications. In the channel list, add a Microsoft Teams channel and give it a name, for example CallgooseSQIBS.
  2. In Webhook URL, enter your SQIBS endpoint:
https://<your-endpoint>/sqibs-api/v1/process?from=trackjs&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. Save it, then subscribe the channel to the notification types you want, such as New Error or Error Rate Increase.

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. Trigger a test error in your application, for example throw new Error('TrackJS test').
  2. In SQIBS, a new incident opens, described with the error. TrackJS's card looks like this (shortened):
{
  "@type": "MessageCard",
  "@context": "http://schema.org/extensions",
  "themeColor": "eb503e",
  "summary": "TrackJS Notification",
  "sections": [
    {
      "activityTitle": "*New Error*<br>[TypeError: cart is undefined](https://my.trackjs.com/errors/filtered?hash=...)",
      "activitySubtitle": "12/03/2026 05:22:23 UTC | 2 times | Chrome | 1 url",
      "markdown": true
    }
  ]
}

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 TrackJS 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 TrackJS reports a new error right after a release, SQIBS can run a workflow that rolls the front end back to the previous build.

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: