/zendesk | Type: Application | PCID required: Yes
Tools
| Tool | Description |
|---|---|
zendesk_list_tickets | List Zendesk tickets with optional pagination and sorting. Does NOT support date filtering. For tickets in a time range (e.g., last 7 days, February 2026), use zendesk_search_tickets instead with query like “type:ticket created>YYYY-MM-DD”. For large date ranges exceeding 1,000 results, use zendesk_iterate_tickets_bulk. |
zendesk_create_ticket | Create a new Zendesk ticket. Returns the created ticket object with all fields. |
zendesk_get_ticket | Get details of a specific Zendesk ticket. Returns search-style response with results array. |
zendesk_update_ticket | Update an existing Zendesk ticket. Returns the updated ticket object. |
zendesk_get_user_info | Get information about a Zendesk user |
zendesk_add_ticket_tags | Add tags to a Zendesk ticket for organization and filtering |
zendesk_set_ticket_tags | Set ticket tags (replaces all existing tags) |
zendesk_remove_ticket_tags | Remove specific tags from a Zendesk ticket |
zendesk_list_ticket_comments | List all comments on a Zendesk ticket. Returns array of comment objects. |
zendesk_search_tickets | Search Zendesk tickets using query syntax. Use for time-based queries (e.g., type:ticket created>2026-02-01 created<2026-02-28). Returns total count and pagination info. Use page parameter to fetch subsequent pages when count exceeds 100. Limited to ~1,000 results. For larger result sets, use zendesk_iterate_tickets_bulk instead. |
zendesk_iterate_tickets_bulk | Iterate through Zendesk tickets using cursor-based pagination with no result limit. Uses the export search endpoint (search/export.json). Designed for iterating through large or complete result sets. Results are sorted by created_at only. On the first call (no cursor), returns total count. Pass the returned after_cursor to fetch subsequent pages. For quick sortable searches under 1,000 results, use zendesk_search_tickets instead. |
zendesk_get_ticket_comments_batch | Get comments for multiple Zendesk tickets in a single call. Accepts up to 100 ticket IDs per call. Returns up to 100 comments per ticket (first page only). Tickets with more than 100 comments are truncated. Failed tickets are recorded in metadata but do not abort the batch. |
zendesk_delete_ticket | Delete a Zendesk ticket |
zendesk_list_macros | List all available Zendesk macros for ticket automation |
zendesk_list_trigger_capabilities | List available trigger types that can be created for Zendesk webhooks |
zendesk_create_trigger | Create a Zendesk webhook and trigger with custom conditions |
zendesk_update_trigger | Update an existing Zendesk trigger (can update title, category, and conditions) |
zendesk_delete_trigger | Delete a Zendesk webhook and trigger |
zendesk_list_tickets
List Zendesk tickets with optional pagination and sorting. Does NOT support date filtering. For tickets in a time range (e.g., last 7 days, February 2026), use zendesk_search_tickets instead with query like “type:ticket created>YYYY-MM-DD”. For large date ranges exceeding 1,000 results, use zendesk_iterate_tickets_bulk. Parameters:| Parameter | Type | Required | Default | Description |
|---|---|---|---|---|
page | number | No | — | Page number for pagination (starts from 1) |
per_page | number | No | — | Number of tickets per page (1-100, default: 100) |
sort_by | string | No | — | Field to sort by |
sort_order | string | No | — | Sort order (ascending or descending) |
zendesk_create_ticket
Create a new Zendesk ticket. Returns the created ticket object with all fields. Parameters:| Parameter | Type | Required | Default | Description |
|---|---|---|---|---|
subject | string | Yes | — | Subject of the ticket |
comment | string | Yes | — | Initial comment/description of the ticket |
priority | string | No | — | Priority of the ticket |
type | string | No | — | Type of the ticket |
tags | string[] | No | — | Tags to associate with the ticket |
zendesk_get_ticket
Get details of a specific Zendesk ticket. Returns search-style response with results array. Parameters:| Parameter | Type | Required | Default | Description |
|---|---|---|---|---|
ticketId | string | Yes | — | Ticket ID to retrieve |
zendesk_update_ticket
Update an existing Zendesk ticket. Returns the updated ticket object. Parameters:| Parameter | Type | Required | Default | Description |
|---|---|---|---|---|
ticketId | string | Yes | — | Ticket ID to update |
status | string | No | — | New status of the ticket (new, open, pending, solved, closed) |
priority | string | No | — | New priority of the ticket (urgent, high, normal, low) |
comment | string | No | — | New comment to add to the ticket |
tags | string[] | No | — | New tags to associate with the ticket |
zendesk_get_user_info
Get information about a Zendesk user Parameters:| Parameter | Type | Required | Default | Description |
|---|---|---|---|---|
userId | string | Yes | — | ID of the user to retrieve information for |
zendesk_add_ticket_tags
Add tags to a Zendesk ticket for organization and filtering Parameters:| Parameter | Type | Required | Default | Description |
|---|---|---|---|---|
ticketId | string | Yes | — | ID of the ticket to add tags to |
tags | string[] | Yes | — | Array of tags to add to the ticket |
zendesk_set_ticket_tags
Set ticket tags (replaces all existing tags) Parameters:| Parameter | Type | Required | Default | Description |
|---|---|---|---|---|
ticketId | string | Yes | — | ID of the ticket to set tags for |
tags | string[] | Yes | — | Array of tags to set (replaces all existing tags) |
zendesk_remove_ticket_tags
Remove specific tags from a Zendesk ticket Parameters:| Parameter | Type | Required | Default | Description |
|---|---|---|---|---|
ticketId | string | Yes | — | ID of the ticket to remove tags from |
tags | string[] | Yes | — | Array of tags to remove from the ticket |
zendesk_list_ticket_comments
List all comments on a Zendesk ticket. Returns array of comment objects. Parameters:| Parameter | Type | Required | Default | Description |
|---|---|---|---|---|
ticketId | string | Yes | — | ID of the ticket to list comments for |
zendesk_search_tickets
Search Zendesk tickets using query syntax. Use for time-based queries (e.g., type:ticket created>2026-02-01 created<2026-02-28). Returns total count and pagination info. Use page parameter to fetch subsequent pages when count exceeds 100. Limited to ~1,000 results. For larger result sets, use zendesk_iterate_tickets_bulk instead. Parameters:| Parameter | Type | Required | Default | Description |
|---|---|---|---|---|
query | string | Yes | — | Search query (e.g., “type:ticket status:open” or “type:ticket created>2026-02-01” for time ranges) |
sortBy | string | No | — | Field to sort by (created_at, updated_at, priority, etc.) |
sortOrder | string | No | — | Sort order |
page | number | No | — | Page number for pagination (1-based). Use to fetch pages 2, 3, etc. when next_page is returned. |
per_page | number | No | — | Results per page (1-100, default 100) |
zendesk_iterate_tickets_bulk
Iterate through Zendesk tickets using cursor-based pagination with no result limit. Uses the export search endpoint (search/export.json). Designed for iterating through large or complete result sets. Results are sorted by created_at only. On the first call (no cursor), returns total count. Pass the returned after_cursor to fetch subsequent pages. For quick sortable searches under 1,000 results, use zendesk_search_tickets instead. Parameters:| Parameter | Type | Required | Default | Description |
|---|---|---|---|---|
query | string | Yes | — | Search query using Zendesk search syntax (e.g., “status:open created>2025-01-01”). type:ticket is handled automatically — do not include it. |
cursor | string | No | — | Opaque cursor from a previous response’s after_cursor field. Omit on the first call. |
pageSize | number | No | — | Results per page (1-100, default 100) |
zendesk_get_ticket_comments_batch
Get comments for multiple Zendesk tickets in a single call. Accepts up to 100 ticket IDs per call. Returns up to 100 comments per ticket (first page only). Tickets with more than 100 comments are truncated. Failed tickets are recorded in metadata but do not abort the batch. Parameters:| Parameter | Type | Required | Default | Description |
|---|---|---|---|---|
ticketIds | string[] | Yes | — | Array of ticket IDs to fetch comments for (max 100) |
zendesk_delete_ticket
Delete a Zendesk ticket Parameters:| Parameter | Type | Required | Default | Description |
|---|---|---|---|---|
ticketId | string | Yes | — | ID of the ticket to delete |
zendesk_list_macros
List all available Zendesk macros for ticket automationzendesk_list_trigger_capabilities
List available trigger types that can be created for Zendesk webhookszendesk_create_trigger
Create a Zendesk webhook and trigger with custom conditions Parameters:| Parameter | Type | Required | Default | Description |
|---|---|---|---|---|
triggerType | string | Yes | — | Type of trigger to create |
webhookUrl | string | Yes | — | The webhook URL where Zendesk should send events |
title | string | Yes | — | Name for the trigger |
categoryId | string | No | — | Optional category ID |
conditions | string | No | — | Trigger conditions (optional - defaults to all ticket updates when empty or not provided). Format: {“all”: [{“field”: “status”, “value”: “new”}]} |
zendesk_update_trigger
Update an existing Zendesk trigger (can update title, category, and conditions) Parameters:| Parameter | Type | Required | Default | Description |
|---|---|---|---|---|
triggerId | string | Yes | — | The ID of the trigger to update |
webhookId | string | Yes | — | The webhook ID associated with this trigger |
title | string | No | — | New title for the trigger |
categoryId | string | No | — | New category ID |
conditions | string | No | — | New trigger conditions (optional). Format: {“all”: [{“field”: “status”, “value”: “new”}]} |
zendesk_delete_trigger
Delete a Zendesk webhook and trigger Parameters:| Parameter | Type | Required | Default | Description |
|---|---|---|---|---|
triggerId | string | Yes | — | The ID of the trigger to delete |
webhookId | string | No | — | Optional webhook ID (if not provided, will be retrieved from metadata) |

