Claude Pipedrive connectorWhat Claude can do in your Pipedrive account.
The Claude Pipedrive connector exposes 32 tools. 19 read deals, leads, contacts, activities and notes, and 13 add or edit records, including turning a lead into a deal. Here: what each tool does, what you approve, and where it stops.
Verified Trustpilot reviews · AI, automation & growth agency
What changes when Claude can reach your Pipedrive
The CRM stops being the last tab you open after a call. You tell Claude what happened in plain words, and it reads the right deal, contact or lead in Pipedrive while it answers, then logs the follow-up where your team expects it. It works inside your own Pipedrive permissions, and Pipedrive records every action in its change log.
From call notes to a clean record. Paste your notes after a discovery call: addPerson and addOrganization create the contact and the company, addDeal opens the deal, addNote pins the notes to it and addActivity books the follow-up call.
Move the pipeline without clicking. A prospect asked for a proposal: updateDeal edits the deal, updateActivity updates the call you had booked, and convertLeadToDeal promotes a warm lead into a real opportunity.
Ask instead of filtering. getDeals, searchDeals and getStages answer questions like which open deals sit in the proposal stage, and searchPersons finds a contact by name or email in seconds.
Now what the directory sheet does not tell you. Pipedrive's own tool list also names five product tools that the sheet leaves out, and Pipedrive's setup article describes a custom connector rather than the directory entry. Nothing on this list deletes a record. And nothing runs on its own: no tool starts when a deal goes stale. For that kind of background job, an automation tool is the right trade, and the Integrations hub gathers that side.
The vocabulary in one minute
Five words you will meet while plugging Pipedrive into Claude.
- Connector
- The link you set up once between Claude and an account you already own, so Claude can work in that account while it answers you.
- Tool
- One named action a connector opens to Claude. It picks the ones it needs by itself, and the directory sheet lists them by name.
- Authorization
- The sign-in screen of the service itself, where you hand Claude the access it will use. Granted once per person, and you can take it back.
- Approval
- The confirmation Claude waits for before it goes through with something that changes your account, shown in the chat when it matters.
- MCP
- The shared standard connectors are built on. It is what lets an assistant like Claude talk to an outside service such as your CRM.
Connect Pipedrive to Claude in three steps
- 01
Find Pipedrive in Claude
In Claude, open Customize, then Connectors, and look for Pipedrive in the list. On a Team or Enterprise workspace, an Owner or Primary Owner has to switch the connector on first, before each member can sign in.
- 02
Start the connection
Click Connect on the Pipedrive row, then sign in to Pipedrive in the window Pipedrive opens itself. If the link ever breaks, use Disconnect and connect again from the same place.
- 03
Read the authorization screen
Review the permissions on Pipedrive's authorization screen before you accept them. The screen belongs to Pipedrive, not to Claude, and it sets what the access covers. You can take it back later from your Pipedrive account.
The 32 Claude Pipedrive connector tools, by what they do
Pipedrive gives Claude 32 tools: 19 that read your account, 13 that change something in it.
Two groups: what Claude reads and what it can add or edit. Every tool on the sheet is described by Pipedrive's own tool list. Names stay exactly as Claude shows them.
- 19 read
- 13 write
What Claude reads (19)
19 toolsNineteen tools that fetch or search your CRM records without touching them.
getActivities
Pulls a list of your activities, the calls, meetings and tasks on your calendar, so Claude can tell you what is coming up or overdue.
getActivity
Opens a single activity with the details Pipedrive holds on it, rather than the whole list.
getDeal
Brings back the record of one specific deal, so Claude answers from the real data rather than from memory.
getDeals
Lists deals from your pipeline, which lets Claude sort, count or summarise them for you in the chat.
getLeadConversionStatus
Checks whether a lead has already been converted, and if so, which deal it became.
getNote
Reads one note in full, wherever it is attached in the CRM.
getNotes
Returns the list of notes in your account, so Claude can scan what the team wrote about a customer over time.
getOrganization
Displays the record of one company, with the details your team keeps on it.
getOrganizations
Lists the companies stored in Pipedrive so Claude can group or filter them in its answer.
getPerson
Retrieves one specific contact's record, as your CRM holds it.
getPersons
Returns a list of contacts, the people stored in your CRM, for Claude to sift through.
getStage
Shows the details of one specific stage of a pipeline.
getStages
Fetches every stage of a pipeline, giving Claude the map of your sales process.
searchDeals
Finds deals by keyword, handy when you remember a word from the title rather than the exact deal.
searchLeads
Looks for leads by keyword or criteria in your leads inbox, the prospects not yet turned into deals.
searchOrganization
Hunts for companies by name or keyword across your organizations.
searchPersons
Tracks down contacts by name, email or other criteria, the fastest way to reach one person's record.
getLeads
Returns your list of leads so Claude can summarise the state of your prospecting.
getLead
Displays one lead record with the information captured so far.
What Claude can add or edit (13)
13 toolsThirteen tools that add records, edit them or convert a lead. No source describes a confirmation of their own: the general rule below applies.
addActivity
Approval: see the ruleCreates a new activity in Pipedrive: a call, a meeting or a task, attached where it belongs.
addDeal
Approval: see the ruleAdds a new deal to your pipeline for a prospect who is ready for it.
addNote
Approval: see the ruleWrites a note and attaches it to a deal, a lead, a contact or an organization.
addOrganization
Approval: see the ruleRegisters a new organization in Pipedrive, ready for contacts and deals to link to.
addPerson
Approval: see the ruleSaves a new person in your CRM, with the details you give Claude.
convertLeadToDeal
Approval: see the ruleTurns a lead into a deal, the moment a prospect becomes a real opportunity in your pipeline.
updateActivity
Approval: see the ruleEdits an existing activity with what has changed since it was booked.
updateDeal
Approval: see the ruleApplies the changes you describe to a deal that already exists in your pipeline.
updateNote
Approval: see the ruleRewrites a specific note, identified by its ID.
updateOrganization
Approval: see the ruleUpdates an existing organization's record with new information.
updatePerson
Approval: see the ruleCorrects or completes an existing person's record in Pipedrive.
addLead
Approval: see the ruleLogs a fresh lead, a prospect that is not a deal yet.
updateLead
Approval: see the ruleModifies an existing lead record with fresh information.
What Claude asks you before it acts
By default, Claude stops and asks for your go-ahead before each action it takes on an account for you. The request shows up in the chat, at the moment it matters.
On Team and Enterprise workspaces, owners decide whether members may let some actions through without being asked every time. They can also limit what a connector may do across the whole organization, for example keep reading open and close writing. That setting applies to everyone and nobody overrides it from their own account. And Claude works with your rights and nothing more: Pipedrive states that it inherits your role and visibility settings, so a deal you cannot see stays out of reach.
Which plans it is available on
Out of the 819 sheets in the official directory, not one shows availability by plan. The per-connector answer is published nowhere: it is a real hole in the catalogue.
The general rule is published, though. Remote connectors are open to all users on Claude, Cowork, Claude Desktop and mobile. On Team and Enterprise, an Owner or Primary Owner switches the connector on for the organization before each member can connect. On Pipedrive's side, two of its own texts disagree about which Pipedrive subscriptions qualify; the limits section sets them side by side. For the current state on your account, check the connector's sheet in the official directory.
Where the Claude Pipedrive connector stops
A connector is not an automation. Claude calls these tools while it answers you: nothing starts when a deal goes quiet, a lead lands or an activity falls overdue.
This page rests on Pipedrive's own material only: no Claude help article covers this connector. The tool list is an observed floor, not a promise, since an admin can open actions that no public sheet shows. The directory's partner badge is not a security audit either, and Anthropic says so on every sheet: it does not pick the tools a publisher exposes and does not vouch that they behave as announced. Connect what comes from a publisher you trust, here Pipedrive itself. For a connector where two official sources clash over what it can send, read the Claude gmail connector.
Which Pipedrive subscriptions does the connector work with?
- Connector sheet in Claude's directory, publisher description ↗read 30 September 2026The description written by Pipedrive says the connector is available on all paid Pipedrive plans.
- Pipedrive's MCP page, FAQ ↗read 30 September 2026Pipedrive's FAQ says every Pipedrive customer can use it, on every plan, with usage capped by token limits tied to the plan.
What this page followsBoth texts come from Pipedrive and concern Pipedrive subscriptions, not Claude plans. One says paid plans, the other says all plans, and neither carries a date precise enough to settle it. Ask Pipedrive about your subscription, and check the directory sheet from your own Claude account.
Need help connecting Pipedrive to Claude?
A person reads every message.
