# Zendesk AI integration on Definable

> Zendesk provides customer support software with ticketing, live chat, and knowledge base features, enabling efficient helpdesk operations and customer engagement

## What this connects

Zendesk provides customer support software with ticketing, live chat, and knowledge base features, enabling efficient helpdesk operations and customer engagement

Vendor: https://www.zendesk.com/

## Tools available

**20** tools available. First 12:

- `ZENDESK_COUNT_ZENDESK_ORGANIZATIONS` — Count Zendesk Organizations — Count the number of organizations in Zendesk. Returns a single numeric total only — no names, IDs, or custom fields. Use ZENDESK_GET_ALL_ZENDESK_ORGANIZATIONS for per-organization detail.
- `ZENDESK_CREATE_ZENDESK_ORGANIZATION` — Create Zendesk Organization — Create an organization in Zendesk. Both `name` and `external_id` must be unique across the account; verify no duplicates exist before calling. Returns `data.id` — persist it for subsequent update or delete operations.
- `ZENDESK_CREATE_ZENDESK_TICKET` — Create Zendesk Ticket — Create a ticket in Zendesk with full support for all ticket fields. Returns `ticket_id` and `ticket_url`; use ZENDESK_GET_ZENDESK_TICKET_BY_ID for the full ticket object.
- `ZENDESK_CREATE_ZENDESK_USER` — Create Zendesk User — Tool to create a new user in Zendesk. Search for existing users first to avoid duplicate accounts with the same email. Use when you need to onboard a user with specific details.
- `ZENDESK_DELETE_ZENDESK_ORGANIZATION` — Delete Zendesk Organization — Delete an organization in Zendesk. This operation is irreversible; confirm organization_id and get explicit user confirmation before calling.
- `ZENDESK_DELETE_ZENDESK_TICKET` — Delete Zendesk Ticket — Permanently deletes a ticket in Zendesk, including its entire conversation history. This action is irreversible; always confirm the correct ticket_id before executing.
- `ZENDESK_DELETE_ZENDESK_USER` — Delete Zendesk User — Tool to permanently delete a user from Zendesk. Use when you need to remove a user account. This action cannot be undone and requires appropriate admin permissions.
- `ZENDESK_DESTROY_MANY_ORGANIZATIONS` — Bulk Delete Zendesk Organizations — Tool to bulk delete Zendesk organizations. Irreversible — confirm ids/external_ids before calling. Use when cleaning up test data or removing obsolete organizations in one call. Returns a job_status payload (initial status typically 'queued'); deletions complete asynchronously and may require follow-up polling to confirm completion.
- `ZENDESK_GET_ABOUT_ME` — Get Zendesk About Me — Get information about the currently authenticated user in Zendesk. Returns only the caller's own account; to look up other users, use ZENDESK_SEARCH_ZENDESK_USERS. Response nests the user object under data.owner_info.user. Useful for verifying the acting user's identity and permissions before performing bulk operations.
- `ZENDESK_GET_ALL_ZENDESK_ORGANIZATIONS` — Get Zendesk Organizations — Get all organizations in Zendesk. Returns results nested under an 'organizations' array; an empty list is valid. Accepts no server-side filters — all filtering by name, domain_names (an array field), or organization_fields must be done client-side. Large accounts require pagination; missing pages will undercount results. Multiple organizations may share similar names or domains — always disambiguate using external_id or domain_names and confirm organization_id before acting. Avoid repeated full-list fetches on large accounts; cache or batch client-side instead.
- `ZENDESK_GET_USER` — Get User — Tool to fetch a single Zendesk user by numeric user_id. Use when you have a user ID from ticket payloads (requester_id, submitter_id, assignee_id, author_id) and need to enrich with full user details (name, email, role, organization_id, etc.).
- `ZENDESK_GET_ZENDESK_ORGANIZATION` — Get Zendesk Organization — Get metadata for a specific Zendesk organization by ID. Response fields are available under data.organization_info. Does not return member/user lists.

## Auth

Auth schemes: `OAUTH2`. Managed by Definable: `OAUTH2` — no client credentials required from the user.

## How agents use Zendesk

Inside a Definable workflow, Zendesk is one of the tools the **Distributor specialist** can call. Example coordination patterns:

- **Researcher → Zendesk** — the Researcher (GPT-5.5) pulls context from Zendesk (records, threads, documents), synthesises findings, and briefs the rest of the team.
- **Writer → Distributor → Zendesk** — the Writer (Claude Opus 4.7) drafts copy in brand voice, the Verifier passes it, then the Distributor writes the result into Zendesk (create record, post message, draft email).
- **Designer / Engineer → Distributor → Zendesk** — the Designer ships an asset or the Engineer ships a code change, the Distributor delivers it via Zendesk (attach file, open PR comment, post status).

The Verifier checks every Zendesk call. On rate limit, schema drift, or auth refresh it self-heals and retries — the workflow completes without manual intervention.

## Categories

- crm — https://definable.ai/apps/category/crm/
- customer support — https://definable.ai/apps/category/customer-support/

## Related

- HTML page: https://definable.ai/apps/zendesk/
- Same category (crm): https://definable.ai/apps/category/crm/
- All integrations: https://definable.ai/apps/
- Workflow (multi-agent loop): https://definable.ai/workflow/
- Apps llms.txt index: https://definable.ai/llms-apps.txt