Pipedrive CRM

The widest connection in this catalogue: forty-three tools across the whole CRM, so an assistant can read a customer’s history and then record what happens next without leaving the conversation.

What it is

Pipedrive is a sales CRM. This integration connects over OAuth2 and covers organisations, people, deals, activities, email threads and projects — reading them, and in many cases writing them.

It is one of the few integrations here that changes data in a customer system, which is what makes the permissions section below the important part of this page.

Use it for

• “Summarise this meeting transcript and create the follow-up activities it implies.”
• “What is the full history with this organisation — deals, notes, activities and email?”
• “Which projects are incomplete, and which have duplicates?”
• “How long did it take this organisation to reach value?”
• “Find this person, update their details and log a note.”

Tools

Forty-three tools across six areas:

Area	Answers
Usage guide	How the areas relate and which identifier to search on — the assistant reads this first
Organisations	Search, overview, notes, deals, people, emails and activities for a company; create and update
People	Search, get, create and update a contact
Deals	Search, get, notes, activities, emails, email threads, and update
Activities	Filters, filtered lists, get, update, add, activity types, and per-user activity
Projects	Fields, get, notes, list by organisation, search, create, update, set live, time-to-value, duplicate check and incomplete-project check

Data and permissions

• OAuth2 against your own Pipedrive. The connection acts within whatever the authorised account can see and do.
• It writes. Eleven of the forty-three tools create or change data: organisations, people, deals, activities, notes and projects.
• Writes are not individually confirmed. Unlike the Google Drive connection, which stops and asks before each change, Pipedrive’s write tools execute when the assistant calls them. Control this through who may use the assistant and what the Pipedrive account is permitted to do — not through a per-action prompt, because there isn’t one.

Getting started

Authorise the integration against your Pipedrive account over OAuth2. Scope the account deliberately: a read-only Pipedrive user makes the whole connection read-only, which is the right starting point if you are not yet ready for an assistant to write.

Limitations

• No per-action consent gate on writes. Worth saying twice, because it is the thing most likely to surprise. An instruction that sounds like a question — “should we create a deal for this?” — can be acted on.
• Nothing is deleted, but an update overwrites, and the previous value is not kept by the integration.
• Scoped to one account’s visibility. What the assistant cannot see, it cannot report — and an incomplete answer looks the same as a complete one.
• Rate limits are Pipedrive’s. A very broad sweep across a large account can be throttled upstream.