Overview
Open Callgoose SQIBS incidents from Salesforce. A record-triggered flow calls your SQIBS API endpoint with an HTTP callout when a high-priority case is created or updated. SQIBS opens an incident for the case and resolves it when the case is closed. The same pattern works for any object, such as a custom alert object.
How it works
High opens it, status Closed 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.
- Add a filter with these values (there is no built-in Salesforce template yet, so enter them by hand):
| Part | Payload JSON key | Key value contains | What it does |
|---|---|---|---|
| Trigger | "priority" |
High |
Opens an incident. |
| Resolve | "status" |
Closed |
Resolves the open incident. |
| Match | "caseId" |
Ties the resolve message to the incident it opened. | |
| Title from | "subject" |
Becomes the incident title. | |
| Description from | "account" |
Becomes the incident description. |
- Choose the Priority for these incidents and click Save.
SQIBS checks the resolve filter first, so a closed case resolves its incident even though its priority is still High.
Not sure of a key? Send one test message first (step below), then build the filter from the real payload.
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 SQIBS endpoint as a named credential
- In Setup, go to Named Credentials. On the External Credentials tab, create one with Authentication Protocol set to No Authentication, and add a principal to it.
- On the Named Credentials tab, create
Callgoose_SQIBSwith URL set tohttps://<your-endpoint>and the external credential from step 1. Tick Allow Formulas in HTTP Header. - Give the users (or the automated process user) that run the flow access to the external credential principal through a permission set.
Replace <your-endpoint> and <your-token> with the values from your SQIBS account. See how to get the endpoint URL and API tokens.
Step 3: Create the flow
- In Setup > Flows, create a Record-Triggered Flow on Case, triggered when a record is created or updated, with the entry condition
Priority Equals HighorStatus Equals Closed. Choose Actions and Related Records. - Add an Action and choose Create HTTP Callout. Pick the
Callgoose_SQIBSnamed credential, method POST, and URL path/sqibs-api/v1/process. Add the query parametersfrom=salesforceandtoken= your SQIBS token. - Use this sample body so Salesforce learns the shape, then map each field from the record:
{
"caseId": "{!$Record.Id}",
"caseNumber": "{!$Record.CaseNumber}",
"subject": "{!$Record.Subject}",
"priority": "{!$Record.Priority}",
"status": "{!$Record.Status}",
"account": "{!$Record.Account.Name}"
}
- Save and activate the flow. HTTP callouts from record-triggered flows must run in an asynchronous path; Flow Builder adds it for you.
Step 4: 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.
- Create a test case with Priority set to High.
- In SQIBS, a new incident opens, titled with the case subject:
{
"caseId": "5005g00000AbCdEFGH",
"caseNumber": "00001042",
"subject": "Checkout page returns errors",
"priority": "High",
"status": "New",
"account": "Acme Ltd"
}
- Close the case. The flow sends
"status": "Closed"for the samecaseId, and 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 flow's HTTP callout.
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 high-priority case reports that the customer portal is down, SQIBS can run a workflow that checks the portal health endpoint and restarts the web tier if it fails.
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.