# Pipedrive: how to read it into Maplith

*CRM · also known as Pipedrive CRM · last checked 2026-10-08 · recipe `maplith://systems/pipedrive`*

Pipedrive holds the company's deals and pipelines, the people and organisations behind them, the activities that move them, and the products sold on each deal.

## Best path

**Recommended: export files.** A global admin can export every data type from Pipedrive as CSV in a few clicks, which gives the full history at once. Pipedrive's official MCP server is still labelled beta, can also create and update records, and has no documented read-only mode, so it suits a quick check rather than the main intake.

Try the paths in this order (ADR-0031):

1. **Your agent fetches it**, with the access your human already gave you. Connectors a vendor or client page confirms: Pipedrive MCP BETA added as a custom connector in Claude; Pipedrive MCP BETA added as an app in ChatGPT (developer mode). If the customer has already connected Pipedrive MCP, the agent can read the fields and recent deals, people, organisations and activities with the access its user already has. It only reads; it should not use the tools that create or update records.
2. **Maplith reads an MCP server your human already has.** Official: **Pipedrive MCP server (Pipedrive MCP BETA)**. Endpoint to connect to: `https://mcp.pipedrive.ai/mcp`. Documentation (a page to read, not an address to connect to): https://www.pipedrive.com/en/features/mcp-server. Access: There is no read-only token. A person signs in to Pipedrive and approves the requested permissions; the server can then see and do what that Pipedrive user can, so connect with a user whose permission set and visibility group are limited. Labelled beta in Pipedrive's setup guides. It can also create and update records and convert leads into deals, and use counts against plan-based limits. Maplith cannot read this server: it offers tools or a personal sign-in to an agent, not resources Maplith reads. Maplith reads only a server that serves MCP resources and takes a token a person types under Data sources › Systems in the Maplith app, such as the customer-run template for a database (ADR-0028). Your human can connect this server to you instead, as path 1.
3. **Export files**, the fallback that always works: see *Export steps* below.

## Datasets that make a good map

| Dataset | One row is | Key columns | Joins to |
|---|---|---|---|
| Deals | One sales opportunity in a pipeline stage. | deal id, pipeline, stage, value, status (open, won, lost), expected close date, person id, organization id, owner | People and organisations by their ids; invoices in the accounting system by a deal or order reference, if the company records one. |
| People | One contact person. | person id, email (Maplith tries to mask it), organization id, owner | Webshop customers, helpdesk tickets and newsletter lists by email; organisations by organization id. |
| Organizations | One customer or prospect company. | organization id, name, address, VAT or CVR number (only if the company added that custom field), owner | Accounting customers by VAT or CVR number or by name; people and deals by organization id. |
| Activities | One call, meeting, task, email or other planned or done activity. | activity id, type, due date, done, deal id, person id, organization id, assigned user | Deals, people and organisations by their ids; shows how fast deals are followed up. |
| Products and deal products | One product in the catalogue, or one product line attached to a deal. | product id, product code, deal id, quantity, item price | Deals by deal id; webshop and accounting products by product code or SKU. |
| Leads | One lead in the Leads Inbox before it becomes a deal. | lead id, person id, organization id, source, owner, created date | People and organisations by their ids; deals once the lead is converted. |

Columns are named, never their values. Maplith tries to mask personal data such as email addresses, but that is best effort: your human decides what goes in.

## Read-only access

**Who usually has the rights:** A global admin, often the owner or the sales lead. Only global admins can use Export data; regular users can export from list views if their permission set allows it.

**For the key your own agent's client uses, choose only these read permissions:** `base`, `deals:read`, `contacts:read`, `activities:read`, `products:read`, `leads:read`, `users:read`

**Where to click:**

1. For export files: open the account menu at the top right, then Tools and apps, then Export data
2. For an app or integration: approve only the read scopes listed here when Pipedrive asks
3. Do not hand out the personal API token under Settings, Personal preferences, API: it has all of your own rights, it is not read-only, and Maplith never asks for it

A key or token made here stays in the tool that reads the system for your human, never in a chat. Maplith asks for one only under Data sources › Systems in the app, and only for an MCP server it can read.

## Export steps

**Format:** CSV · **Date range:** All records; deals and activities from the last 12 months are enough for a first map

1. Open the account menu at the top right and choose Tools and apps, then Export data
2. Pick a data type: Deals, People, Organizations, Activities, Products or Leads
3. Choose CSV as the format and click Export
4. Download the file from Generated exports with the cloud icon in the Available until column
5. Repeat for each data type; activities and notes are exported separately from deals
6. Without admin rights: open a list view, pick the columns with the gear icon, then click the three dots and Export filter results

## Volume hint

**About 20–300 new deals; 100–1,500 activities a month** (an estimate). Estimate for a small company, not a measured figure: a few sales people, each logging several activities per deal.

Every row an agent reads passes through its context, about one token per four characters. Above a few thousand rows a dataset, or for a daily refresh, prefer an MCP server or an export over fetching through the chat.

## Always

- Read-only, and never a credential sent to Maplith through the chat.
- The same recent period, a few months, from every system.
- Your human decides what goes in.

## Sources

Written from the vendor's public documentation, last checked 2026-10-08:

- https://support.pipedrive.com/en/article/mcp-claude
- https://support.pipedrive.com/en/article/mcp-chatgpt
- https://www.pipedrive.com/en/features/mcp-server
- https://support.pipedrive.com/en/article/exporting-data-from-pipedrive
- https://support.pipedrive.com/en/article/how-can-i-find-my-personal-api-key
- https://pipedrive.readme.io/docs/marketplace-scopes-and-permissions-explanations