> 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/others/integrating-with-clari.md).

# Integrating with Clari

Pull Clari revenue forecasting data into Drivetrain to align pipeline projections with financial models. Covers generating a Clari API token.

Drivetrain connects to Clari with a Clari API token.

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

* A Clari user who can see the **API Token** tab in Clari settings. If you don't see it, ask your Clari customer success manager to enable it.
* **Admin** access in Drivetrain.

### Clari setup <a href="#clari-setup" id="clari-setup"></a>

#### Create an API token <a href="#creating-an-authentication-token" id="creating-an-authentication-token"></a>

1. Log in to Clari.
2. Click your avatar and select **Settings**.
3. Open the **API Token** tab and click **Generate New API Token**.
4. Enter a **Token Name** and click **Generate New Token**.
5. Copy the token and store it securely. Clari won't show it again.

{% hint style="danger" %}

1. If you revoke a token, any active integration that is using that token will break.
2. When deactivating a user, any tokens created by the user will be revoked (and thus break any active integration).
   {% endhint %}

### Connect in Drivetrain

1. On the **Data** page, click **+** next to **Data** (or **Add data source** if nothing is connected yet).
2. In **Connect a data source**, select **Clari**.
3. Clari is a premium integration: click **Request access**.
4. Paste the token into **API Key** and click **Submit credentials**.

The connection shows **Credentials submitted** until your Drivetrain team finishes the setup.


---

# 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/others/integrating-with-clari.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.
