Overview

Turn urgent Zendesk tickets into Callgoose SQIBS incidents. A Zendesk webhook, called by two triggers, posts a ticket when it is created and when it is solved. SQIBS opens an incident for the new ticket and resolves it when the ticket is solved. An automation workflow can also fix the issue and solve the ticket through the Zendesk API.

You need
A Zendesk account with admin access, and a SQIBS API token
Setup time
About 20 minutes
Result
Urgent tickets open SQIBS incidents; solved tickets close them

How it works

Zendesk
Alert fires
An urgent ticket is created.
Zendesk
Sends a webhook
A trigger calls the webhook, which posts JSON.
SQIBS
API filter matches
The filter decides whether to open or resolve, and the priority.
SQIBS
Incident opens
ticket_created opens it, ticket_solved 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 Zendesk template yet, so enter them by hand):
Part Payload JSON key Key value contains What it does
Trigger "event" ticket_created Opens an incident.
Resolve "event" ticket_solved Resolves the open incident.
Match "ticket_id" Ties the solved ticket to the incident it opened.
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: Create the webhook in Zendesk

  1. In Admin Center, go to Apps and integrations > Webhooks > Webhooks and click Create webhook.
  2. Choose Trigger or automation and click Next.
  3. Name it Callgoose SQIBS, set Endpoint URL to your SQIBS endpoint, Request method to POST and Request format to JSON:
https://<your-endpoint>/sqibs-api/v1/process?from=zendesk&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. Click Test webhook, then Create webhook.

Step 3: Add two triggers

  1. In Admin Center, go to Objects and rules > Business rules > Triggers and click Create trigger.
  2. First trigger, Urgent ticket to SQIBS: conditions Ticket is Created and Priority is Urgent (or your own). Action Notify by > Active webhook > Callgoose SQIBS, with this body:
{
  "event": "ticket_created",
  "ticket_id": "{{ticket.id}}",
  "subject": "{{ticket.title}}",
  "priority": "{{ticket.priority}}",
  "status": "{{ticket.status}}",
  "requester": "{{ticket.requester.email}}",
  "link": "{{ticket.link}}"
}
  1. Second trigger, Solved ticket to SQIBS: conditions Status changed to Solved and the same priority. Same webhook, with this body:
{
  "event": "ticket_solved",
  "ticket_id": "{{ticket.id}}",
  "subject": "{{ticket.title}}",
  "priority": "{{ticket.priority}}",
  "status": "{{ticket.status}}",
  "requester": "{{ticket.requester.email}}",
  "link": "{{ticket.link}}"
}
  1. Save both triggers.

Step 4: Let automation solve the ticket (optional)

When an automation workflow fixes the issue, it can solve the ticket too, which also resolves the incident through the second trigger. In the workflow, add an HTTP request to the Zendesk Tickets API (store the API token in the workflow's credentials, never in plain text):

PUT https://<your-subdomain>.zendesk.com/api/v2/tickets/<ticket_id>.json
Content-Type: application/json
Authorization: Basic <base64 of agent-email/token:api-token>

{"ticket": {"status": "solved", "comment": {"body": "Resolved by Callgoose SQIBS automation.", "public": true}}}

Step 5: 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. Create a ticket with priority Urgent.
  2. In SQIBS, a new incident opens, titled with the ticket subject.
  3. Solve the ticket. 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 Zendesk 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 customers open urgent tickets saying they cannot log in, SQIBS can run a workflow that checks the sign-in service, restarts it if needed, and solves the ticket with a note.

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: