Overview

Turn urgent Freshservice incident tickets into Callgoose SQIBS incidents. Two Workflow Automator workflows trigger a webhook: one when an urgent or high-priority incident is raised, one when it is resolved or closed. SQIBS opens the incident on the first and resolves it on the second.

You need
A Freshservice account with admin access, and a SQIBS API token
Setup time
About 15 minutes
Result
Urgent tickets open SQIBS incidents; resolving the ticket resolves them

How it works

Freshservice
Alert fires
An urgent or high-priority incident ticket is raised.
Freshservice
Sends a webhook
A workflow triggers a webhook with JSON.
SQIBS
API filter matches
The filter decides whether to open or resolve, and the priority.
SQIBS
Incident opens
ticket_created opens it, status Resolved or 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. Add a filter with these values (there is no built-in Freshservice template yet, so enter them by hand):
Part Payload JSON key Key value contains What it does
Trigger "event" ticket_created Opens an incident (the workflow only sends urgent and high tickets).
Resolve "status" Resolved Resolves the incident.
Resolve "status" Closed A second resolve filter for closed tickets.
Match "ticket_id" Ties the update to the ticket's incident.
Title from "subject" Becomes the incident title.
  1. Choose the Priority for these incidents and click Save.

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 two workflows in Freshservice

  1. In Freshservice, go to Admin > Workflow Automator and click New Automator > Ticket.
  2. Set the event to ticket is raised, add a condition for priority Urgent or High, and add the action Trigger Webhook: method POST, content type JSON, URL:
https://<your-endpoint>/sqibs-api/v1/process?from=freshservice&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.

Use this body:

{
  "event": "ticket_created",
  "ticket_id": "{{ticket.id}}",
  "subject": "{{ticket.subject}}",
  "priority": "{{ticket.priority}}",
  "status": "{{ticket.status}}",
  "url": "{{ticket.url}}"
}
  1. Create a second workflow for when the status is changed to Resolved or Closed, with the same webhook and this body:
{
  "event": "ticket_updated",
  "ticket_id": "{{ticket.id}}",
  "subject": "{{ticket.subject}}",
  "priority": "{{ticket.priority}}",
  "status": "{{ticket.status}}",
  "url": "{{ticket.url}}"
}
  1. Activate both workflows.

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. Raise an incident ticket with Urgent priority.
  2. In SQIBS, a new incident opens, titled with the ticket subject.
  3. Resolve the ticket. The second workflow sends the new status 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 Freshservice workflow.

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 an urgent ticket reports a shared drive full, SQIBS can run a workflow that clears the temporary files and rechecks the space.

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: