> For the complete documentation index, see [llms.txt](https://docs.whaly.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.whaly.io/connectors/source-catalog/sales-crms/pipedrive.md).

# Pipedrive

## **Why syncing my Pipedrive to** [**Whaly**](https://whaly.io)**?**

Syncing your Pipedrive account can be useful for various cases:

* Understand who your contacts are
* Analyse your deal pipeline variation on a weekly / monthly basis
* Check the effect of your marketing campaigns on sales
* Build Sales Rep performance dashboards to animate your sales team
* Reconcile your Sales closed amount with the cash that you really collected
* ...

## Which Pipedrive data is synced by [Whaly](https://whaly.io)?

[Whaly](https://whaly.io) 🐳 is currently syncing the following data:

* **Person**: Persons are your contacts, the customers you are doing Deals with.
* **Deal**: Deals represent ongoing, lost or won sales to an Organization or to a Person.
* **Lead**: Leads are potential deals stored in Leads Inbox before they are archived or converted to a deal.
* **Pipeline**: Represent your sales process(es).
* **Stage**: Steps in your pipeline that signify to your sales team that an opportunity is moving toward the point of closing.
* **Deal Stage History**: Deal stage history represent the history of each deal progress towards a lost or won sale.
* **Organization**: Organizations are companies and other kinds of organizations you are making Deals with.
* **User**: Users are people with access to your Pipedrive account.

[You can find the relationship between all those objects here.](https://docs.google.com/presentation/d/1PybGmYx0qB9scRD3boXwLL6EOaPxX_cOrp9wOHTlH5I/edit?usp=sharing)

{% embed url="<https://docs.google.com/presentation/d/1PybGmYx0qB9scRD3boXwLL6EOaPxX_cOrp9wOHTlH5I/edit?usp=sharing>" %}


---

# 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 dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.whaly.io/connectors/source-catalog/sales-crms/pipedrive.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.