Overview
Send Sauce Labs test results to Callgoose SQIBS. A Sauce Labs webhook pushes test result events to your SQIBS API endpoint. SQIBS opens an incident when a job fails and resolves it when the same job passes again.
How it works
FAILED opens it, PASSED 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
- In SQIBS, open Services, choose the service that should receive these incidents, and click Add Or Update API Integration.
- In Select Integration Template, choose Sauce Labs. It fills in these filter values:
| Part | Payload JSON key | Key value contains | What it does |
|---|---|---|---|
| Trigger | "status" |
FAILED |
Opens an incident. |
| Resolve | "status" |
PASSED |
Resolves the open incident. |
| Match | "name" |
Ties the resolve message to the incident it opened. | |
| Title from | "name" |
Becomes the incident title. |
- Choose the Priority for these incidents and click Save.
SQIBS lists two identical Sauce Labs templates; either one fills in these values.
The template is a starting point, not a lock-in: every value stays visible and you can change it.
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 Sauce Labs
- In Sauce Labs, go to Account > Integrations and click Configure next to Webhooks.
- Click + New Configuration.
- In URL, enter your SQIBS endpoint:
https://<your-endpoint>/sqibs-api/v1/process?from=saucelabs&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.
- Choose the event. Pick Virtual Device Automation | All tests (or Real Device Automation | All tests). The Failed tests only events never send the passing run, so incidents would not resolve.
- Choose whose events to receive (your account, a team or the organization) 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.
- Run a test job that fails.
- In SQIBS, a new incident opens, titled with the job name. Sauce Labs' payload looks like this (shortened):
{
"id": "8f4b0e1c2d3a4b5c",
"status": "FAILED",
"name": "Checkout smoke test",
"build": "build-2026-11-22T04:44:14Z",
"automation_backend": "playwright",
"browser_name": "Chrome",
"os_name": "macOS",
"duration_sec": "77",
"error": "expect(locator).toBeVisible() failed"
}
- Fix the test and run it again. When the job with the same name is
PASSED, 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 Sauce Labs 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 the checkout smoke test fails against staging, SQIBS can run a workflow that checks the staging services and restarts the one that is not healthy.
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:
- Select Workflow: choose the automation workflow to run when this filter opens an incident.
- If success then make incident resolved: turn on to resolve the incident when the workflow succeeds.
- 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:
- Prometheus: incident auto remediation, a full worked example.
- Automation workflow: build a workflow from actions.
- Run workflows where your systems are: SSH, Bash, PowerShell, Python, Ansible, kubectl, Terraform.