Zendesk

Manage support tickets, users, and organizations.

Install

amodal connect zendesk

Authentication

Basic auth with email/token format.

• ZENDESK_EMAIL — Zendesk agent email (used with /token suffix)
• ZENDESK_API_TOKEN — API token from Admin > Channels > API
• ZENDESK_BASE_URL — Full subdomain URL (e.g., https://mycompany.zendesk.com)

Auth format: {ZENDESK_EMAIL}/token:{ZENDESK_API_TOKEN}

Endpoints

Tickets

• GET /api/v2/tickets — List tickets
• GET /api/v2/tickets/:id — Get ticket details
• POST /api/v2/tickets — Create a ticket (confirmation)
• PUT /api/v2/tickets/:id — Update a ticket (confirmation)
• GET /api/v2/tickets/:id/comments — List ticket comments
• DELETE /api/v2/tickets/:id — Delete a ticket (confirmation)
• PUT /api/v2/tickets/:id/mark_as_spam — Mark as spam (confirmation)
• PUT /api/v2/tickets/update_many — Bulk update tickets (confirmation)
• POST /api/v2/tickets/create_many — Bulk create tickets (confirmation)

Users

• GET /api/v2/users — List users
• GET /api/v2/users/:id — Get user details

Organizations

• GET /api/v2/organizations — List organizations
• GET /api/v2/organizations/:id — Get organization details

Search

• GET /api/v2/search — Search tickets, users, organizations

Entities

• api, ticket, comment, user, organization, search, mark_as_spam

Rules

• Rate limit: 700 requests/minute per account (varies by plan); search API has a separate lower limit
• Ticket status "closed" is terminal — cannot reopen, must create a follow-up; status flow: new > open > pending/hold > solved > closed
• description is read-only (it is the body of the first comment); comments are append-only and cannot be edited or deleted
• Zendesk uses PUT (not PATCH) for updates; include a comment object in the update body to add a reply with public: true or false for internal notes