Overview

Track Flagsmith changes in Callgoose SQIBS. A Flagsmith audit log webhook posts every change (a flag created, toggled or edited) to your SQIBS API endpoint. SQIBS opens a low-priority incident for each change, so on-call engineers can see what changed in production when something breaks.

You need
A Flagsmith organisation with admin access, and a SQIBS API token
Setup time
About 5 minutes
Result
Flagsmith changes appear as SQIBS incidents

How it works

Flagsmith
Alert fires
Someone changes a flag or remote config.
Flagsmith
Sends a webhook
The audit log webhook posts the change.
SQIBS
API filter matches
The filter decides whether to open or resolve, and the priority.
SQIBS
Incident opens
The incident takes its title from the change log.

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 Flagsmith template yet, so enter them by hand):
Part Payload JSON key Key value contains What it does
Trigger "data"."log" Opens an incident for every audit log entry.
Title from "data"."log" For example "Flag state updated: new_checkout".
  1. Choose the Priority for these incidents and click Save.

Give this filter a low Priority: it records changes, it should not page anyone at night. To track one environment only, add its name in Key value contains on "data"."environment"."name".

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 the audit webhook in Flagsmith

  1. In Flagsmith, open Organisation Settings > Webhooks and click Create Audit Webhook.
  2. Enter your SQIBS endpoint:
https://<your-endpoint>/sqibs-api/v1/process?from=flagsmith&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. Optionally set a secret so you can check the signature header, then click Create 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. Toggle a test flag.
  2. In SQIBS, a new incident opens. Flagsmith's payload looks like this (shortened):
{
  "data": {
    "created_date": "2026-11-22T10:15:00.000000Z",
    "log": "Flag state updated: new_checkout",
    "author": {
      "email": "dev@example.com"
    },
    "environment": {
      "id": 4,
      "name": "Production"
    },
    "project": {
      "id": 6,
      "name": "Shop"
    },
    "related_object_type": "FEATURE_STATE"
  },
  "event_type": "AUDIT_LOG_CREATED"
}

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 Flagsmith 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 production flag change is followed by an error spike, SQIBS can run a workflow that turns the flag back off through the Flagsmith API.

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: