Overview

Send Marker.io website feedback and bug reports to Callgoose SQIBS. A workspace webhook posts issue events to your SQIBS API endpoint. SQIBS opens an incident for each new issue and resolves it when the issue's status changes to resolved.

You need
A Marker.io workspace with admin access, and a SQIBS API token
Setup time
About 10 minutes
Result
Marker.io issues open and resolve SQIBS incidents

How it works

Marker.io
Alert fires
A visitor or tester reports an issue.
Marker.io
Sends a webhook
Through a workspace webhook, as JSON.
SQIBS
API filter matches
The filter decides whether to open or resolve, and the priority.
SQIBS
Incident opens
issue.created opens it, a resolved status 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. Add a filter with these values (there is no built-in Marker.io template yet, so enter them by hand):
Part Payload JSON key Key value contains What it does
Trigger "type" issue.created Opens an incident.
Resolve "type" issue.status_updated Status change event...
Resolve "data"."status" resolved ...to resolved: resolves the open incident.
Match "data"."id" One incident per issue.
Title from "data"."title" Becomes the incident title.
Description from "data"."description" Becomes the incident description.
  1. Choose the Priority for these incidents and click Save.

Both resolve rows must match, so only a change to resolved closes the incident. To page only on urgent reports, add a trigger row "data"."priority" contains urgent.

Not sure of a key? Send one test message first (step below), then build the filter from the real payload.

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 the webhook in Marker.io

  1. In Marker.io, go to Workspace Settings > Webhooks and click Create webhook.
  2. Set Name to Callgoose SQIBS and URL to your SQIBS endpoint:
https://<your-endpoint>/sqibs-api/v1/process?from=markerio&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. Under Events, choose Issue created and Issue status updated. Under Projects, choose all projects or the ones you want.
  2. Save. To test, open the webhook's menu and click Send sample webhook.

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 Send sample webhook, or report a test issue with the Marker.io widget.
  2. In SQIBS, a new incident opens. Marker.io's payload looks like this (shortened):
{
  "type": "issue.created",
  "webhookId": "68690db898b5767ca2c3fbd7",
  "webhookTimestamp": 1763806500000,
  "data": {
    "id": "6864f4ee8ea25470b6b7bc34",
    "markerId": "SHOP-12",
    "title": "Checkout button does nothing on Safari",
    "description": "Clicking Pay shows no response.",
    "status": "open",
    "priority": "high",
    "project": {
      "id": "67dd8d16c5821a340c9af705",
      "name": "Shop website"
    },
    "publicUrl": "https://marker.io/i/6864f4ee8ea25470b6b7bc34"
  }
}
  1. Set the issue to resolved in Marker.io. 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 Marker.io 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 a report says a page returns an error, SQIBS can run a workflow that checks the page and restarts the web service 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: