Zoho Desk icon

Zoho Desk

Create and update tickets in Zoho Desk
Join our community

Actions2

Overview

This node creates a new ticket in Zoho Desk, a customer support platform. It is useful for automating the creation of support tickets based on incoming data or events, such as customer inquiries or issue reports. For example, it can be used to automatically log a ticket when a customer sends an email or fills out a support form, assigning it to the appropriate department and team for resolution.

Use Case Examples

  1. Automatically create a support ticket when a customer submits a form on a website.
  2. Log a ticket in Zoho Desk when an error is detected in a system monitoring tool.

Properties

Name Meaning
Department Name or ID The department to which the ticket belongs. This is required and can be selected from a list or specified by ID.
Team Name or ID The team assigned to resolve the ticket. Teams load based on the selected department and can be chosen from a list or specified by ID.
Subject The subject or title of the ticket. This is a required string input.
Contact Details of the contact who raised the ticket. If an email exists, the contact ID is used; otherwise, a new contact is created. Either last name or email must be provided.
Priority Priority level of the ticket, with options Low, Medium, or High.
Classification Classification of the ticket, such as Question, Problem, Request, or Others.
Due Date The due date for resolving the ticket, specified as a date-time string.
Description Detailed description of the ticket.
Additional Fields Optional additional fields for the ticket, including secondary contacts, custom fields (as JSON), account ID, assignee ID, category, channel, email, language, phone, product ID, resolution, status, and sub-category.

Output

JSON

  • json - The JSON response from Zoho Desk API containing the created ticket details.

Dependencies

  • Requires Zoho Desk OAuth2 API credentials for authentication.

Troubleshooting

  • Rate limit errors may occur if more than 10 requests per second are sent. The node will throw an error indicating the rate limit has been exceeded; reduce request frequency or batch size to resolve.
  • Validation errors for fields such as email format, due date format, and required fields (e.g., subject, departmentId) may occur. Ensure inputs meet the expected formats and required fields are provided.
  • Custom fields must be valid JSON objects; invalid JSON or incorrect structure will cause errors.
  • Ticket ID must be numeric when updating tickets; invalid formats will cause errors.

Links

Discussion