Overview

Send Bugsee events to Callgoose SQIBS. A Bugsee webhook posts the events you choose, such as new issues and crashes, to your SQIBS API endpoint. SQIBS opens an incident for a new issue and resolves it when the issue is closed.

You need
A Bugsee account with admin access, and a SQIBS API token
Setup time
About 10 minutes
Result
Bugsee issues open and resolve SQIBS incidents

How it works

Bugsee
Alert fires
A user reports a bug or the app crashes.
Bugsee
Sends a webhook
Through a webhook, as JSON.
SQIBS
API filter matches
The filter decides whether to open or resolve, and the priority.
SQIBS
Incident opens
Issue state open opens it, closed 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 the Bugsee template that fits the alerts you send. Each fills in its own filter values:

Bugsee - Issue Events

Part Payload JSON key Key value contains What it does
Trigger "payload"."issue"."state" open Opens an incident.
Resolve "payload"."issue"."state" closed Resolves the open incident.
Match "payload"."app"."key" Ties the resolve message to the incident it opened.
Title from "type" Becomes the incident title.
Description from "payload"."issue"."summary" Becomes the incident description.

Bugsee - Feedback Events

Part Payload JSON key Key value contains What it does
Trigger "payload"."thread"."state" open Opens an incident.
Title from "type" Becomes the incident title.
Description from "payload"."message"."messages" Becomes the incident description.

Bugsee - App Events

Part Payload JSON key Key value contains What it does
Trigger "type" (anything) Opens an incident.
Title from "type" Becomes the incident title.
Description from "payload"."app" Becomes the incident description.

Bugsee - User Events

Part Payload JSON key Key value contains What it does
Trigger "type" (anything) Opens an incident.
Title from "type" Becomes the incident title.
Description from "payload"."user" Becomes the incident description.
  1. Choose the Priority for these incidents and click Save.

Most teams only need Issue Events. It matches the resolve message on the app ("payload"."app"."key"), so all issues of one app share one incident. To track each issue on its own, change Map incident with (trigger and resolve) to "payload"."issue"."key".

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 webhook in Bugsee

  1. In Bugsee, open Administration and choose Webhooks, then click Add webhook.
  2. Enter your SQIBS endpoint as the URL:
https://<your-endpoint>/sqibs-api/v1/process?from=bugsee&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 Next and choose the events, for example new issue reported and issue updated.
  2. Click Next, choose the applications, and save.

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. In the webhook list, click the three dots next to the webhook and choose the test option.
  2. In SQIBS, a new incident opens. Bugsee's payload looks like this (shortened):
{
  "id": "d6Gg0ftAW",
  "type": "issue.created",
  "created_on": "2026-11-22T10:53:24.033Z",
  "payload": {
    "app": {
      "key": "SHOP_IOS",
      "name": "Shop iOS"
    },
    "issue": {
      "key": "SHOP_IOS-128",
      "summary": "Checkout button does nothing",
      "type": "bug",
      "state": "open",
      "severity": "high"
    }
  }
}
  1. Close the issue in Bugsee. It sends "state": "closed" 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 Bugsee 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 Bugsee reports a crash spike in a new app version, SQIBS can run a workflow that turns off the feature flag for the new code path.

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: