Overview

Send Aha! roadmap activity to Callgoose SQIBS. An activity webhook posts every change in a workspace to your SQIBS API endpoint, and an integration webhook posts a feature or release when someone sends it. Your SQIBS filter decides which changes become incidents, for example a release being deleted.

You need
An Aha! workspace where you can manage integrations, and a SQIBS API token
Setup time
About 10 minutes
Result
Selected Aha! changes open SQIBS incidents

How it works

Aha!
Alert fires
Someone changes a record in the workspace.
Aha!
Sends a webhook
Through an activity 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 change description.

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 Aha! template yet, so enter them by hand):
Part Payload JSON key Key value contains What it does
Trigger "audit"."audit_action" destroy Opens an incident for deletions. Change the value, or add filters, for other changes.
Title from "audit"."description" Becomes the incident title.
Description from "audit"."auditable_type" Becomes the incident description.
  1. Choose the Priority for these incidents and click Save.

An activity webhook sends every change, so a filter with no value would open an incident for each edit. Keep a value in Key value contains. Aha! 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 a webhook in Aha!

  1. In Aha!, open Settings (gear icon) > Workspace > Integrations and click +.
  2. Choose Activity webhook to send every change, or Integration webhook to send a feature or release only when someone picks Send to Webhook.
  3. In Hook URL, enter your SQIBS endpoint:
https://<your-endpoint>/sqibs-api/v1/process?from=aha&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. Turn the integration on (Enable) 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. Delete a test record in the workspace (or make the change your filter matches).
  2. In SQIBS, a new incident opens, titled with the change description. Aha! sends payloads like this (shortened):
{
  "event": "audit",
  "audit": {
    "id": "7486747259601627325",
    "audit_action": "destroy",
    "created_at": "2026-11-22T06:43:03.326Z",
    "auditable_type": "release",
    "auditable_id": "7486747259577489247",
    "description": "deleted release Q1 launch",
    "user": {
      "name": "A. Product"
    }
  }
}

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 Aha! integration.

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 release is moved or deleted in Aha!, SQIBS can run a workflow that posts the change to your release channel and updates the deployment calendar.

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: