> 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-freshdesk.md).

# Integrating with Freshdesk

Sync Freshdesk support data with Drivetrain to add customer success metrics into planning. Covers API key, domain config, and completing the connection.

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

* **In Drivetrain:** you need to be an admin.
* **In Freshdesk:** an active subscription and an agent with admin privileges whose account is verified (Freshdesk shows the API key only to verified agents). The API key has exactly that agent's access, so use an agent who can see all the tickets you want in Drivetrain.

## Step 1: Get your subdomain and API key <a href="#step-1-get-your-subdomain-and-api-key" id="step-1-get-your-subdomain-and-api-key"></a>

1. Sign in to Freshdesk. Your subdomain is the first part of the URL: for `https://mysubdomain.freshdesk.com` it's `mysubdomain`.
2. Click your profile picture in the top-right corner and select **Profile Settings**.
3. Click **View API key**, complete the captcha and copy the key.

<figure><img src="https://4220329029-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FmBZR0D9lq6jrI895OuOU%2Fuploads%2Fgit-blob-7fad77411d30ff3b9831c465e5d438dffeba8cf6%2FFreshdesk.avif?alt=media" alt=""><figcaption></figcaption></figure>

## 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 **Freshdesk** (under **Ticketing**, or search for it).
2. Drivetrain shows **Freshdesk is a premium integration**. Click **Request access**.
3. Click **Add field** twice and enter `Subdomain` and `API key` with their values. If the form already lists fields under **Connector fields**, fill those in instead. Click **Submit credentials**.
4. Freshdesk 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>

Tickets and related Freshdesk data such as conversations, contacts, companies, agents, groups, products and ticket 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. |
| **Freshdesk not in your subscription**                                         | Freshdesk 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.                                                     |
| Syncs fail after someone reset the API key                                     | Resetting the key in Freshdesk disconnects every app using it. Send the new key 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-freshdesk.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.
