productivity
Zendesk CLI for Headless Automation
Use the Zendesk CLI for headless automation with headless JSON commands, schema discovery, credentials, and permission controls.
7 functions 6 read 1 write Manual OAuth token auth
Zendesk 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 Zendesk CLI uses the same integration registry as the TUI, Lua runtime, and MCP gateway, but returns predictable command output for automation.
Command Shape
# Zendesk CLI for Headless Automation
kosmokrator integrations:configure zendesk --set access_token="$ZENDESK_ACCESS_TOKEN" --enable --read allow --write ask --json
kosmo integrations:call zendesk.zendesk_create_ticket '{"subject":"example_subject","description":"example_description","priority":"example_priority","type":"example_type","status":"example_status","assignee_id":"example_assignee_id","tags":"example_tags"}' --jsonDiscovery Before Execution
Agents and scripts can inspect Zendesk docs and schemas before choosing a function.
kosmo integrations:docs zendesk --json
kosmo integrations:docs zendesk.zendesk_create_ticket --json
kosmo integrations:schema zendesk.zendesk_create_ticket --json
kosmo integrations:search "Zendesk" --json
kosmo integrations:list --jsonUseful Zendesk CLI Functions
| Function | Type | Parameters | Description |
|---|---|---|---|
zendesk.zendesk_create_ticket | Write | subject, description, priority, type, status, assignee_id, tags | Create a new ticket in Zendesk. Requires a subject and description. Optionally set priority, type, status, and assignee. Returns the created ticket with its ID. |
zendesk.zendesk_get_current_user | Read | none | Retrieve the currently authenticated Zendesk user. Returns the user's ID, name, email, role, and avatar. Useful for identifying which account or token is in use. |
zendesk.zendesk_get_ticket | Read | ticket_id | Retrieve a Zendesk ticket by its ID. Returns the full ticket including subject, description, status, priority, and metadata. |
zendesk.zendesk_get_user | Read | user_id | Retrieve a Zendesk user by its ID. Returns the user's ID, name, email, role, and profile details. |
zendesk.zendesk_list_organizations | Read | per_page, page | List Zendesk organizations with pagination. Returns organization IDs, names, and created dates. Use per_page and page for pagination. |
zendesk.zendesk_list_tickets | Read | per_page, page, sort_by, sort_order, status | List Zendesk tickets with pagination and filtering. Returns ticket IDs, subjects, status, priority, and created dates. Use per_page, page, and status for pagination and filtering. |
zendesk.zendesk_list_users | Read | per_page, page, role, sort_by, sort_order | List Zendesk users with pagination and filtering. Returns user IDs, names, emails, and roles. Use per_page, page, and role for pagination and filtering. |
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.