> ## Documentation Index > Fetch the complete documentation index at: https://help.wotnot.io/llms.txt > Use this file to discover all available pages before exploring further. # Zendesk > Create tickets, fetch ticket status and perform live chat from Zendesk. ![Image](https://mintcdn.com/wotnot/ZvBlY58cOcRHCVBj/images/image-559.png?fit=max\&auto=format\&n=ZvBlY58cOcRHCVBj\&q=85\&s=7b7f0fa45bd4c5cffedde526fc638626) Zendesk is a popular ticketing system used by many organizations. With WotNot's Zendesk integration, you will be able to perform the following actions: 1. **Create tickets** 2. **Get ticket status** 3. **Live chat in Zendesk** > [!NOTE] > > **Push and fetch:** Zendesk supports both sending information from WotNot to Zendesk and fetching ticket information back into the chatbot. > [!NOTE] > > Available on the **STARTER** plan and above. # What you can do | Capability | What it does | Action block | What the user experiences | | - | - | - | - | | **Create a ticket** | Creates a new support ticket in Zendesk using information collected during the conversation. | Zendesk action block | The visitor can receive the newly created ticket number and continue the conversation. | | **Get ticket status** | Fetches information about an existing Zendesk ticket. | Zendesk action block | The visitor can provide their ticket number and receive its current status or other saved ticket details. | | **Live chat in Zendesk** | Creates a Zendesk ticket and routes the conversation to a Zendesk agent. | Zendesk action block | The visitor can continue chatting while the agent responds from Zendesk instead of WotNot Live Chat. | # Before you start Make sure you have the following ready before connecting Zendesk: * A Zendesk account with API access. * Administrator access to your Zendesk account. * Your Zendesk account email. * A Zendesk API token. * Your Zendesk helpdesk URL or subdomain, for example:\ `https://yourcompany.zendesk.com` * Any mandatory Zendesk ticket fields that you want to populate from WotNot. * A WotNot plan that supports the Zendesk integration. If you are creating a live chat integration, make sure your Zendesk ticket configuration and automation rules can assign newly created tickets to the appropriate agents. # Connecting Zendesk 1. Open your chatbot flow. 2. Add the **Zendesk** action block. 3. Click **connect Zendesk account**. 4. Enter an **Account name** to identify the Zendesk connection. 5. Enter your **Helpdesk URL**. 6. Enter the **Zendesk account email**. 7. Enter your **API token**. 8. Save the connection. > [!NOTE] > > WotNot currently uses an **API token** for the Zendesk connection. The Zendesk account email is an administrator email and is also used when configuring the webhook required for Zendesk live chat. # Using it in a flow ### Create Tickets Using this action block, after collecting information from users, your chatbot can create a ticket on Zendesk and acknowledge the user with the created ticket number. For example, you are creating an IT support chatbot that: * Collects user's email address * Category of the problem (Hardware, Software, Networking, Something else...) * Sub-category of the problem (PC not starting, PC stuck ...) * Description of the problem * Files/images to be attached and creates a ticket on Zendesk after collecting these details. **1. Connect your Zendesk account** Connect your Zendesk account by clicking on “+ Add account”, and choose it from the dropdown. * **Account name** - General name for this account. * **Helpdesk URL** - Domain on your Zendesk account i.e. [https://wotnot2535.zendesk.com](https://wotnot2535.zendesk.com) * **Zendesk account email** - An administrator's email address. It will be used to configure WotNot's webhook on Zendesk (used for live chat for Zendesk). * **API token** - API token created on Zendesk. [Follow these steps](https://support.zendesk.com/hc/en-us/articles/4408889192858-Managing-access-to-the-Zendesk-API#topic_bsw_lfg_mmb) ![Screenshot 2026 08 27 114642](https://mintcdn.com/wotnot/79SKP2TEnpNsM0nK/images/Screenshot-2026-08-27-114642.png?fit=max\&auto=format\&n=79SKP2TEnpNsM0nK\&q=85\&s=3cd421e5ed7eee27b992a2df9ecb3ad7) **2. Configure the fields** Map the Zendesk fields on the left column with the respective WotNot variables which contain its data. > [!NOTE] > > Make sure that you configure all the mandatory fields of your Zendesk account here. Otherwise, tickets may not be created due to missing field information. ![Screenshot 2026 08 27 144759](https://mintcdn.com/wotnot/79SKP2TEnpNsM0nK/images/Screenshot-2026-08-27-144759.jpg?fit=max\&auto=format\&n=79SKP2TEnpNsM0nK\&q=85\&s=796955df80ba9a896fee7bdc510087ff) **3. Acknowledge the user** Using this action, you can fetch the status of a ticket from Zendesk. This helps users be informed of the progress being made on their tickets. ### Get ticket status Using this action, you can fetch the status of a ticket from Zendesk. This helps users be informed of the progress being made on their tickets. **1. Connect your Zendesk account** Connect your Zendesk account by clicking on “+ Add account”, and choose it from the dropdown. * **Account name** - General name for this account. * **Helpdesk URL** - Domain on your Zendesk account i.e. [https://wotnot2535.zendesk.com](https://wotnot2535.zendesk.com) * **Zendesk account email** - An administrator's email address. It will be used to configure WotNot's webhook on Zendesk (used for live chat for Zendesk). * **API token** - API token created on Zendesk. [Follow these steps](https://support.zendesk.com/hc/en-us/articles/4408889192858-Managing-access-to-the-Zendesk-API#topic_bsw_lfg_mmb) ![Screenshot 2026 08 27 114642 1](https://mintcdn.com/wotnot/79SKP2TEnpNsM0nK/images/Screenshot-2026-08-27-114642-1.png?fit=max\&auto=format\&n=79SKP2TEnpNsM0nK\&q=85\&s=51f28037f5ccb3a5714e7684cde816ba) **2. Save the response** In order to fetch the status of a ticket, we need to first collect the ticket number from the user. Use a "Collect input" action block to collect and store the ticket ID into a variable. Then choose that variable in the Zendesk action block and choose the list of fields you want to save. For example, you want to save the "Status", "Last updated" fields and send a acknowledgement message to the user saying *"The status of your #ticket\_id# is #ticket\_status#. It was last updated on #last\_updated#".* ![Screenshot 2026 08 27 145226](https://mintcdn.com/wotnot/79SKP2TEnpNsM0nK/images/Screenshot-2026-08-27-145226.jpg?fit=max\&auto=format\&n=79SKP2TEnpNsM0nK\&q=85\&s=6e5e1014a053ed4c632ef2cb57ab8ae2) ### Route a chat to Zendesk Use the Zendesk live chat capability when the visitor needs help from a human agent and your support team works in Zendesk. The live chat flow first creates a Zendesk ticket and then uses your Zendesk configuration and automation rules to assign the ticket to an agent. See [Live chat via Zendesk](#live-chat-via-zendesk) for the complete setup. # Mapping fields When configuring the Zendesk action block, map the information collected by WotNot to the corresponding Zendesk ticket fields. | **WotNot variable** | **Zendesk ticket field** | **Required** | | :- | :- | :- | | Visitor email variable | Requester / email | Depends on your Zendesk configuration | | Visitor name variable | Requester / name | Depends on your Zendesk configuration | | Subject variable | Subject | If required by your Zendesk configuration | | Description variable | Description | If required by your Zendesk configuration | | Priority variable | Priority | Only if required or used in your workflow | | Type variable | Type | Only if required or used in your workflow | | Tags variable | Tags | Optional | | Custom field variables | Corresponding custom fields | Required only when configured as mandatory in Zendesk | #### Requester identity The visitor information you collect in WotNot must be mapped to the corresponding Zendesk ticket fields. Before publishing the flow, verify which requester fields are mandatory in your Zendesk setup and make sure the corresponding WotNot variables are populated. Make sure the required requester information, such as an email address, is available before creating the ticket. #### Subject and description Use the **Subject** field for a short summary of the issue. Use the **Description** field for the detailed customer request or conversation context. #### Priority and type If your Zendesk workflow uses **Priority** or **Type**, make sure the value stored in the WotNot variable matches a value accepted by Zendesk. #### Tags Tags help your support team categorize and filter tickets. You can map static values or WotNot variables to Zendesk tags. #### Custom fields If your Zendesk account uses custom ticket fields, make sure those fields already exist before mapping them in WotNot. If a custom field is mandatory, map it to a WotNot variable before the ticket is created. Missing mandatory fields can prevent ticket creation. # **Live chat via Zendesk** With this action block, users can seamlessly engage in live conversations with your agents directly from the Zendesk portal. This eliminates the need for agents to access WotNot live chat, allowing them to communicate with users through ticket pages using comments. **1. Connect your Zendesk account** Follow these steps to connect as mentioned above Connect your Zendesk account by clicking on “+ Add account”, and choose it from the dropdown. * **Account name** - General name for this account. * **Helpdesk URL** - Domain on your Zendesk account i.e. [https://wotnot2535.zendesk.com](https://wotnot2535.zendesk.com) * **Zendesk account email** - An administrator's email address. It will be used to configure WotNot's webhook on Zendesk (used for live chat for Zendesk). * **API token** - API token created on Zendesk. [Follow these steps](https://support.zendesk.com/hc/en-us/articles/4408889192858-Managing-access-to-the-Zendesk-API#topic_bsw_lfg_mmb) ![Screenshot 2026 08 27 112905](https://mintcdn.com/wotnot/79SKP2TEnpNsM0nK/images/Screenshot-2026-08-27-112905.png?fit=max\&auto=format\&n=79SKP2TEnpNsM0nK\&q=85\&s=7134c0a3ea68fa648f098fbe2fd64188) **2. Mapping the required fields to create a ticket** n order to start a new live chat, the system needs to first create a ticket and assign it to your agent. Hence, map the Zendesk fields with the WotNot variables required to create a ticket on Zendesk. > [card] MAKE SURE : > > * Make sure that you configure all the mandatory fields of your Zendesk account here. Otherwise, tickets may not be created due to missing field information. > * When the ticket is created on Zendesk, based on your Zendesk automation rules, the ticket will be auto-assigned to an agent. **3. Setup the acknowledgement messages** When the ticket is successfully created on Zendesk, you can choose the variable where the ticket ID is to be stored, and define a acknowledgement message like: > Your ticket #ticket\_id# has been created. > > Our agent will be with you shortly. ![Screenshot 2026 08 27 150516](https://mintcdn.com/wotnot/79SKP2TEnpNsM0nK/images/Screenshot-2026-08-27-150516.png?fit=max\&auto=format\&n=79SKP2TEnpNsM0nK\&q=85\&s=6821429ab76781e23f3450a893292d57) > [!NOTE] > > If the agent to whom the ticket is assigned on Zendesk is not present on WotNot, the system will automatically add that person as a user on WotNot with an "Agent" role. ### **Live Chat for Zendesk in WhatsApp** When using the **"Live Chat for Zendesk"** block in the WhatsApp channel, users must select a WhatsApp template. * The selected template will be sent to the user if a new comment is received from a Zendesk agent. * A new conversation will be created using the selected template message and assigned to the same agent who added the comment. * This behavior is implemented due to WhatsApp's limitation on sending free-text messages after the user session window has closed. **Best Practice:**\ Define a template message that clearly informs the user about the new comment on their ticket and encourages them to respond. When the user replies to the template message, the agent will be notified in Zendesk and can continue the conversation by adding comments with the required details. ![Screenshot 2026 08 27 151041](https://mintcdn.com/wotnot/79SKP2TEnpNsM0nK/images/Screenshot-2026-08-27-151041.png?fit=max\&auto=format\&n=79SKP2TEnpNsM0nK\&q=85\&s=a9859f93bff2d152549fd9086470b185) # Zendesk vs. WotNot Live Chat Zendesk live chat is different from WotNot's standard Live Chat experience. | Zendesk Live Chat | WotNot Live Chat | | - | - | | Agent works from Zendesk | Agent works from WotNot | | Conversation is handled through a Zendesk ticket | Conversation is handled from WotNot's Live Chat page | | Zendesk automation assigns the ticket | WotNot handles the live chat workflow | **For WotNot's native agent handoff, see [Talk to human](https://help.wotnot.io/build/blocks/talk-to-human.md).** # **Known behaviors** The following are some expected behaviors and limitations when integrating Zendesk with WotNot across different channels. These behaviors stem from platform restrictions and specific implementation choices to ensure optimal functionality. * Only **bold** and *italic* text formats are supported and will be displayed correctly in WhatsApp and the web channel. Other formatting styles will not appear as they do in Zendesk due to channel restrictions. * Agents will **not** be notified in Zendesk when a conversation is closed from the WotNot side. * The **"Add Link"** feature in Zendesk comments will not render the URL properly on WhatsApp or the chat widget. However, if a URL is added as plain text in the message, it will be automatically converted into a clickable link. * **Internal notes** added by an agent in Zendesk will not appear on the WotNot Live Chat page and will not be visible to the customer. * Multiple attachments added in a **single** Zendesk comment will be sent as **individual messages** to the user. * Unsupported media types in certain channels will either be **discarded** or not sent to the user. * If an agent adds a comment to a **closed ticket**, the following will occur: * For **WhatsApp**, a new conversation will be created in WotNot with a template message. * For the **web channel**, the comment will be ignored, and no further action will be taken on WotNot’s side. # Troubleshooting > [accordion] My Zendesk token is invalid > > Check that the API token or OAuth authorization is still valid. > > If the token was revoked, expired, or regenerated, reconnect Zendesk from **Settings → Integrations** and complete the authentication process again. > [accordion] My Zendesk subdomain is incorrect > > Verify that you entered the correct Zendesk subdomain. > > For example, if your Zendesk URL is `https://company.zendesk.com`, enter `company` as the subdomain. > [accordion] The ticket was created without a requester > > Make sure the requester information is available in WotNot and mapped correctly to the Zendesk requester field. > > If your Zendesk configuration requires a requester email address, make sure the conversation collects the customer's email before creating the ticket. > [accordion] My custom field was rejected > > Verify that the custom field exists in Zendesk and that the value being sent from WotNot matches the field's expected format. > > Also check whether the custom field is required and whether the supplied value is valid for the available field options. > [accordion] The ticket status lookup returns nothing > > Verify that the ticket ID being passed to Zendesk is correct. > > Make sure the variable containing the ticket ID is populated before the Zendesk status lookup runs. > [accordion] Chats are not reaching Zendesk agents > > Verify that the Zendesk integration is connected and that the **Talk to human** block is configured correctly. > > Check the routing and agent availability settings in Zendesk. Then test the flow again to confirm that the conversation is being transferred successfully. This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.