Purpose
This guide explains how to configure the Zoho Desk Response integration in Logsign USO, so that Incidents and Alarms can automatically, or an analyst can manually, create a Zoho Desk ticket and look up departments and contacts directly from a Logsign Incident. This is a Response (action) integration, configured under Settings > Integrations > Responses > +Device.
Prerequisites
- A Zoho Desk account and a Zoho API OAuth2 application (Client ID and Client Secret), plus a refresh token for a Zoho Desk-scoped account.
- Use least privilege. Scope the OAuth application's permissions to Zoho Desk ticket management only, not your broader Zoho account.
- EU data center only. This integration connects to Zoho Desk's EU data center (desk.zoho.eu) and has no setting to point it at another region. If your Zoho Desk account runs on the US, India, Australia, or another non-EU data center, this integration cannot reach it; contact Logsign support to check whether a region-aware version is available before relying on this integration.
Step 1: Create a Zoho API Client and Obtain a Refresh Token
- Log in to the Zoho API Console (api-console.zoho.com) and create a new Server-based Application (or Self Client, depending on your integration pattern).
- Note the Client ID and Client Secret.
- Complete Zoho's OAuth authorization flow scoped to Zoho Desk (Desk.tickets.ALL or a narrower ticket-scoped permission) to obtain a refresh token. The exact OAuth flow steps are standard Zoho API Console procedure and were not independently re-verified against a live Zoho Desk account during this research.
Step 2: Configure the Integration in Logsign USO
In Logsign USO, go to Settings > Integrations > Responses, search for Zoho Desk, click Configure then +Device, and fill in:
| Field | Required | Description |
|---|---|---|
| Device Name | Yes | Free-text label identifying this Zoho Desk device in Logsign. |
| Refresh Token | Yes | The refresh token from Step 1. Stored encrypted at rest. |
| Client Id | Yes | The OAuth Client ID from Step 1. Stored encrypted at rest. |
| Client Secret | Yes | The OAuth Client Secret from Step 1. Stored encrypted at rest. |
| Insecure Skip Verify | Yes | Disables TLS certificate validation on Logsign's outbound calls when enabled. Defaults to on; leave off unless you have a specific reason to keep it enabled. |
Note: the underlying integration definition lists a "grant_type" and "code" as required inputs, but neither corresponds to an actual field in this configuration form; this appears to be a leftover from the OAuth token-exchange step rather than something you need to fill in here. Fill in the four fields shown above and click Create to save the device.
Available Methods
- department_list (Analysis) — lists departments. No args.
- contact_list (Analysis) — lists contacts. No args.
- create_ticket (Containment) — creates a Zoho Desk ticket. Args (all required): subject, contactId, email, assigneeId, departmentId, description, priority (High, Medium, or Low), status (Open, On Hold, Escalated, or Closed).
Troubleshooting
| Symptom | Likely cause | What to check |
|---|---|---|
| 401 Unauthorized / invalid_token | Wrong Refresh Token, Client Id, or Client Secret, or the refresh token was revoked. | Re-verify all three OAuth credentials, and re-generate the refresh token in the Zoho API Console if it has been revoked. |
| 403 Forbidden | The OAuth application's scope does not include the permission needed for the action (for example ticket creation). | Confirm the scope granted during the OAuth authorization flow in Step 1 includes the required Desk.tickets permission. |
| create_ticket fails with an invalid departmentId/contactId/assigneeId | Wrong ID values. | Use department_list and contact_list to confirm valid IDs before calling create_ticket. |
Notes and Limits
- Zoho's OAuth refresh tokens can be revoked from the Zoho API Console at any time (for example if the app's permissions are reviewed and changed); if authentication starts failing after previously working, check there first.