Overview

Send AWS CodePipeline failures to Callgoose SQIBS. An EventBridge rule matches pipeline execution state changes and sends them to an API destination that points at your SQIBS API endpoint. SQIBS opens an incident when a pipeline fails and resolves it when the next run succeeds.

You need
An AWS account with permission to manage EventBridge, and a SQIBS API token
Setup time
About 15 minutes
Result
Failed pipelines open SQIBS incidents; successful runs resolve them

How it works

CodePipeline
Alert fires
A pipeline execution fails.
CodePipeline
Sends a webhook
EventBridge sends the state change to an API destination.
SQIBS
API filter matches
The filter decides whether to open or resolve, and the priority.
SQIBS
Incident opens
FAILED opens it, SUCCEEDED 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 CodePipeline template yet, so enter them by hand):
Part Payload JSON key Key value contains What it does
Trigger "detail"."state" FAILED Opens an incident.
Resolve "detail"."state" SUCCEEDED Resolves the open incident.
Match "detail"."pipeline" The pipeline name ties the next good run to the failure (the execution id is new for every run).
Title from "detail"."pipeline" Becomes the incident title.
Description from "detail-type" Becomes the incident description.
  1. Choose the Priority for these incidents and click Save.

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 API destination

Create an EventBridge API destination for SQIBS as described in step 2 of Amazon EventBridge, with this endpoint:

https://<your-endpoint>/sqibs-api/v1/process?from=codepipeline&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.

Step 3: Create the rule

  1. In EventBridge, go to Rules > Create rule, and keep Rule with an event pattern.
  2. Use this event pattern (add "pipeline": ["<name>"] under detail to limit it to some pipelines):
{
  "source": [
    "aws.codepipeline"
  ],
  "detail-type": [
    "CodePipeline Pipeline Execution State Change"
  ],
  "detail": {
    "state": [
      "FAILED",
      "SUCCEEDED"
    ]
  }
}
  1. Choose the SQIBS API destination as the target, let EventBridge create a role, and create the rule.

Step 4: 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. Start a pipeline run that fails, for example by pushing a commit that breaks the build.
  2. In SQIBS, a new incident opens, titled with the pipeline name. The event looks like this (shortened):
{
  "version": "0",
  "detail-type": "CodePipeline Pipeline Execution State Change",
  "source": "aws.codepipeline",
  "region": "ap-southeast-1",
  "time": "2026-11-22T10:15:00Z",
  "detail": {
    "pipeline": "shop-api-deploy",
    "execution-id": "01234567-0123-0123-0123-012345678901",
    "state": "FAILED",
    "version": 3
  }
}
  1. Fix the change and run the pipeline again. When it succeeds, 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 API destination.

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 deployment pipeline fails at the deploy stage, SQIBS can run a workflow that checks the target environment and rolls it back to the last good release.

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: