Composio powers 1000+ toolkits, tool search, context management, authentication, and a sandboxed workbench to help you build AI agents that turn intent into action.
| 1 | --- |
| 2 | type: "reference" |
| 3 | title: "Zendesk" |
| 4 | description: "Public support knowledge for Zendesk." |
| 5 | category: "auth-config" |
| 6 | visibility: "public" |
| 7 | timestamp: "2026-06-24T00:00:00Z" |
| 8 | tags: |
| 9 | - "zendesk" |
| 10 | --- |
| 11 | # Zendesk |
| 12 | |
| 13 | |
| 14 | ## Zendesk OAuth setup does not require manually entering an access token |
| 15 | |
| 16 | For Zendesk OAuth, the access token is injected automatically after the OAuth flow completes; customers do not need to manually enter it. Redirect URI can be optional depending on the auth-config setup, but if Zendesk requires one, configure the Composio auth redirect URL in the Zendesk OAuth app. |
| 17 | |
| 18 | ## Zendesk connections require the account subdomain |
| 19 | |
| 20 | Zendesk requires the account subdomain during connection initiation. Pass the Zendesk site prefix, not the full URL, as `subdomain`. Composio uses that field to construct Zendesk URLs. |
| 21 | |
| 22 | ## Initiate Zendesk OAuth connections by passing `subdomain` in config values |
| 23 | |
| 24 | When initiating a Zendesk OAuth connected account, pass `subdomain` in the connection config values. For the current SDK shape, use `config={"auth_scheme":"OAUTH2","val":{"subdomain":"<site-name>"}}`; older examples used `connected_account_params={"subdomain":"<site-name>"}`. |
| 25 | |
| 26 | ## Zendesk API-key/basic auth initiation passes `subdomain` and base64 encoded credentials |
| 27 | |
| 28 | For Zendesk API-key/basic auth connection initiation, pass the Zendesk `subdomain` and `basic_encoded` credential value in the connection data. The `basic_encoded` value should be the base64 encoding of the Zendesk email/token credential form requested by the auth config. |
| 29 | |
| 30 | ## Include `toolkit_versions` when listing Zendesk tools through the API |
| 31 | |
| 32 | When listing Zendesk tools through the API, include the toolkit version query parameter. For example, use `toolkit_versions=latest&toolkit_slug=zendesk&limit=1000`. Without the toolkit version query, the API response may not show the expected tool set. |
| 33 | |
| 34 | ## `ZENDESK_SEARCH_ZENDESK` was added for Zendesk search use cases |
| 35 | |
| 36 | Use `ZENDESK_SEARCH_ZENDESK` for Zendesk search use cases. |
| 37 | |
| 38 | ## `ZENDESK_UPDATE_ZENDESK_TICKET` is available for updating Zendesk tickets |
| 39 | |
| 40 | Use `ZENDESK_UPDATE_ZENDESK_TICKET` for Zendesk ticket updates. For endpoint-level context, the corresponding Zendesk API is the Update Ticket endpoint in Zendesk's ticketing API. |
| 41 | |
| 42 | ## Zendesk get-ticket-by-id returns ticket details in one tool call |
| 43 | |
| 44 | The Zendesk get-ticket-by-id action is available and returns the ticket details in a single tool call. Use it when the customer has a Zendesk ticket ID and needs the ticket's metadata/details rather than searching first. |
| 45 | |
| 46 | ## Zendesk supports triggers in Composio |
| 47 | |
| 48 | Zendesk has trigger support in Composio. Verify the current trigger catalog before naming an exact count. |