support
Zoho Desk CLI for Headless Automation
Use the Zoho Desk CLI for headless automation with headless JSON commands, schema discovery, credentials, and permission controls.
8 functions 6 read 2 write Manual OAuth token auth
Zoho Desk CLI for Headless Automation
Use KosmoKrator as a non-interactive integration runtime for local automations and wrappers.
Use headless automation when another tool needs a stable local command surface. The Zoho Desk CLI uses the same integration registry as the TUI, Lua runtime, and MCP gateway, but returns predictable command output for automation.
Command Shape
# Zoho Desk CLI for Headless Automation
kosmokrator integrations:configure zoho-desk --set access_token="$ZOHO_DESK_ACCESS_TOKEN" --set org_id="$ZOHO_DESK_ORG_ID" --enable --read allow --write ask --json
kosmo integrations:call zoho-desk.zohodesk_list_tickets '{"departmentId":"example_departmentId","status":"example_status","priority":"example_priority","from":1,"limit":1,"sortBy":"example_sortBy","sortOrder":"example_sortOrder","search":"example_search"}' --json Discovery Before Execution
Agents and scripts can inspect Zoho Desk docs and schemas before choosing a function.
kosmo integrations:docs zoho-desk --json
kosmo integrations:docs zoho-desk.zohodesk_list_tickets --json
kosmo integrations:schema zoho-desk.zohodesk_list_tickets --json
kosmo integrations:search "Zoho Desk" --json
kosmo integrations:list --json Useful Zoho Desk CLI Functions
| Function | Type | Parameters | Description |
|---|---|---|---|
zoho-desk.zohodesk_list_tickets | Read | departmentId, status, priority, from, limit, sortBy, sortOrder, search | List support tickets from Zoho Desk. Supports filtering by department, status, priority, and other criteria. Returns ticket IDs, subjects, statuses, and basic details. |
zoho-desk.zohodesk_get_ticket | Read | ticketId | Get full details of a specific support ticket by its ID, including subject, description, status, priority, assignee, contact info, and custom fields. |
zoho-desk.zohodesk_create_ticket | Write | subject, departmentId, description, contactId, email, priority, status, channel, assigneeId, teamId | Create a new support ticket in Zoho Desk. Requires at least a subject and department ID. Optionally include a contact ID, description, priority, and other ticket fields. |
zoho-desk.zohodesk_update_ticket | Write | ticketId, subject, description, status, priority, assigneeId, teamId, departmentId, channel | Update an existing support ticket in Zoho Desk. Provide the ticket ID and the fields to update (e.g., status, priority, assignee, subject, description). |
zoho-desk.zohodesk_list_contacts | Read | from, limit, search, sortBy, sortOrder | List contacts from Zoho Desk. Supports filtering by name, email, and search terms. Returns contact IDs, names, emails, and phone numbers. |
zoho-desk.zohodesk_list_articles | Read | departmentId, categoryId, from, limit, search, sortBy, sortOrder | List knowledge base articles from Zoho Desk. Supports filtering by department, category, and search terms. Returns article IDs, titles, summaries, and categories. |
zoho-desk.zohodesk_list_departments | Read | from, limit | List all departments configured in Zoho Desk. Returns department IDs, names, descriptions, and visibility settings. Department IDs are needed when creating tickets. |
zoho-desk.zohodesk_get_current_user | Read | none | Get the profile of the currently authenticated Zoho Desk user. Returns user ID, name, email, role, and other profile information. |
Automation Notes
- Use
--jsonfor machine-readable output. - Keep credentials out of argv by using environment variables or stored KosmoKrator configuration.
- Configure read/write policy before unattended runs; use
--forceonly for trusted automation. - Use the MCP gateway instead when the agent needs dynamic tool discovery inside a conversation.