Overview
Send Buddy (buddy.works) pipeline results to Callgoose SQIBS. A webhook integration posts each execution to your SQIBS API endpoint. SQIBS opens an incident when a pipeline fails and resolves it when the pipeline runs green again.
How it works
FAILED opens it, SUCCESSFUL 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 Buddy Works. It fills in these filter values:
| Part | Payload JSON key | Key value contains | What it does |
|---|---|---|---|
| Trigger | "execution"."status" |
FAILED |
Opens an incident. |
| Resolve | "execution"."status" |
SUCCESSFUL |
Resolves the open incident. |
| Match | "execution"."url" |
Ties the resolve message to the incident it opened. | |
| Title from | "project"."name" |
Becomes the incident title. |
- Choose the Priority for these incidents and click Save.
The template matches the resolve message on "execution"."url", which is different for every run, so a later successful run never resolves the failed one. Change Map incident with (trigger and resolve) to "execution"."pipeline"."id" so the next green run of the same pipeline resolves it.
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 a webhook integration in Buddy
- In Buddy, open Integrations in the sidebar and click New integration, then choose Webhook.
- Give it a name, for example
Callgoose SQIBS, and enter your SQIBS endpoint as the URL:
https://<your-endpoint>/sqibs-api/v1/process?from=buddy&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.
- Leave the secret empty, choose the trigger events (pipeline finished, failed and successful), and set Enable in projects to the projects you want (or all).
- Click Save 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.
- Run a pipeline that fails, for example with an action that exits with an error.
- In SQIBS, a new incident opens, titled with the project name. Buddy's payload looks like this (shortened):
{
"project": {
"name": "shop-api",
"display_name": "shop-api"
},
"execution": {
"id": 812,
"status": "FAILED",
"branch": {
"name": "main"
},
"url": "https://api.buddy.works/workspaces/example/projects/shop-api/pipelines/42/executions/812",
"pipeline": {
"id": 42,
"name": "Deploy to production"
}
}
}
- Fix the pipeline and run it again. When the run is
SUCCESSFUL, 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 Buddy 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 deploy pipeline fails, SQIBS can run a workflow that checks the target servers and rolls back to the last good release.
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.