> For the complete documentation index, see [llms.txt](https://integrations.drivetrain.ai/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://integrations.drivetrain.ai/integration-guide/readme/customer-success/integrating-with-zendesk.md).

# Integrating with Zendesk

Connect Zendesk to Drivetrain and sync support ticket data into planning models. Covers the subdomain, the admin user and the in-app connection request.

## Before you start <a href="#before-you-start" id="before-you-start"></a>

* **In Drivetrain:** you need to be an admin.
* **In Zendesk:** an active account and an admin user. We recommend a dedicated admin user for Drivetrain, so the connection doesn't break when someone leaves. Don't create an API token unless your customer success manager asks: Zendesk API tokens all stop working by April 30, 2027.

## Step 1: Note your subdomain <a href="#step-1-note-your-subdomain" id="step-1-note-your-subdomain"></a>

Your subdomain is the first part of your Zendesk URL: for `https://acme.zendesk.com` it's `acme`.

## Step 2: Connect in Drivetrain <a href="#step-2-connect-in-drivetrain" id="step-2-connect-in-drivetrain"></a>

1. Go to **Data** in the left navigation, click the **+** button and select **Zendesk** (under **Ticketing**, or search for it). Don't pick **Zendesk Sell**: that's Zendesk's CRM.
2. Drivetrain shows **Zendesk is a premium integration**. Click **Request access**.
3. Click **Add field** twice and enter `Subdomain` and `Admin email` (the admin user's email) with their values. If the form already lists fields under **Connector fields**, fill those in instead. Click **Submit credentials**.
4. Zendesk appears on the **Data** page with the status **Credentials submitted**. Drivetrain completes the setup and runs the first sync; the **Sync** option stays hidden until then.

## What data comes in <a href="#what-data-comes-in" id="what-data-comes-in"></a>

Zendesk data such as tickets, comments, contacts, attachments, accounts, users, teams and tags.

## Troubleshooting <a href="#troubleshooting" id="troubleshooting"></a>

| What you see                                                                   | Cause and fix                                                                                                                                                                      |
| ------------------------------------------------------------------------------ | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| **Submit credentials** does nothing                                            | No field has both a name and a value. Fill in both: a row missing either is dropped without warning.                                                                               |
| You submitted a wrong value                                                    | While the status is **Credentials submitted**, repeat Step 2. The new submission replaces the pending one.                                                                         |
| `This connector is currently being set up. Please try again once it finishes.` | Drivetrain has started setting up or syncing this connector, so your submission wasn't saved. Don't submit again: send the corrected credentials to your customer success manager. |
| **Zendesk not in your subscription**                                           | Zendesk isn't in your plan. Contact Drivetrain support to add it.                                                                                                                  |
| You need to change credentials after setup                                     | Don't repeat Step 2: after setup, that creates a second connection. Send the new credentials to your customer success manager.                                                     |


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://integrations.drivetrain.ai/integration-guide/readme/customer-success/integrating-with-zendesk.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
