Overview

Send Spacelift run events to Callgoose SQIBS. A Spacelift webhook posts run state changes to your SQIBS API endpoint. SQIBS opens an incident when a run fails and resolves it when the next run on the stack finishes.

You need
A paid Spacelift account with admin access, and a SQIBS API token
Setup time
About 10 minutes
Result
Failed runs open SQIBS incidents; finished runs close them

How it works

Spacelift
Alert fires
A tracked run fails.
Spacelift
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
State FAILED opens it, FINISHED 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 Spacelift. It fills in these filter values:
Part Payload JSON key Key value contains What it does
Trigger "state" failed Opens an incident.
Resolve "state" finished Resolves the open incident.
Match "run"."commit"."hash" Ties the resolve message to the incident it opened.
Title from "account" Becomes the incident title.
Description from "run"."commit"."message" Becomes the incident description.
  1. Choose the Priority for these incidents and click Save.

The template matches the resolve message on the commit hash. A fix is usually a new commit, so the green run would not resolve the incident. Change Map incident with (trigger and resolve) to "stack"."id", and Incident title from to "stack"."name" (the template uses the account name, which is the same for every stack).

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 Spacelift

  1. As a Spacelift admin, open Integrations, go to the Webhooks section and click View, then Create webhook.
  2. Set Name to CallgooseSQIBS and choose the Space that may use it.
  3. In Endpoint URL, enter your SQIBS endpoint:
https://<your-endpoint>/sqibs-api/v1/process?from=spacelift&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. Turn on Enable webhook and Retry on failure, then click Create.
  2. Send run events to it. Spacelift recommends a notification policy that routes stack events to the webhook by its ID. Stack webhooks still work too: on the Stacks page, open a stack's Settings > Integrations > Webhooks and select the 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. Trigger a run that fails, for example with an invalid change on a test stack.
  2. In SQIBS, a new incident opens. Spacelift's payload looks like this (shortened):
{
  "account": "example",
  "state": "FAILED",
  "stateVersion": 5,
  "timestamp": 1764152021,
  "run": {
    "id": "01JD4W0Q6KX7",
    "branch": "main",
    "commit": {
      "hash": "0ee3a3b7266d",
      "message": "Add cache cluster"
    },
    "type": "TRACKED",
    "url": "https://example.app.spacelift.io/stack/prod-network/run/01JD4W0Q6KX7"
  },
  "stack": {
    "id": "prod-network",
    "name": "prod-network"
  }
}
  1. Fix the change and push. When the stack's next run is FINISHED, 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 Spacelift 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 Spacelift run fails because a provider lock is stuck, SQIBS can run a workflow that clears the stale lock and retries the run.

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: