Overview

Track AI prompt changes in Callgoose SQIBS. A PromptLayer webhook posts prompt template events to your SQIBS API endpoint. SQIBS opens a low-priority incident for each prompt release, so a change to production prompts is visible to the on-call team and easy to correlate with any incident that follows.

You need
A PromptLayer workspace with admin access, and a SQIBS API token
Setup time
About 10 minutes
Result
Prompt releases appear as SQIBS incidents

How it works

PromptLayer
Alert fires
A prompt template is published or its release label moves.
PromptLayer
Sends a webhook
Through a workspace webhook, as JSON.
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 prompt name.

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 PromptLayer template yet, so enter them by hand):
Part Payload JSON key Key value contains What it does
Trigger "event" prompt_template Opens an incident.
Title from "data"."prompt_name" Becomes the incident title.
Description from "data"."commit_message" Becomes the incident description.
  1. Choose the Priority for these incidents and click Save.

Set the Priority to low: these are change records, not outages. PromptLayer does not send a message when the problem clears, so close these incidents in SQIBS (or with an automation workflow) when the fix is in.

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 webhook in PromptLayer

  1. In PromptLayer, open Settings > Webhooks and add a webhook.
  2. In Webhook URL, enter your SQIBS endpoint:
https://<your-endpoint>/sqibs-api/v1/process?from=promptlayer&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. Choose the prompt template events you want to track (for example new versions and release label changes) and save.

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. Publish a new version of a test prompt, or move its release label.
  2. In SQIBS, a new incident opens, titled with the prompt name. 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": "prompt_template.label_moved",
  "timestamp": "2026-11-22T12:05:00Z",
  "data": {
    "prompt_name": "incident-summary-bot",
    "version": 42,
    "label": "production",
    "commit_message": "Add safety guardrails"
  }
}

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 PromptLayer 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 prompt release coincides with a spike in failed model calls, SQIBS can run a workflow that moves the production label back to the previous version.

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: