Overview

Send HaloITSM ticket events to Callgoose SQIBS. A HaloITSM webhook posts ticket events to your SQIBS API endpoint. SQIBS opens an incident when a new ticket is logged and resolves it when the ticket is closed, so on-call sees urgent tickets straight away.

You need
HaloITSM with admin access to Configuration, and a SQIBS API token
Setup time
About 15 minutes
Result
New tickets open SQIBS incidents; closing them resolves the incidents

How it works

HaloITSM
Alert fires
A new ticket is logged.
HaloITSM
Sends a webhook
Through a HaloITSM webhook, as JSON.
SQIBS
API filter matches
The filter decides whether to open or resolve, and the priority.
SQIBS
Incident opens
new ticket logged opens it, 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

  1. In SQIBS, open Services, choose the service that should receive these incidents, and click Add Or Update API Integration.
  2. In Select Integration Template, choose HaloITSM. It fills in these filter values:
Part Payload JSON key Key value contains What it does
Trigger "event" new ticket logged Opens an incident.
Resolve "event" closed Resolves the open incident.
Match "object_id" Ties the resolve message to the incident it opened.
Title from "event" Becomes the incident title.
Description from "message" Becomes the incident description.
  1. Choose the Priority for these incidents and click Save.

To page on-call only for urgent tickets, limit the webhook's events to the ticket types or priorities you want in step 2.

The template is a starting point, not a lock-in: every value stays visible and you can change it.

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 HaloITSM

  1. In HaloITSM, go to Configuration > Integrations > Webhooks and click New.
  2. Give it a name, set Webhook type to Standard webhook, Method to POST and Content type to application/json.
  3. In Payload URL, enter your SQIBS endpoint (authentication: none, the token is in the URL):
https://<your-endpoint>/sqibs-api/v1/process?from=haloitsm&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. Make sure Enabled is on. Under Events, click Add and add the New ticket logged and Ticket closed events.
  2. Save the 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. Log a test ticket in HaloITSM.
  2. In SQIBS, a new incident opens. HaloITSM's payload looks like this (shortened):
{
  "id": "65119eb0-d766-48d9-973b-4dbfe4448c87",
  "event": "new ticket logged",
  "message": "New request logged for Example Ltd. ID:0002309.",
  "object_id": 2309,
  "timestamp": "2026-11-22T07:28:55.258Z"
}
  1. Close the ticket. HaloITSM sends "event": "closed" for the same object_id, 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 HaloITSM 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 ticket reports that a user cannot reach a file share, SQIBS can run a workflow that checks the share and restarts the file service if it is down.

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: