How to
How to connect Claude to Pipedrive
Claude can summarize your pipeline from a read-leaning connection, but the CRM upkeep still lands on you. A custom connector lets Claude create the deal, log the call, and update the fields from the same conversation.
Connect Claude to Pipedrive through a custom MCP connector that authenticates as your own Pipedrive account over OAuth. Claude then reads deals, contacts, and activities freely, and uses scoped write tools to create deals, log activities, and update fields. Closing moves and deletions stay gated behind a confirmation you approve every time.
Key takeaways
- A custom connector gives Claude write tools for Pipedrive, so it creates deals and logs activities instead of only reporting on them.
- Reading the pipeline flows freely, while marking a deal won or lost and deleting records wait for your approval.
- The connector authenticates as your account over OAuth and inherits your existing Pipedrive permissions, never more.
- It covers your real setup, including custom pipelines, stages, and fields, not a generic slice of the API.
Can Claude connect to Pipedrive out of the box?
Partly. The Pipedrive connection available to Claude today tends to be read-leaning or covers a thin slice of the API, so Claude can surface deals and contacts but often cannot reliably create or move them. Full read-write, where Claude creates deals and logs activities with approvals, comes from a custom connector.
Reading is genuinely useful. Claude can answer questions about your pipeline, summarize open deals, and pull up a contact's history. The limit shows up the moment you ask it to act: create this deal, log that call, move this to the next stage. A read-leaning connection runs out exactly where the work starts.
A custom MCP connector closes that gap with scoped write actions like creating deals, logging activities, and updating fields, each with human-in-the-loop controls on the risky ones.
The wider pattern holds beyond this one tool: in our June 2026 review of 264 business tools, 77 percent had no Claude connector at all, and none shipped full read-write out of the box.
How do I connect Claude to Pipedrive with write access?
You connect Claude to Pipedrive by having a custom MCP connector built against the Pipedrive API, authenticated as your own account over OAuth with the narrowest scopes the work needs. Once it is added to Claude, you ask for CRM work in plain language and approve the gated actions.
The setup runs like this:
- 1Tell us which Pipedrive work Claude should handle: creating deals, logging activities, updating people and organizations.
- 2We build a small MCP server against the Pipedrive API, with read tools like
search_dealsseparated from write tools likecreate_dealandlog_activity. - 3You authenticate the connector as your own Pipedrive account over OAuth, so it inherits exactly your permissions and visibility.
- 4Claude starts doing the work in your conversations, with closing moves and deletions gated behind your confirmation.
From then on, CRM upkeep happens inline. You talk through a call with Claude, and it logs the activity, updates the deal value, and adds the note without you switching tabs.
What can Claude do in Pipedrive with full read-write access?
With full read-write access, Claude can create a deal in the right pipeline and stage with its value and owner, add or update people and organizations, log calls and meetings as activities, move deals forward, and attach notes. It can also find open deals matching a filter and propose follow-up activities.
The write tools map to the work sales teams actually defer:
create_dealputs a new deal in the right pipeline and stage, with value and owner set.log_activityrecords a call, meeting, or email against the deal it belongs to.update_personadds or updates a contact and links them to an organization.add_noteattaches a summary of a conversation to a deal or contact.update_dealadvances a stage or changes fields, with won and lost changes held for your approval.
Because the connector is built for your account, it works with your custom pipelines, stages, and fields, not a generic default set.
Will Claude mark a deal won or lost without my approval?
No. Stage changes that close a deal, along with deleting a record, are gated write actions. Claude prepares the update and shows you exactly what will change, and it only applies after you confirm. You decide which actions run automatically and which require that confirmation step.
The line between automatic and gated is yours to set. Most teams let reads, notes, and activity logging flow freely, and keep closing moves and deletions behind a confirmation. That keeps the fast part fast and the irreversible part deliberate.
Claude never outranks your account
The connector authenticates as you through OAuth and inherits your existing permissions. If a pipeline, deal, or contact is hidden from you in Pipedrive, it stays hidden from Claude.
Is a custom Pipedrive connector safe for my CRM data?
Yes, when it is scoped properly. The connector uses OAuth with the narrowest scopes the work needs, keeps read and write tools separate, and gates destructive actions like deleting a record or marking a deal lost behind your confirmation. Claude only ever has the access your own Pipedrive account already has.
Nothing about the connector expands your CRM's attack surface beyond your own login. It acts as you, sees what you see, and stops where your permissions stop. The additional control is the approval gate, which your manual work never had.