Overview

Send Raygun errors to Callgoose SQIBS. Raygun posts to your SQIBS API endpoint when a new error occurs in an application, and SQIBS opens an incident for it.

You need
A Raygun application on the Team plan or higher, and a SQIBS API token
Setup time
About 5 minutes
Result
New Raygun errors open SQIBS incidents

How it works

Raygun
Alert fires
A new error occurs in your application.
Raygun
Sends a webhook
Through the application's webhook, as JSON.
SQIBS
API filter matches
The filter decides whether to open or resolve, and the priority.
SQIBS
Incident opens
The incident shows the error message.

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 Raygun. It fills in these filter values:
Part Payload JSON key Key value contains What it does
Trigger "eventType" NewErrorOccurred Opens an incident.
  1. Choose the Priority for these incidents and click Save.

The template sets no title. Set Incident title from to "error"."message" and Incident description from to "error"."url" so each incident says what failed and links to it in Raygun. Raygun does not send a message when you resolve an error, 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 the webhook in Raygun

Raygun webhooks are set up per application. To cover several applications at once, use Alerting in Raygun and send the alert to the webhook.

  1. Open the application, go to Integrations and click Webhook.
  2. In URL, enter your SQIBS endpoint:
https://<your-endpoint>/sqibs-api/v1/process?from=raygun&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. Enable the webhook and save your changes.

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. Send a test error from your application, or wait for a new error.
  2. In SQIBS, a new incident opens. Raygun's payload looks like this (shortened):
{
  "event": "error_notification",
  "eventType": "NewErrorOccurred",
  "error": {
    "url": "https://app.raygun.com/crashreporting/abc123/errors/42",
    "message": "TypeError: Cannot read properties of undefined (reading 'total')",
    "firstOccurredOn": "2026-11-22T10:01:12Z",
    "lastOccurredOn": "2026-11-22T10:01:12Z",
    "usersAffected": 1,
    "totalOccurrences": 1
  },
  "application": {
    "name": "shop-web",
    "url": "https://app.raygun.com/crashreporting/abc123"
  }
}

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 Raygun 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 Raygun reports a spike of errors from one service, SQIBS can run a workflow that checks its dependencies and restarts it if a health check 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: