Triage Zoho Desk tickets and prepare a concise support handoff from the tickets your account can access.
Example workflows
Copy a prompt into your connected AI client after connecting this integration. Choose resources you can access and review the supported command before running it.
Prepare a support triage queue
Read one page of 20 Zoho Desk tickets from my connected organization. Build a triage table with ticket ID, subject, status, priority and assignee where returned. Highlight tickets that need an owner or next action, without guessing missing fields. Keep ticket references and ask before reading another page or changing a ticket.
Explore this command: zoho-desk.tickets.list
Summarize one customer issue
Ask me for a Zoho Desk ticket ID. Read that ticket and draft an internal handoff covering the customer request, current status, assigned owner and unresolved next step using only returned facts. Preserve its ID and source link if present. Do not imply that comments or conversation history were retrieved, and do not send a reply.
Explore this command: zoho-desk.tickets.get
What you can do (2)
What you can do
Available commands: 2 (2 read, 0 write). Enable only the commands your application needs.
| Command | Effect |
|---|---|
Find Zoho Desk tickets for a support handoff — zoho-desk.tickets.list |
Read |
Read a selected Zoho Desk ticket — zoho-desk.tickets.get |
Read |
Connect and use
This connection uses your provider account.
Connect this integration, enter your provider credentials, choose commands and save. Complete provider authorization if prompted.
Get your provider credentials
Follow these steps for Zoho Desk, then enter the issued values in the connection form below.
- Zoho OAuth access token with Desk.tickets.READ and your organization ID. This adapter uses the US data center. Customer-managed token renewal and Desk API credits apply. Open the official API documentation, create credentials limited to this workflow, then enter the values shown below. Select only the commands you need. Revoking credentials at the provider disconnects access.
Where to enter credentials
In the integration page, sign in, choose your workspace and open Connect. If a Credentials choice is shown, select Use my credentials. Fill the following connection fields and save. Provider credentials belong in this form, never in an MCP configuration or tool input.
| Connection field | Requirement |
|---|---|
| Zoho Desk API key | Required |
| Zoho Desk organization ID | Required |
Open API keys and create a Tooluse.net key for the enabled commands.
Set TOOLUSE_API_KEY in your client and use the shared MCP configuration.
Configure Claude Code, Codex or Cursor once
Permissions and results
If you have more than one workspace, check the selected workspace in the connection or API-key dialog before saving. Roles, enabled commands, expiry and revocation use Tooluse.net's existing permissions. Disabling a connection or revoking a key immediately prevents new calls.
Send one Claude tool_use block per request. Keep the same Idempotency-Key when retrying the same request; use a new key for a new call. The response includes the shared Tooluse.net receipt and Claude tool_result. Check both HTTP status and the returned tool result before treating a call as successful.
Your connection's daily allowance and key permissions also apply. Adding a connection does not make a provider request.
Calls return the shared execution receipt and a Claude tool_result. Provider output varies by operation; consult the provider documentation for its response fields. Unconfirmed calls should be checked before retrying.
Call from your client
Use the shared MCP configuration. Refresh your client's tool list after saving the connection or changing key permissions, then call the returned tool name with the example input below.
Configure Claude Code, Codex or Cursor once
Discover your enabled tools
List permitted tools in Claude format. Read every page using page and size (maximum 100) until all results have been received. Use the returned name, not a catalog capability identifier, in the tool_use block.
curl 'https://api.tooluse.net/v1/tools' \
-H "Authorization: Bearer $TOOLUSE_API_KEY"
Find this command in the tool list permitted by your key. Replace svc_FROM_YOUR_TOOL_LIST with its returned name. Use a new Idempotency-Key for each new call and retain it when retrying that same call.
HTTP call
curl 'https://api.tooluse.net/v1/tool-calls' \
-H "Authorization: Bearer $TOOLUSE_API_KEY" \
-H 'Content-Type: application/json' \
-H 'Idempotency-Key: replace-with-a-new-call-id' \
--data '{
"type": "tool_use",
"id": "toolu_example",
"name": "svc_FROM_YOUR_TOOL_LIST",
"input": {
"query": {
"from": 0,
"limit": 20
}
}
}'
Send one Claude tool_use block per request. Keep the same Idempotency-Key when retrying the same request; use a new key for a new call. The response includes the shared Tooluse.net receipt and Claude tool_result. Check both HTTP status and the returned tool result before treating a call as successful.
Commands
Find Zoho Desk tickets for a support handoff — zoho-desk.tickets.list
Find Zoho Desk tickets for a support handoff. One explicit provider request; no retries or automatic follow-up pages. Customer permissions and quotas apply.
This is a read operation. Provider rate limits and data access rules still apply.
Parameters
Requiredness is local to the containing object. A required child is required only when its parent object or array item is provided. Alternative schemas are identified in the Constraints column; the linked full JSON Schema is authoritative.
| Parameter | Type | Required in parent | Description | Constraints |
|---|---|---|---|---|
query |
object | Required | additionalProperties: false |
|
query.from |
integer | Required | minimum: 0; maximum: 100000 |
|
query.limit |
integer | Required | minimum: 1; maximum: 100 |
|
query.status |
string | Optional | minLength: 1; maxLength: 100 |
Full JSON Schema
Example input
{
"query": {
"from": 0,
"limit": 20
}
}
At most 1 provider requests per invocation; timeout: 30 seconds.
Read a selected Zoho Desk ticket — zoho-desk.tickets.get
Read a selected Zoho Desk ticket. One explicit provider request; no retries or automatic follow-up pages. Customer permissions and quotas apply.
This is a read operation. Provider rate limits and data access rules still apply.
Parameters
Requiredness is local to the containing object. A required child is required only when its parent object or array item is provided. Alternative schemas are identified in the Constraints column; the linked full JSON Schema is authoritative.
| Parameter | Type | Required in parent | Description | Constraints |
|---|---|---|---|---|
path |
object | Required | additionalProperties: false |
|
path.ticket_id |
string | Required | minLength: 1; maxLength: 100 |
Full JSON Schema
Example input
{
"path": {
"ticket_id": "1001"
}
}
At most 1 provider requests per invocation; timeout: 30 seconds.
Errors
Check the key's expiry, revocation, workspace and allowed operations.
Reuse the same idempotency key only for the same request.
The connection or provider limit has been reached. Check the receipt before retrying.
Test the connection
Open the integration's commands below to inspect parameters and examples. Start with a read command for an account or resource you can access. Refresh your client's tool list, use the returned tool name, and check the execution result and usage. Provider charges and permissions still apply. Never test a write against production data without reviewing it.