> 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/crm/integrating-with-pipedrive.md).

# Integrating with Pipedrive

Connect Pipedrive to Drivetrain and pull deal and pipeline data into revenue models. Covers signing in from the Data page and which user to sign in with.

You connect Pipedrive yourself by signing in from Drivetrain. You don't need a separate user or to share credentials.

## Before you start

* **In Drivetrain:** an admin role (or a role with the **Connect a data source** action).
* **In Pipedrive:** sign in as an admin, or a user who can see all the deals you want in Drivetrain. Pipedrive's visibility settings decide what each user can see.

## Connect Pipedrive

1. Go to the **Data** page and click the **+** icon at the top of the **Data** panel (or **Add data source** if nothing is connected yet).
2. Select **Pipedrive** and click **Login to connect**.
3. Sign in to your [Pipedrive](https://app.pipedrive.com/auth/login) account and approve access for Drivetrain.

You return to Drivetrain, and Pipedrive appears in the **Data** panel. Drivetrain uses your deals, stages, organizations and users.

{% hint style="info" %}
Drivetrain supports one Pipedrive connection per workspace. To sign in again (for example after access was revoked), use the three dots next to the connection > **Edit credentials**. **Remove** disconnects Pipedrive and deletes its synced data in Drivetrain.
{% endhint %}


---

# 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/crm/integrating-with-pipedrive.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.
