Zendesk
Service domainCUSTOMER SUPPORT
Arcade Optimized
6tools
6require secrets
Zendesk Toolkit
The Zendesk toolkit connects Arcade to your Zendesk account, enabling agents and apps to manage support tickets, retrieve conversation history, search the Help Center knowledge base, and inspect account context.
Capabilities
- Ticket management: List tickets with offset-based pagination, add public or internal comments, and mark tickets as solved (with an optional closing comment). All ticket responses include a direct
html_urllink. - Conversation history: Retrieve all comments on a ticket in chronological order, including the original description, author IDs, visibility (public/internal), timestamps, and file attachments.
- Knowledge base search: Search published Help Center articles by query text and/or label names, with support for date filters and offset-based pagination. Multiple filters can be combined in a single call.
- Account introspection: Fetch the authenticated user's profile, role, organization details, and Zendesk account context via a dedicated identity tool.
OAuth
This toolkit uses OAuth 2.0. The auth provider is Zendesk. See the Arcade Zendesk auth provider docs for setup instructions.
Secrets
ZENDESK_SUBDOMAIN— Your Zendesk subdomain identifies which Zendesk account to target. It is the{subdomain}portion of your Zendesk URL:https://{subdomain}.zendesk.com. You can find it by logging into Zendesk and inspecting the browser address bar, or under Admin Center → Account → Branding. This value is not a credential but is required for the toolkit to construct the correct API base URL.
Configure secrets in the Arcade secrets dashboard or via the Arcade secrets guide.
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