Overview

Send Clever Cloud application events to Callgoose SQIBS. A notification webhook posts the events you choose, such as failed deployments, to your SQIBS API endpoint. SQIBS opens an incident when a deployment fails and resolves it when the next deployment succeeds.

You need
A Clever Cloud organization with admin access, and a SQIBS API token
Setup time
About 10 minutes
Result
Failed deployments open SQIBS incidents; successful ones resolve them

How it works

Clever Cloud
Alert fires
A deployment fails.
Clever Cloud
Sends a webhook
A notification webhook posts the event, as raw JSON.
SQIBS
API filter matches
The filter decides whether to open or resolve, and the priority.
SQIBS
Incident opens
DEPLOYMENT_FAIL opens it, DEPLOYMENT_SUCCESS 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 Clever Cloud template yet, so enter them by hand):
Part Payload JSON key Key value contains What it does
Trigger "event" DEPLOYMENT_FAIL Opens an incident.
Resolve "event" DEPLOYMENT_SUCCESS Resolves the open incident.
Match "data"."appId" The application ties the next good deployment to the failure.
Title from "event" Becomes the incident title.
  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: Add a notification webhook in Clever Cloud

  1. In the Clever Cloud console, open the organization (or Personal space) and go to Notifications > Webhooks, then Add.
  2. Give it a name and enter your SQIBS endpoint as the URL:
https://<your-endpoint>/sqibs-api/v1/process?from=clevercloud&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. Set the format to Raw (JSON).
  2. Choose the events DEPLOYMENT_FAIL and DEPLOYMENT_SUCCESS (and the applications), and click Create.

With the Clever Tools CLI you can do the same: clever notify-webhook add --format raw --event DEPLOYMENT_FAIL,DEPLOYMENT_SUCCESS CallgooseSQIBS <url>.

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. Push a change that fails to build.
  2. In SQIBS, a new incident opens. The payload below shows the shape to expect. Field names can differ between versions, so send one test message first and copy the exact keys from the API log with the JSON key creator.
{
  "event": "DEPLOYMENT_FAIL",
  "date": "2026-11-22T10:15:00Z",
  "data": {
    "appId": "app_1c2d3e4f-5a6b-7c8d-9e0f-a1b2c3d4e5f6",
    "appName": "shop-api",
    "cause": "build failed"
  }
}
  1. Fix the build and deploy again. When the deployment 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 Clever Cloud 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 deployment fails, SQIBS can run a workflow that restarts the last good instance with clever restart --commit <sha>.

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: