Overview
Customer support platform for managing tickets and service requests. Through Langdock’s integration, you can access and manage Zendesk directly from your conversations.Authentication: OAuth
Category: Productivity & Collaboration
Availability: All workspace plans
Available Actions
Create help center article
zendesk.create_help_center_article
Creates a new article in the Zendesk Help Center knowledge base
Requires Confirmation: Yes
Parameters:
sectionId(TEXT, Required): The ID of the section where the article will be created. Format: Integer Example: 12345 LLM Guidance: This is required. The section must exist in the Help Center. You can find section IDs using the find_help_center_articles action or by browsing the Help Center structure.title(TEXT, Required): The title of the article. Format: String (1-255 characters) Example: “How to reset your password” or “Troubleshooting login issues” LLM Guidance: Generate a clear, descriptive title that accurately represents the article content. The title should be concise but informative enough for users to und…body(MULTI_LINE_TEXT, Required): The main content of the article in HTML format. Format: String (can include HTML formatting) Example: “To reset your password:
- Go to the login page
- Click ‘Forgot Password’
- Enter your email address
permissionGroupId(TEXT, Required): The ID of the permission group that can edit and publish this article. Format: Integer LLM Guidance: This determines who can manage the article. Different permission groups have different access levels: - Higher IDs typically represent more restrictive permissions - Lower IDs typically represent …locale(TEXT, Optional): The language/locale for the article. Format: String in locale format (e.g., ‘en-us’, ‘fr’, ‘de’, ‘es’) Default: ‘en-us’ LLM Guidance: Specify the language the article is written in. Common values: - ‘en-us’ for English (US) - ‘en-gb’ for English (UK) - ‘fr’ for French - ‘de’ for German - ‘es’ for…userSegmentId(TEXT, Optional): The ID of the user segment that can view this article (API field: user_segment_ids). Format: Integer or null Default: null (visible to everyone) LLM Guidance: Specify which users can see this article: - null or empty: Article visible to everyone - Specific ID: Only users in that segment can view …draft(SELECT, Optional): Whether the article should be created as a draft. Format: Boolean (true/false) Default: false (published) LLM Guidance: Set to true if: - The article needs review before publishing - Content is incomplete - You want to create the article but publish it later Set to false to publish immediately.promoted(SELECT, Optional): Whether the article should be promoted (featured). Format: Boolean (true/false) Default: false LLM Guidance: Set to true for: - Important articles that should be highly visible - Frequently accessed content - Featured tutorials or guides Promoted articles typically appear more prominently in sear…position(TEXT, Optional): The position of this article within its section. Format: Integer Default: 0 (added to end) LLM Guidance: Use this to control the order articles appear in their section: - 0: Article appears at the end - 1: Article appears first - Higher numbers: Article appears later in the list Consider the logi…commentsDisabled(SELECT, Optional): Whether to disable comments on this article. Format: Boolean (true/false) Default: false (comments enabled) LLM Guidance: Set to true if: - The article shouldn’t allow user feedback - Comments are not relevant for this content type - You want to prevent spam or inappropriate comments Set to false…labelNames(TEXT, Optional): Labels/tags to associate with the article for better organization and searchability. Format: Array of strings (comma-separated) Example: [“billing”, “account”, “troubleshooting”] LLM Guidance: Add relevant labels that help categorize and make the article discoverable: - Use lowercase labels - Inc…contentTagIds(TEXT, Optional): Content tag IDs to attach to the article. Format: Array of strings (comma-separated) Example: [“01GT23D51Y”, “01GT23FWWN”] LLM Guidance: If your organization uses content tags for advanced categorization, specify the relevant tag IDs here. Content tags are different from label names and are typic…authorId(TEXT, Optional): The ID of the user who should be credited as the article author. Format: Integer Default: Current authenticated user LLM Guidance: Specify the Zendesk user ID of the person who should be listed as the article author. This is useful when: - Creating articles on behalf of subject matter experts - M…notifySubscribers(SELECT, Optional): Whether to send email notifications to article subscribers. Format: Boolean (true/false) Default: true LLM Guidance: Set to false when: - Creating multiple articles at once to avoid spam - The article is not ready for public attention - You’re importing content and don’t want to trigger notificat…
Create ticket
zendesk.create_ticket
Creates a ticket in Zendesk
Requires Confirmation: Yes
Parameters:
subject(TEXT, Required): The subject line of the ticket that summarizes the issue or request. Format: String (1-255 characters) Example: “Website login error” or “Billing question for invoice #12345” LLM Guidance: Generate a concise, descriptive subject that clearly indicates the nature of the ticket. Avoid vague subject…description(TEXT, Required): he main body content of the ticket that provides details about the issue or request. Format: String (can include HTML formatting) Example: “I’m unable to log in to my account. I keep getting an ‘Invalid credentials’ error even though I’m sure my password is correct.” LLM Guidance: Generate a deta…isPublic(SELECT, Optional): Determines whether the comment is visible to the end-user/requester. Format: Boolean (true/false) Default: true LLM Guidance: Set to true for comments that should be visible to the customer. Set to false for internal notes visible only to agents. If the user mentions “internal note” or similar ph…priority(TEXT, Optional): he urgency level of the ticket. Format: String, must be one of: “low”, “normal”, “high”, “urgent” Default: “normal” LLM Guidance: Determine priority based on the urgency expressed by the user and the nature of the issue: “urgent”: Critical business impact, service outage “high”: Significant impac…status(TEXT, Optional): The current state of the ticket in the support workflow. Format: String, must be one of: “new”, “open”, “pending”, “hold”, “solved”, “closed” Default: “new” LLM Guidance: For new ticket creation, typically use “new” unless specifically instructed otherwise. Other statuses are more commonly used w…ticketType(TEXT, Optional): The category of the ticket that helps with routing and reporting. Format: String, common values include: “question”, “incident”, “problem”, “task” LLM Guidance: Determine the type based on the nature of the request: “question”: General inquiries or help requests “incident”: Reports of service dis…tags(TEXT, Optional): Labels applied to the ticket for categorization and filtering. Format: Array of strings Example: [“billing”, “subscription”, “error”] Extract relevant keywords from the user’s request to create tags. Use lowercase, simple terms without spaces (use underscores if needed). Include product names, is…customFields(TEXT, Optional): Additional ticket fields specific to the organization’s Zendesk configuration. Format: Array of objects with id and value properties: [{id: 123, value: “some_value”}] LLM Guidance: If the user specifies custom fields, format them as objects with id and value properties. The id must be a number …requesterId(TEXT, Optional): The ID of the user who requested the ticket. Format: Integer LLM Guidance: If the user mentions creating a ticket on behalf of someone else, ask for or extract the requester’s Zendesk user ID. If not specified, this will default to the authenticated API user.assigneeId(TEXT, Optional): The ID of the agent the ticket should be assigned to. Format: Integer or null LLM Guidance: If the user wants to assign the ticket to a specific agent, ask for or extract the agent’s Zendesk user ID. Leave as null for automatic assignment based on Zendesk’s routing rules.groupId(TEXT, Optional): The ID of the support group the ticket should be assigned to. Format: Integer or null LLM Guidance: If the user wants to assign the ticket to a specific support group, ask for or extract the group’s Zendesk ID. Leave as null for automatic assignment based on Zendesk’s routing rules.
Find help center articles
zendesk.find_help_center_articles
Find articles in the Zendesk Help Center
Requires Confirmation: No
Parameters:
query(TEXT, Optional): Search for articles containing specific text. Uses Zendesk Search API for comprehensive text matching.\nFormat: Plain text search terms\nExamples: ‘password reset’, ‘billing questions’, ‘installation guide’\nSearch supports: exact phrases like “password reset”, wildcards, boolean operators\n For …locales(TEXT, Optional): Filter results by language locale. Only works when combined with other search parameters (query, tags, categoryIds, or sectionIds).\nFormat: Locale code (language-country)\nExamples: ‘en-us’, ‘de-de’, ‘fr-fr’, ‘es-es’\nLLM Guidance: Must be used with at least one other search parameter. Returns a…categoryIds(TEXT, Optional): Limit results to articles within a specific category. Provide a single category ID number.\nFormat: Integer\nExample: 12345\nLLM Guidance: Use this to get all articles from a specific category. Cannot be combined with sectionIds parameter. If both categoryIds and sectionIds are provided, category…sectionIds(TEXT, Optional): Limit results to articles within a specific section. Provide a single section ID number.\nFormat: Integer\nExample: 98765\nLLM Guidance: Use this to get all articles from a specific section (more specific than category). Cannot be combined with categoryIds parameter. If both are provided, categor…tags(TEXT, Optional): Filter articles by their label names. Returns articles that have ALL specified labels (AND logic).\nFormat: Comma-separated label names (case-sensitive)\nExamples: ‘HERTHA’ (single label), ‘documentation,guide’ (multiple labels)\nLLM Guidance: Matching is case-sensitive (‘HERTHA’ ≠ ‘hertha’). For…updatedAfter(TEXT, Optional): Filter articles updated after this date. Supports multiple date formats.\nSupported Formats: YYYY-MM-DD, YYYY-MM-DDTHH:MM:SSZ (ISO 8601)\nExamples: ‘2023-01-01’, ‘2023-01-01T12:00:00Z’\nLLM Guidance: Use YYYY-MM-DD for date-only filtering, or full ISO 8601 for specific time filtering. Can be comb…updatedBefore(TEXT, Optional): Filter articles updated before this date. Supports multiple date formats.\nSupported Formats: YYYY-MM-DD, YYYY-MM-DDTHH:MM:SSZ (ISO 8601)\nExamples: ‘2023-12-31’, ‘2023-12-31T23:59:59Z’\nLLM Guidance: Use YYYY-MM-DD for date-only filtering, or full ISO 8601 for specific time filtering. Can be com…sortBy(SELECT, Optional): Choose how to sort the article results. Default behavior varies by context.\nOptions:\n- ‘position’: Manual order set in Zendesk (default for most cases)\n- ‘title’: Alphabetical by article title\n- ‘created_at’: By article creation date\n- ‘updated_at’: By last modification date\nLLM Guidance: U…sortOrder(SELECT, Optional): Choose the direction for sorting results.\nOptions:\n- ‘asc’: Ascending order (A-Z, oldest first, lowest first)\n- ‘desc’: Descending order (Z-A, newest first, highest first)\nLLM Guidance: Use ‘desc’ for most recent items first, ‘asc’ for chronological or alphabetical order. Default varies by so…
Find tickets
zendesk.find_tickets
Finds existing tickets by searching
Requires Confirmation: No
Parameters:
searchQuery(TEXT, Optional): A text string for full-text search across all searchable properties. The query parameter specifies the search criteria for retrieving tickets, users, organizations, or groups from the Zendesk API. It supports a flexible syntax that allows you to define resource types and specific conditions. The …sortOrder(SELECT, Optional):sortBy(SELECT, Optional): Sorting parameter for returned results. One of updated_at, created_at, priority, status, or ticket_type. Defaults to sorting by relevance
Find users
zendesk.find_users
Finds users in Zendesk based on a query string or external ID
Requires Confirmation: No
Parameters:
query(TEXT, Optional): The search query to find users. Format: String Example: “john.doe@example.com” or “John Doe” LLM Guidance: Generate a search query based on the user’s request. The query can specify a partial or full value of any user property, including name, email address, notes, or phone. For example, to find …externalId(TEXT, Optional): Search for a user by their external ID. Format: String LLM Guidance: If the user wants to find a specific user by their external ID, extract that ID and use it here. Note that the external_id parameter does not support the search syntax; it only accepts exact IDs.page(TEXT, Optional): The page number for pagination. Format: Integer Default: 1 LLM Guidance: Use this field to navigate through multiple pages of results. The API returns a maximum of 100 records per page, up to a total of 10,000 records per query.perPage(TEXT, Optional): The number of records to return per page. Format: Integer Default: 100 Maximum: 100 LLM Guidance: Use this field to control how many records are returned per page. The maximum value is 100, which is also the default.
Get article
zendesk.get_article
Gets a specific article from the Zendesk Help Center by ID
Requires Confirmation: No
Parameters:
articleId(TEXT, Required): The unique identifier of the article to retrieve
Get ticket
zendesk.get_ticket
Gets a specific ticket by ID with basic ticket information
Requires Confirmation: No
Parameters:
ticketId(TEXT, Required): The unique identifier of the ticket to retrieve
Get ticket conversation log
zendesk.get_ticket_conversation_log
Gets a specific ticket by ID along with its complete conversation history and logs
Requires Confirmation: No
Parameters:
ticketId(TEXT, Required): The unique identifier of the ticket to retrieve
List users
zendesk.list_users
Retrieves a list of users from Zendesk, with optional filtering by role, permission set, or external ID
Requires Confirmation: No
Parameters:
role(SELECT, Optional): Filters the results by a single role. Format: String Possible values: “end-user”, “agent”, or “admin” LLM Guidance: Use this field to filter users by a specific role. For example, to get only agents, set this to “agent”. If you need to filter by multiple roles, use the roles field instead.roles(TEXT, Optional): Filters the results by multiple roles. Format: Array of strings Possible values: “end-user”, “agent”, or “admin” LLM Guidance: Use this field to filter users by multiple roles. For example, to get both agents and admins, set this to [“agent”, “admin”]. If you only need to filter by a single role,…permissionSet(TEXT, Optional): For custom roles on Enterprise plan and above. Filters by a specific role ID. Format: Integer LLM Guidance: If the user wants to filter by a specific custom role ID, extract that ID and use it here. This is only applicable for Zendesk accounts on the Enterprise plan or above with custom roles con…externalId(TEXT, Optional): List users by external ID. External ID must be unique for each user under the same account. Format: String LLM Guidance: If the user wants to find a specific user by their external ID, extract that ID and use it here. External IDs are typically used to link Zendesk users with users in other systems.page(TEXT, Optional): The page number for pagination. Format: Integer Default: 1 LLM Guidance: Use this field to navigate through multiple pages of results. The API returns a maximum of 100 records per page.perPage(TEXT, Optional): The number of records to return per page. Format: Integer Default: 100 Maximum: 100 LLM Guidance: Use this field to control how many records are returned per page. The maximum value is 100, which is also the default.
Reply to ticket
zendesk.reply_to_ticket
Adds a comment/reply to an existing Zendesk ticket
Requires Confirmation: Yes
Parameters:
ticketId(TEXT, Required): The ID of the ticket to reply to. Format: Integer Example: 12345 LLM Guidance: Extract the ticket ID from the user’s request or context. This is typically a numeric value that uniquely identifies the ticket in Zendesk.comment(MULTI_LINE_TEXT, Required): The content of the reply/comment to add to the ticket. Format: String (can include HTML formatting) Example: “Thank you for your patience. I’ve investigated the issue and found that…” LLM Guidance: Generate a clear and professional response that addresses the user’s concerns or questions. Inclu…isPublic(SELECT, Optional): Determines whether the comment is visible to the end-user/requester. Format: Boolean (true/false) Default: true LLM Guidance: Set to true for comments that should be visible to the customer. Set to false for internal notes visible only to agents. If the user mentions “internal note” or similar ph…
Search
zendesk.search
Searches across Zendesk for tickets, users, organizations, and groups using Zendesk’s query syntax
Requires Confirmation: No
Parameters:
query(TEXT, Required): Search query using Zendesk’s query syntax. Supports operators like : (equals), < > (comparison), - (exclusion), * (wildcard), and “quotes” (exact phrase). Common query patterns: - Filter by type: type:ticket, type:user, type:organization, type:group - Ticket status: status:open, status:pending, s…sortBy(SELECT, Optional): Field to sort results by. Only applies when searching for tickets. Options: - updated_at: Sort by last update time - created_at: Sort by creation time - priority: Sort by ticket priority - status: Sort by ticket status - ticket_type: Sort by ticket type Defaults to relevance if not specified.sortOrder(SELECT, Optional): Direction to sort results. Options: - asc: Ascending (oldest first, A-Z) - desc: Descending (newest first, Z-A) Defaults to desc if not specified.limit(NUMBER, Optional): Maximum number of results to return. The action will automatically paginate through results if needed. Format: Integer Default: 100 Maximum: 1000 (Zendesk API limit) Use smaller limits for faster responses.
Update ticket
zendesk.update_ticket
Updates an existing Zendesk ticket with new information
Requires Confirmation: Yes
Parameters:
ticketId(TEXT, Required): The ID of the ticket to update. Format: Integer Example: 12345 LLM Guidance: Extract the ticket ID from the user’s request or context. This is typically a numeric value that uniquely identifies the ticket in Zendesk.status(SELECT, Optional): The new status of the ticket. Format: String, must be one of: “new”, “open”, “pending”, “hold”, “solved”, “closed” LLM Guidance: Update the status based on the current state of the ticket and the user’s request. Common status changes include: “open”: Ticket is being worked on “pending”: Waiting f…customStatusId(TEXT, Optional): The ID of a custom status to apply to the ticket. Format: Integer LLM Guidance: If the user wants to set a custom status, extract the status ID and use it here. Custom statuses are only available on certain Zendesk plans.priority(SELECT, Optional): The new priority level of the ticket. Format: String, must be one of: “low”, “normal”, “high”, “urgent” LLM Guidance: Update the priority based on the urgency of the issue and the user’s request. Common priority changes include: “urgent”: Critical business impact, service outage “high”: Significa…type(SELECT, Optional): The new type of the ticket. Format: String, common values include: “question”, “incident”, “problem”, “task” LLM Guidance: Update the type based on the nature of the issue and the user’s request. Common type changes include: “question”: General inquiries or help requests “incident”: Reports of se…assigneeId(TEXT, Optional): The ID of the agent to assign the ticket to. Format: Integer or null LLM Guidance: If the user wants to assign the ticket to a specific agent, extract the agent’s Zendesk user ID and use it here. Set to null to remove the current assignee.groupId(TEXT, Optional): The ID of the support group to assign the ticket to. Format: Integer or null LLM Guidance: If the user wants to assign the ticket to a specific support group, extract the group’s Zendesk ID and use it here. Set to null to remove the current group assignment.tags(TEXT, Optional): The new tags to apply to the ticket. Format: List of strings Example:“billing”, “subscription”, “error” LLM Guidance: Update the tags based on the nature of the issue and the user’s request. Extract relevant keywords to create tags. Use lowercase, simple terms without spaces (use underscores if n…customFields(TEXT, Optional): The new custom field values to apply to the ticket. Format: Array of objects with id and value properties: [{id: 123, value: “some_value”}] LLM Guidance: If the user wants to update custom fields, format them as objects with id and value properties. The id must be a number corresponding to the …comment(MULTI_LINE_TEXT, Optional): A comment to add to the ticket with this update. Format: String (can include HTML formatting) Example: “I’ve updated the ticket status to solved.” LLM Guidance: Generate a clear and professional comment that explains the changes being made to the ticket. Include any relevant information or next s…isPublic(SELECT, Optional): Determines whether the comment is visible to the end-user/requester. Format: Boolean (true/false) Default: true LLM Guidance: Set to true for comments that should be visible to the customer. Set to false for internal notes visible only to agents. If the user mentions “internal note” or similar ph…authorId(TEXT, Optional): The ID of the user who is adding the comment. Format: Integer or null LLM Guidance: If the user wants to add a comment on behalf of another user, extract that user’s Zendesk ID and use it here. If not specified, the comment will be attributed to the authenticated API user.