Zendesk
Service domainCUSTOMER SUPPORT
Arcade Optimized
6tools
6require secrets
The Zendesk toolkit connects Arcade to your Zendesk account, enabling agents and applications to manage support tickets, retrieve conversations, and search Help Center content programmatically.
Capabilities
- Ticket management — list tickets with offset-based pagination, mark tickets as solved (with an optional final comment), and retrieve direct
html_urllinks to any ticket in the Zendesk UI. - Conversation access — fetch all comments on a ticket (including the original description, author metadata, timestamps, visibility flags, and file attachments).
- Ticket commenting — append new public or internal comments to existing tickets.
- Knowledge base search — search published Help Center articles by query, labels, or date filters; supports pagination and combining multiple filters in a single call.
- Identity & account context — retrieve the authenticated user's profile, role, organization, and Zendesk account details.
OAuth
This toolkit uses OAuth 2.0 via the Zendesk provider. See the Arcade Zendesk auth provider docs for setup instructions.
Secrets
ZENDESK_SUBDOMAIN— Your Zendesk subdomain, which identifies your specific Zendesk instance. It is the prefix of your Zendesk URL: forhttps://yourcompany.zendesk.com, the subdomain isyourcompany. You can find this in your browser's address bar when logged in to Zendesk, or under Admin Center → Account → Branding. This value is not sensitive on its own but is required so the toolkit knows which Zendesk instance to route API calls to.
For instructions on storing secrets in Arcade, see the Arcade secrets guide. You can also manage secrets directly at https://api.arcade.dev/dashboard/auth/secrets.
Available tools(6)
6 of 6 tools
Operations
Behavior
| Tool name | Description | Secrets | |
|---|---|---|---|
Add a comment to an existing Zendesk ticket.
The returned ticket object includes an 'html_url' field with the direct link
to view the ticket in Zendesk. | 1 | ||
Get all comments for a specific Zendesk ticket, including the original description.
The first comment is always the ticket's original description/content.
Subsequent comments show the conversation history.
Each comment includes:
- author_id: ID of the comment author
- body: The comment text
- created_at: Timestamp when comment was created
- public: Whether the comment is public or internal
- attachments: List of file attachments (if any) with file_name, content_url, size, etc. | 1 | ||
List tickets from your Zendesk account with offset-based pagination.
By default, returns tickets sorted by ID with newest tickets first (desc).
Each ticket in the response includes an 'html_url' field with the direct link
to view the ticket in Zendesk.
PAGINATION:
- The response includes 'next_offset' when more results are available
- To fetch the next batch, simply pass the 'next_offset' value as the 'offset' parameter
- If 'next_offset' is not present, you've reached the end of available results | 1 | ||
Mark a Zendesk ticket as solved, optionally with a final comment.
The returned ticket object includes an 'html_url' field with the direct link
to view the ticket in Zendesk. | 1 | ||
Search for Help Center articles in your Zendesk knowledge base.
This tool searches specifically for published knowledge base articles that provide
solutions and guidance to users. At least one search parameter (query or label_names)
must be provided.
PAGINATION:
- The response includes 'next_offset' when more results are available
- To fetch the next batch, simply pass the 'next_offset' value as the 'offset' parameter
- If 'next_offset' is not present, you've reached the end of available results
- The tool automatically handles fetching from the correct page based on your offset
IMPORTANT: ALL FILTERS CAN BE COMBINED IN A SINGLE CALL
You can combine multiple filters (query, labels, dates) in one search request.
Do NOT make separate tool calls - combine all relevant filters together. | 1 | ||
Get comprehensive user profile and Zendesk account information.
This tool provides detailed information about the authenticated user including
their name, email, role, organization details, and Zendesk account context. | 1 |
Last updated on