Connect Zendesk to Kimola
min read - Updated on Oct 28, 2026You can connect Zendesk to Kimola to analyze your support tickets with AI, without exporting them first. You type your Zendesk subdomain, allow Kimola to read your account in a Zendesk window, and Kimola reads your tickets with their comments. The tickets then open as a dataset in the report wizard, where you choose the columns, the classifiers and the Dimensions the same way as for an uploaded file. The result is a Report that shows what your customers contact support about, how they feel about each topic and which topics perform worst.
The Zendesk integration is available in the paid packages (Basic, Standard, Business and Enterprise), not in Starter. It is one of the data sources Kimola connects to for Reports; see What are Integrations? for the others.
You need your Zendesk subdomain and a Zendesk account that can see the tickets you want to analyze. The subdomain is the part of your Zendesk address before ".zendesk.com": if your team opens Zendesk at https://acme.zendesk.com, it is acme. Kimola only reads tickets: it never answers, changes or closes them.
See kimola.com/pricing for the packages that include integrations. Kimola On-Premises doesn't offer the Zendesk integration.
Step 1: Enter Your Zendesk Subdomain
You can start the connection from your account's Integrations page or from the Reports page. Both open the same Zendesk Support window.
From Account › Integrations. Open ACCOUNT in the main menu and go to Integrations. Under AVAILABLE, find the Zendesk card ("Analyze support tickets") and click the + on it.
From Reports. Open REPORTS. Under the upload area, Integrations lists Intercom, Zendesk and Google Sheets, each with an icon that is gray while the integration isn't connected. Click Zendesk.
In the Zendesk Support window, type your subdomain in Sub Domain. Type only the subdomain, without "https://" and ".zendesk.com": acme, not https://acme.zendesk.com. Then click Connect.
If Kimola can't find a Zendesk account at that address, the window shows "Please type a subdomain." Compare what you typed with the address bar of your Zendesk and try again. To leave without connecting, click Close.
[Screenshot: The Zendesk Support window with the Sub Domain field and the Connect button]
Step 2: Authorize Kimola
After you click Connect, Zendesk opens its authorization page for your subdomain in a new window. Sign in to Zendesk if it asks you to, and allow Kimola to access your account. Kimola requests read access.
Zendesk's authorization page opens in a new browser window, so allow pop-ups for app.kimola.com.
When you allow it, Kimola saves the connection and the window closes by itself. Zendesk then appears under ACTIVE on the Integrations page, with the date it was connected, and its icon turns green in the Integrations list on REPORTS.
If the window reports an error instead, the connection wasn't saved. Start again from Step 1.
The connection belongs to your team's Kimola account, so your teammates don't need to connect Zendesk again to create Reports from the same tickets.
[Screenshot: The Integrations page with Zendesk under ACTIVE]
Step 3: Create a Report from Your Tickets
With Zendesk connected, you create a Report from your tickets on the REPORTS page. The tickets go through the same steps as an uploaded file: columns, classifiers, structure, Dimensions and a final review. See Create a Report Using Integrations for how the three integrations compare.
Open Your Tickets
Open REPORTS and click Zendesk under Integrations. Because Zendesk is connected, Kimola reads your tickets with their comments and opens them in the report wizard as a dataset with a Tickets sheet.
Choose the Columns
The wizard opens on Sheets & Columns: "Here is the preview of your dataset file. Choose required columns to continue." The step shows the Tickets sheet with a preview of its rows and the number of rows in total.
The Tickets sheet has one row per ticket and three columns. Content holds the whole conversation of the ticket: its description followed by every comment, one under another. Zendesk's automatic chat transcripts (comments that contain "Conversation with") are left out. Date is the date the ticket was created, and Ticket Id is the ticket's number in Zendesk.
Kimola doesn't separate public replies from internal notes, so the internal notes your Zendesk account can see are part of Content too.
Choose Content as the Text Column and Date as the Date Column. Leave the Url Column empty, because the sheet has no ticket links. With a Date Column, the Report can show how topics change over time.
[Screenshot: The Sheets & Columns step with Content chosen as the Text Column and Date as the Date Column]
Choose Classifiers and Dimensions
In Classifiers, choose the models that label your tickets. The Automatic Classifier discovers the themes from the tickets themselves, and the Sentiment Classifier labels the sentiment of every ticket. You can add other pretrained models, such as the Software Feedback Classifier or the E-Commerce Feedback Classifier, or your own custom models. Choose a content classifier and the Sentiment Classifier together to see the best and worst performing themes.
In Structure, decide whether a ticket can get more than one label. Enable Multi-label Classification suits support tickets, because one ticket often raises more than one issue: a late delivery and a refund request, for example. See Create a Report Using Multi-Label Classification.
In Dimensions, you can choose research questions to ask of every ticket. They are optional. For support tickets, Pain Points ("What goes wrong or creates difficulty?"), Underlying Causes ("Why does this occur?") and Unmet Needs ("What is missing or desired?") are a common start. See Add Dimensions to a Report.
[Screenshot: The Classifiers step with the Automatic Classifier and the Sentiment Classifier chosen]
Review and Create the Report
The Review step shows your choices before anything is analyzed: an optional Report Title, the Report Language, the Dataset and the Required Query. The Report Language is the language the Report is written in: English, Spanish, French, German, Portuguese, Dutch or Turkish. Your tickets can be in any of the 30+ languages Kimola analyzes, whatever the Report Language.
Analyzing tickets uses queries = rows × models × Dimensions. The Required Query shows the total before anything is analyzed.
Confirm to start the analysis. When it is complete, Kimola shows "Here we go!" and View Report opens your Report.
The Report analyzes the tickets Kimola read when you created it and doesn't update itself from Zendesk later. To analyze newer tickets, create a new Report from Zendesk.
The Report opens on Overview: the number of records analyzed, the sentiment, the best and worst performing themes and your Dimensions. To see which support topics customers are least satisfied with, open Performance. For the whole workflow, from tickets to an Action Plan, see How to Analyze Support Tickets, and for more on analyzing support and call conversations with Kimola, see Conversation Analysis.
[Screenshot: The Overview of a Report created from Zendesk tickets]
Disconnect Zendesk
You disconnect Zendesk from your account's Integrations page. Once disconnected, Kimola can no longer read your tickets until someone connects Zendesk again.
Open ACCOUNT, go to Integrations and find the Zendesk card under ACTIVE. Click the delete icon on the card. Kimola asks "Are you sure you want to remove connection Zendesk?" Click Yes, delete it.
Zendesk moves back to AVAILABLE, and its icon on REPORTS turns gray again. To analyze your tickets again later, connect Zendesk from Step 1.
Reports you created from Zendesk tickets stay as they are, with all their results. Each Report keeps its own copy of the tickets it analyzed and doesn't connect to Zendesk again.
Disconnecting removes the connection from Kimola only. To withdraw Kimola's read access completely, a Zendesk admin removes Kimola from Zendesk's list of authorized apps too.
[Screenshot: The confirmation for removing the Zendesk connection]