Zoho Desk
Connect NetLock RMM to Zoho Desk: alerts become tickets of the mapped account in a department, the all-clear adds a private comment and closes the ticket, accounts can be imported as tenants.
Zoho Desk
Requirements
- A Zoho Desk organization. Its edition sets the daily API credits; the Free edition has 5 000.
- A self client in the Zoho API console with its client id and client secret.
- A refresh token of that client for the scopes
Desk.tickets.ALL,Desk.accounts.READ,Desk.contacts.READ,Desk.contacts.CREATE,Desk.basic.READ. Generate an authorization code in the console and exchange it once, as described in the self client guide. The refresh token does not expire. - The user of the token needs a profile that may create contacts and comment on tickets.
- The organization id, shown in Zoho Desk under
Setup → Developer Space → API.
Setup
- In
Settings → Integrations, open the Zoho Desk tile and chooseConnect. - Enter the
Instance addressof your data center:https://desk.zoho.com,.eu,.in,.com.au,.jp,.sa,.uk,.sg,.aeorhttps://desk.zohocloud.ca. It also determines the accounts server. Other addresses are refused. - Enter the
Organization ID,Client ID,Client secretandRefresh token. - Under options, choose the
Departmentthat receives the tickets and theStatus when closing. - Map each tenant to an account, or import accounts as tenants. Tenants without a mapping are not included. Severities can be mapped to the priorities of Zoho Desk; without a mapping the default of the department applies.
- Activate the connection.
What goes to the vendor
For every alert that passes the filter of the connection: a title, the severity, tenant, location and device name, the source, first and last time seen, the alert text, and a link to the web console if the public console URL is set. Check that this matches your data processing agreements before you activate the connection.
For each account that receives tickets, NetLock also creates one contact named NetLock RMM without an e-mail address, unless it already exists.
What happens to a ticket
- An alert becomes a ticket of the mapped account in the chosen department. The subject ends in
[NetLock-Alert-<id>], which NetLock uses to find the ticket again. - The contact of the ticket is the
NetLock RMMcontact of the account. It has no address, so department notifications cannot be sent to it. No e-mail goes to the customer, but what a help center shows depends on your settings. - When the alert ends, the ticket gets a private comment and goes to the chosen status if nobody is assigned.
The behaviour is set in the Settings tab, see A.14.4. NetLock never closes a ticket whose status somebody changed in the meantime, and it never deletes anything at the vendor.
Known limits
- Every read and write uses the daily API credits. Lists are read during setup and when a ticket is created, never on a schedule. When the credits run out, Zoho answers with a time to wait, and the jobs wait for it.
- New tickets take minutes to reach the search of Zoho Desk, so a repeated job reads the ticket list of the department instead. If that department has too many new tickets to look through, the job ends as failed and no second ticket is created. Check the department, then use
Send again. - Zoho allows ten access tokens per ten minutes.
- If Zoho Desk refuses to close the ticket, for example because of a required field, the note is added and the ticket stays open. The history shows
close_refused. - If Zoho Desk refuses the comment, the ticket is left unchanged, because nobody could otherwise see why it ended. The history shows
note_refused. - A repeated job only looks in the chosen department. If a rule moves new tickets elsewhere right away, a repeat can create a second ticket.
Related
Zendesk
Connect NetLock RMM to Zendesk Support: alerts become tickets of the mapped organization with an internal first comment, the all-clear adds an internal note and solves the ticket, organizations can be imported as tenants.
ServiceDesk Plus
Connect NetLock RMM to ManageEngine ServiceDesk Plus, Cloud or On-Premises: alerts become requests of the mapped site, the all-clear adds a hidden note and closes the request, sites can be imported as tenants.