Overview

Turn Zoho Desk tickets into Callgoose SQIBS incidents. A Zoho Desk webhook posts ticket events to your SQIBS API endpoint as a JSON list. SQIBS opens an incident when a ticket is added and resolves it when the ticket is closed.

You need
A Zoho Desk account with admin access, and a SQIBS API token
Setup time
About 15 minutes
Result
New tickets open SQIBS incidents; closed tickets resolve them

How it works

Zoho Desk
Alert fires
A ticket is added.
Zoho Desk
Sends a webhook
Through a webhook, as a JSON list of events.
SQIBS
API filter matches
The filter decides whether to open or resolve, and the priority.
SQIBS
Incident opens
Ticket_Add opens it, a Closed ticket 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 Zoho Desk template yet, so enter them by hand):
Part Payload JSON key Key value contains What it does
Trigger [0]."eventType" Ticket_Add Opens an incident for each new ticket.
Resolve [0]."payload"."statusType" Closed Resolves the incident when the ticket is closed.
Match [0]."payload"."id" Ties the closed ticket to the incident it opened.
Title from [0]."payload"."subject" Becomes the incident title.
  1. Choose the Priority for these incidents and click Save.

Zoho Desk sends a list, so every key starts with [0].. Other ticket updates match neither filter and are ignored. To page only on urgent tickets, add a filter value on [0]."payload"."priority".

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 the webhook in Zoho Desk

  1. In Zoho Desk, click Settings, then under Developer Space choose Webhooks, and click New Webhook.
  2. Give it a name and set the URL to your SQIBS endpoint:
https://<your-endpoint>/sqibs-api/v1/process?from=zohodesk&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. Under events, choose Ticket Add and Ticket Update, for the departments you want.
  2. Click Test Run, then 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. Create a test ticket.
  2. In SQIBS, a new incident opens. The payload looks like this (shortened):
[
  {
    "eventType": "Ticket_Add",
    "orgId": "123456",
    "payload": {
      "id": "4000000123045",
      "ticketNumber": "101",
      "subject": "Cannot log in to the portal",
      "statusType": "Open",
      "status": "Open",
      "priority": "High",
      "channel": "Email"
    },
    "eventTime": "1763800000000"
  }
]
  1. Close the ticket. Zoho Desk sends a Ticket_Update with "statusType": "Closed", 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 Zoho Desk 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 tickets about a slow portal arrive, SQIBS can run a workflow that checks the portal's health endpoint and restarts the app server if it fails.

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: