Docs: System guides
Read Pipedrive into Maplith
On this page
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:
- Your agent fetches it, with the access you already gave it. 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 you have already connected Pipedrive MCP, the agent can read the fields and recent deals, people, organisations and activities with the access you already gave it. It only reads; it should not use the tools that create or update records.
- Maplith reads an MCP server you already run. Pipedrive runs Pipedrive MCP server (Pipedrive MCP BETA). Its address is
https://mcp.pipedrive.ai/mcp. Documentation: www.pipedrive.com. 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 itself, because it offers tools or a personal sign-in to an agent. Connect it to your agent instead, as the first path. - Export files, the fallback that always works. See the 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: you decide what goes in.
The access to give
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.
Choose the narrowest access that covers the data:
- base
deals:readcontacts:readactivities:readproducts:readleads:readusers:read
Where to click:
- For export files: open the account menu at the top right, then Tools and apps, then Export data
- For an app or integration: approve only the read scopes listed here when Pipedrive asks
- 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, never in a chat. Maplith asks for one only under Data sources › Systems in the app.
Export steps
Format: CSV Date range: All records; deals and activities from the last 12 months are enough for a first map
- Open the account menu at the top right and choose Tools and apps, then Export data
- Pick a data type: Deals, People, Organizations, Activities, Products or Leads
- Choose CSV as the format and click Export
- Download the file from Generated exports with the cloud icon in the Available until column
- Repeat for each data type; activities and notes are exported separately from deals
- Without admin rights: open a list view, pick the columns with the gear icon, then click the three dots and Export filter results
How much data
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.
An agent that reads rows through a chat reads every one of them, about one token per four characters. Above a few thousand rows a dataset, or for a daily refresh, an MCP server or an export is the better path.
Always
- Read-only, and never a credential sent to Maplith through a chat.
- The same recent period, a few months, from every system.
- You decide what goes in.
Sources
Written from public documentation, last checked 2026-10-08: