Integrations
Zendesk
16 actions for Zendesk.
Add Zendesk Internal Note#
Add an internal note (private comment) to a Zendesk support ticket.
Plans: Trial, Pro, Premium, Enterprise · Type: ZendeskAddInternalNote · Beta
Inputs#
| Field | Type | Required | Default | What it does |
|---|---|---|---|---|
| Ticket ID | Text | Yes | (empty) | The ID of the ticket to add a note to. |
| Body | Text | Yes | (empty) | The internal note body text. |
| Author ID | Text | No | (empty) | Optional Zendesk user ID of the note author. |
Outputs#
| Output | Type |
|---|---|
| Ticket Id | Any |
| Comment Id | Any |
Use as an agent tool#
Tool name: zendesk_add_internal_note
Add an internal note (private, not visible to requester) on a Zendesk ticket
Add Zendesk Public Reply#
Add a public reply to a Zendesk support ticket.
Plans: Trial, Pro, Premium, Enterprise · Type: ZendeskAddPublicReply · Beta
Inputs#
| Field | Type | Required | Default | What it does |
|---|---|---|---|---|
| Ticket ID | Text | Yes | (empty) | The ID of the ticket to reply to. |
| Body | Text | Yes | (empty) | The reply body text. |
| Author ID | Text | No | (empty) | Optional Zendesk user ID of the comment author. |
Outputs#
| Output | Type |
|---|---|
| Ticket Id | Any |
| Comment Id | Any |
Use as an agent tool#
Tool name: zendesk_add_public_reply
Add a public reply visible to the requester on a Zendesk ticket
Archive Conversation to Zendesk#
Creates a Zendesk ticket with the full conversation history. Each message is added as a separate internal comment. Ticket status is configurable (defaults to ‘open’).
Plans: Trial, Pro, Premium, Enterprise · Type: ZendeskArchiveConversation · Beta
Inputs#
| Field | Type | Required | Default | What it does |
|---|---|---|---|---|
| Subject | Text | No | (empty) | Subject line for the archive ticket. Defaults to ‘Conversation Archive’. |
| Body | Text | No | (empty) | Optional body/description for the ticket. Defaults to a summary line. |
| Requester Email | Text | No | (empty) | Email address to set as the ticket requester. |
| Requester Name | Text | No | (empty) | Display name for the requester. Used together with Requester Email. |
| Tags | Text | No | (empty) | Optional comma-separated tags for the ticket. |
| Group ID | Text | No | (empty) | Optional Zendesk group ID to assign the ticket to. |
| Assignee ID | Text | No | (empty) | Optional Zendesk agent ID to assign the ticket to. |
| Priority | Text | No | (empty) | Ticket priority level. Options: , urgent, high, normal, low |
| Ticket Status | Text | No | open | Status to set on the archived ticket. Use ‘open’ or ‘pending’ if your Zendesk instance requires custom fields to be filled before a ticket can be solved. Options: open, pending, solved, closed |
| Custom Fields | Text | No | (empty) | Optional JSON array of custom fields, e.g. [{“id”: 123, “value”: “abc”}]. |
Outputs#
| Output | Type |
|---|---|
| Ticket Id | Any |
| Ticket Url | Any |
| Status | Any |
| Subject | Any |
| Message Count | Number |
Use as an agent tool#
Tool name: zendesk_archive_conversation
Archive the current chat conversation to Zendesk as a ticket containing the full message history. Optional fields let the agent pass requester email/name, subject, body, tags, priority, status, group/assignee IDs, and custom_fields (JSON array of {id, value} entries).
Check Zendesk Agent Availability#
Check agent availability status in Zendesk.
Plans: Trial, Pro, Premium, Enterprise · Type: ZendeskCheckAgentAvailability · Beta
Inputs#
| Field | Type | Required | Default | What it does |
|---|---|---|---|---|
| Channel Status Filter | Text | No | (empty) | Optional filter by channel and status (e.g. messaging:online). Uses the Zendesk Omnichannel API. Options: , messaging:online, messaging:offline, chat:online, chat:offline |
Outputs#
| Output | Type |
|---|---|
| Agents Online | Number |
| Agents | List |
| Any Available | Yes/No |
Use as an agent tool#
Tool name: zendesk_check_agent_availability
Check which Zendesk agents are currently available/online
Create Zendesk KB Article#
Create a new article in Zendesk Help Center.
Plans: Trial, Pro, Premium, Enterprise · Type: ZendeskCreateKBArticle · Beta
Inputs#
| Field | Type | Required | Default | What it does |
|---|---|---|---|---|
| Section ID | Text | Yes | (empty) | The section ID where the article will be created. |
| Title | Text | Yes | (empty) | The title of the article. |
| Body | Text | Yes | (empty) | The HTML content of the article. |
| Locale | Text | No | en-us | The locale for the article (e.g., en-us). |
| Draft | Text | No | true | Whether the article should be created as a draft. Options: true, false |
Outputs#
| Output | Type |
|---|---|
| Article Id | Text |
| Title | Text |
| Html Url | Text |
| Draft | Yes/No |
Use as an agent tool#
Tool name: zendesk_create_kb_article
Create a new article in Zendesk Knowledge Base
Create Zendesk Ticket#
Create a new support ticket in Zendesk.
Plans: Trial, Pro, Premium, Enterprise · Type: ZendeskCreateTicket · Beta
Inputs#
| Field | Type | Required | Default | What it does |
|---|---|---|---|---|
| Subject | Text | Yes | (empty) | The subject/title of the ticket. |
| Body | Text | Yes | (empty) | The body/description of the ticket. |
| Requester ID | Text | No | (empty) | Optional Zendesk user ID of the requester. Takes precedence over Requester Email. |
| Requester Email | Text | No | (empty) | Email of the requester. Zendesk will match an existing user or create a new one. Ignored when Requester ID is set. |
| Requester Name | Text | No | (empty) | Display name for the requester. Used together with Requester Email. |
| Priority | Text | No | (empty) | Ticket priority level. Options: , urgent, high, normal, low |
| Status | Text | No | (empty) | Ticket status. Options: , new, open, pending, hold, solved, closed |
| Tags | Text | No | (empty) | Optional comma-separated tags for the ticket. |
| Assignee ID | Text | No | (empty) | Optional Zendesk agent ID to assign the ticket to. |
| Group ID | Text | No | (empty) | Optional Zendesk group ID to assign the ticket to. |
| Custom Fields | Text | No | (empty) | Optional JSON array of custom fields, e.g. [{“id”: 123, “value”: “abc”}]. |
Outputs#
| Output | Type |
|---|---|
| Ticket Id | Any |
| Ticket Url | Any |
| Status | Any |
| Subject | Any |
Use as an agent tool#
Tool name: zendesk_create_ticket
Create a new support ticket in Zendesk with subject, body, priority, and other fields
Escalate to Zendesk Agent#
Escalate the conversation to a human Zendesk agent via Chat or Ticket.
Plans: Trial, Pro, Premium, Enterprise · Type: ZendeskEscalateToAgent · Beta
Inputs#
| Field | Type | Required | Default | What it does |
|---|---|---|---|---|
| Conversation Context | Text | Yes | (empty) | Conversation history or escalation reason to include. |
| Channel | Text | No | chat | Escalation channel: ‘chat’ uses Zendesk Messaging (Sunshine Conversations), ’ticket’ creates a Zendesk Support ticket. Options: chat, ticket |
| Subject | Text | No | (empty) | Subject line. Defaults to ‘Escalated from FlowHunt’. |
| Group ID | Text | No | (empty) | Optional Zendesk group to assign to. |
| Assignee ID | Text | No | (empty) | Optional Zendesk agent ID to assign to. |
| Priority | Text | No | normal | Priority level. Options: normal, urgent, high, low |
| Tags | Text | No | (empty) | Optional additional comma-separated tags. |
| Include Conversation History | Text | No | true | Automatically include the full conversation transcript in the escalation. Options: true, false |
| Requester Email | Text | No | (empty) | Email address to set as the ticket requester. If provided, Zendesk will match an existing user or create a new one. Applies to the ’ticket’ channel and sets the Sunshine Conversations user profile for the ‘chat’ channel. |
| Requester Name | Text | No | (empty) | Display name for the requester. Used together with Requester Email. |
| Custom Fields | Text | No | (empty) | Optional JSON array of custom ticket fields, e.g. [{“id”: 123, “value”: “abc”}]. |
| Stop Session Close Trigger | Text | No | true | When enabled, prevents the SessionClosed trigger from firing after escalation. The conversation is now handled by a human agent. Options: true, false |
| Close Session | Yes/No | No | Off | Closes the FlowHunt session after the ticket is created, so the conversation is fully handed over to the Zendesk agent and the bot stops responding. Only applies when Channel is ’ticket’ |
Outputs#
| Output | Type |
|---|---|
| Ticket Id | Any |
| Conversation Id | Any |
| Ticket Url | Any |
| Status | Any |
| Escalated | Yes/No |
| Channel | Text |
| Forwarded Attachment Count | Number |
| Session Closed | Yes/No |
Use as an agent tool#
Tool name: zendesk_escalate_to_agent
Escalate the current conversation to a human Zendesk agent
Get Zendesk KB Article#
Get the full content of a Zendesk Help Center article by ID.
Plans: Trial, Pro, Premium, Enterprise · Type: ZendeskGetKBArticle · Beta
Inputs#
| Field | Type | Required | Default | What it does |
|---|---|---|---|---|
| Article ID | Text | Yes | (empty) | The ID of the article to retrieve. |
Outputs#
| Output | Type |
|---|---|
| Article Id | Text |
| Title | Text |
| Body | Text |
| Html Body | Text |
| Html Url | Text |
| Section Id | Text |
| Locale | Text |
| Label Names | List |
| Created At | Text |
| Updated At | Text |
Use as an agent tool#
Tool name: zendesk_get_kb_article
Get the full content of a Zendesk Knowledge Base article including HTML body
Get Zendesk Ticket#
Retrieve a Zendesk support ticket by ID.
Plans: Trial, Pro, Premium, Enterprise · Type: ZendeskGetTicket · Beta
Inputs#
| Field | Type | Required | Default | What it does |
|---|---|---|---|---|
| Ticket ID | Text | Yes | (empty) | The ID of the ticket to retrieve. |
Outputs#
| Output | Type |
|---|---|
| Ticket Id | Any |
| Subject | Any |
| Description | Any |
| Status | Any |
| Priority | Any |
| Requester Id | Any |
| Assignee Id | Any |
| Tags | List |
| Created At | Any |
| Updated At | Any |
Use as an agent tool#
Tool name: zendesk_get_ticket
Retrieve a Zendesk support ticket by its ID including status, priority, and details
Get Zendesk Ticket Comments#
Retrieve comments/conversation for a Zendesk support ticket.
Plans: Trial, Pro, Premium, Enterprise · Type: ZendeskGetTicketComments · Beta
Inputs#
| Field | Type | Required | Default | What it does |
|---|---|---|---|---|
| Ticket ID | Text | Yes | (empty) | The ID of the ticket to get comments for. |
| Sort Order | Text | No | asc | Sort order for comments (asc = oldest first, desc = newest first). Options: asc, desc |
Outputs#
| Output | Type |
|---|---|
| Ticket Id | Any |
| Comments | List |
| Comment Count | Number |
Use as an agent tool#
Tool name: zendesk_get_ticket_comments
Retrieve all comments and conversation history for a Zendesk ticket
List Zendesk KB Categories#
List all categories in Zendesk Help Center.
Plans: Trial, Pro, Premium, Enterprise · Type: ZendeskListKBCategories · Beta
Inputs#
| Field | Type | Required | Default | What it does |
|---|---|---|---|---|
| Locale | Text | No | en-us | The locale for the categories (e.g., en-us). |
Outputs#
| Output | Type |
|---|---|
| Categories | List |
| Count | Number |
Use as an agent tool#
Tool name: zendesk_list_kb_categories
List all categories in Zendesk Knowledge Base
List Zendesk KB Sections#
List sections in a Zendesk Help Center category.
Plans: Trial, Pro, Premium, Enterprise · Type: ZendeskListKBSections · Beta
Inputs#
| Field | Type | Required | Default | What it does |
|---|---|---|---|---|
| Category ID | Text | No | (empty) | Optional category ID to filter sections. If empty, lists all sections. |
Outputs#
| Output | Type |
|---|---|
| Sections | List |
| Count | Number |
Use as an agent tool#
Tool name: zendesk_list_kb_sections
List sections in a Zendesk Knowledge Base category
Search Zendesk KB Articles#
Search for articles in Zendesk Help Center Knowledge Base.
Plans: Trial, Pro, Premium, Enterprise · Type: ZendeskSearchKBArticles · Beta
Inputs#
| Field | Type | Required | Default | What it does |
|---|---|---|---|---|
| Query | Text | Yes | (empty) | The search query to find articles. |
| Category ID | Text | No | (empty) | Optional category ID to filter results. |
| Section ID | Text | No | (empty) | Optional section ID to filter results. |
| Label Names | Text | No | (empty) | Optional comma-separated label names to filter results. |
| Locale | Text | No | en-us | The locale for the search (e.g., en-us). |
| Per Page | Text | No | 25 | Number of results per page (max 100). |
Outputs#
| Output | Type |
|---|---|
| Articles | List |
| Count | Number |
| Query | Text |
Use as an agent tool#
Tool name: zendesk_search_kb_articles
Search for articles in Zendesk Knowledge Base by keyword, category, section, or labels
Search Zendesk Tickets#
Search for tickets in Zendesk using the search API.
Plans: Trial, Pro, Premium, Enterprise · Type: ZendeskSearchTickets · Beta
Inputs#
| Field | Type | Required | Default | What it does |
|---|---|---|---|---|
| Query | Text | Yes | (empty) | The search query (Zendesk search syntax). ’type:ticket’ is automatically prepended. |
| Sort By | Text | No | (empty) | Field to sort results by. Options: , created_at, updated_at, priority, status |
| Sort Order | Text | No | desc | Sort order for results. Options: desc, asc |
| Per Page | Text | No | 25 | Number of results per page (max 100). |
Outputs#
| Output | Type |
|---|---|
| Tickets | List |
| Count | Number |
Use as an agent tool#
Tool name: zendesk_search_tickets
Search for Zendesk tickets by query, status, assignee, or date range
Update Zendesk KB Article#
Update an existing article in Zendesk Help Center.
Plans: Trial, Pro, Premium, Enterprise · Type: ZendeskUpdateKBArticle · Beta
Inputs#
| Field | Type | Required | Default | What it does |
|---|---|---|---|---|
| Article ID | Text | Yes | (empty) | The ID of the article to update. |
| Title | Text | No | (empty) | The new title for the article. Leave empty to keep current. |
| Body | Text | No | (empty) | The new HTML content for the article. Leave empty to keep current. |
| Draft | Text | No | unchanged | Whether the article should be a draft. Select ‘unchanged’ to keep current status. Options: true, false, unchanged |
Outputs#
| Output | Type |
|---|---|
| Article Id | Text |
| Title | Text |
| Html Url | Text |
| Updated | Yes/No |
Use as an agent tool#
Tool name: zendesk_update_kb_article
Update an existing article in Zendesk Knowledge Base
Update Zendesk Ticket#
Update an existing Zendesk support ticket.
Plans: Trial, Pro, Premium, Enterprise · Type: ZendeskUpdateTicket · Beta
Inputs#
| Field | Type | Required | Default | What it does |
|---|---|---|---|---|
| Ticket ID | Text | Yes | (empty) | The ID of the ticket to update. |
| Status | Text | No | (empty) | New ticket status. Options: , new, open, pending, hold, solved, closed |
| Priority | Text | No | (empty) | New ticket priority. Options: , urgent, high, normal, low |
| Assignee ID | Text | No | (empty) | New assignee agent ID. |
| Tags | Text | No | (empty) | Comma-separated tags to set on the ticket (replaces existing tags). |
| Custom Fields | Text | No | (empty) | Optional JSON array of custom fields, e.g. [{“id”: 123, “value”: “abc”}]. |
Outputs#
| Output | Type |
|---|---|
| Ticket Id | Any |
| Status | Any |
| Updated Fields | List |
Use as an agent tool#
Tool name: zendesk_update_ticket
Update an existing Zendesk ticket’s status, priority, assignee, tags, or custom fields