Use the Zendesk CLI from KosmoKrator to call Zendesk tools headlessly, return JSON, inspect schemas, and automate workflows from coding agents, scripts, and CI.
Zendesk can be configured headlessly with `kosmokrator integrations:configure zendesk`.
# Install KosmoKrator first if it is not available on PATH.curl -fsSL https://raw.githubusercontent.com/OpenCompanyApp/kosmokrator/main/install.sh | bash# Configure and verify this integration.kosmokrator integrations:configure zendesk --set access_token="$ZENDESK_ACCESS_TOKEN" --enable --read allow --write ask --jsonkosmokrator integrations:doctor zendesk --jsonkosmokrator integrations:status --json
Credentials
Authentication type: Manual OAuth tokenoauth2_manual_token. Configure credentials once, then use the same stored profile from
scripts, coding CLIs, Lua code mode, and the MCP gateway.
Key
Env var
Type
Required
Label
access_token
ZENDESK_ACCESS_TOKEN
Secret secret
yes
Access Token
base_url
ZENDESK_BASE_URL
URL url
no
API Base URL
Call Zendesk Headlessly
Use the generic call form when another coding CLI or script needs a stable universal interface.
Every function below can be called headlessly. The generic form is stable across all integrations;
the provider shortcut is shorter but specific to Zendesk.
zendesk.zendesk_create_ticket
Write write
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.
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.
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.
List Zendesk users with pagination and filtering.
Returns user IDs, names, emails, and roles.
Use per_page, page, and role for pagination and filtering.
Use these parameter tables when building CLI payloads without calling integrations:schema first.
zendesk.zendesk_create_ticket
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.
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.
Number of organizations per page (default 100, max 100).
page
integer
no
Page number for pagination (1-indexed).
zendesk.zendesk_list_tickets
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.
Field to sort by (e.g. "created_at", "updated_at", "priority").
sort_order
string
no
Sort order: "asc" or "desc".
status
string
no
Filter by ticket status: "new", "open", "pending", "hold", "solved", "closed".
zendesk.zendesk_list_users
List Zendesk users with pagination and filtering.
Returns user IDs, names, emails, and roles.
Use per_page, page, and role for pagination and filtering.
Headless calls still follow the integration read/write permission policy. Configure read/write defaults
with integrations:configure. Add --force only for trusted automation that should bypass that policy.