How do AI agents use Pipedrive through Open Connector?

Your user connects Pipedrive once with one of its cataloged authentication methods. Open Connector stores the credential in an encrypted vault and exposes Pipedrive tools to your agent over MCP or a typed API, with credentials injected server-side on each call.

Is this a Pipedrive MCP server?

Yes. Open Connector can serve Pipedrive as a named MCP server with a scoped allowlist and a per-user connection URL, so any MCP client can call Pipedrive actions with credentials injected server-side.

Where do Pipedrive credentials live?

In your own infrastructure. Open Connector keeps credentials in its own vault and injects them at call time, so they never leave your environment.

Pipedrive integration

Pipedrive integration for AI agents.

Pipedrive integration for AI agents with secure authentication and server-side credential injection. Open Connector runs the OAuth, seals the token in an encrypted vault, and serves Pipedrive tools to your agent over MCP or a typed API — credentials injected server-side, every call audited, nothing leaving your infrastructure. Open source (AGPL-3.0) and self-hostable.

View source on GitHub All integrations →

What your agents can do

Real Pipedrive actions, managed and audited.

Your user connects Pipedrive once; your agent can then use Pipedrive API to manage CRM deals, leads, people, organizations, activities, products, projects, pipelines, stages, users, and search — scoped to the OAuth permissions you grant and the tool allowlist you configure. Every action is least-privilege and written to a tamper-evident audit trail.

1
Your user grants Pipedrive access once (OAuth) — the token lands in the vault.
2
Your agent calls a tool over MCP or the typed API; Open Connector injects the credential server-side.
3
Every routed call appends a hash-chained audit record — nothing leaves your infra.

Tools & triggers

Supported Pipedrive tools.

213 tools are generated from the published Pipedrive catalog. Descriptions are plain text; each action remains subject to its configured authentication and tool allowlist.

Showing 213 tools. All published catalog entries are included in this page's server-rendered HTML.

Add new activity type: Adds a new activity type.; ActivityTypes
Add a call log: Adds a new call log.; CallLogs
Attach an audio file to the call log: Adds an audio recording to the call log. That audio can be played by those who have access to the call log object.; CallLogs
Add a channel: Adds a new messaging channel, only admins are able to register new channels. It will use the getConversations endpoint to fetch conversations, participants and messages afterward. To use the endpoint, you need to have **Messengers integration** OAuth scope enabled and the Messaging manifest ready for the [Messaging app extension](https://pipedrive.readme.io/docs/messaging-app-extension).; Channels
Add a new deal field: Adds a new deal field. For more information, see the tutorial for <a href="https://pipedrive.readme.io/docs/adding-a-new-custom-field" target="_blank" rel="noopener noreferrer">adding a new custom field</a>.; DealFields
Add a follower to a deal: Adds a follower to a deal.; Deals
Add a participant to a deal: Adds a participant to a deal.; Deals
Add file: Lets you upload a file and associate it with a deal, person, organization, activity, product or lead. For more information, see the tutorial for <a href="https://pipedrive.readme.io/docs/adding-a-file" target="_blank" rel="noopener noreferrer">adding a file</a>.; Files
Create a remote file and link it to an item: Creates a new empty file in the remote location (`googledrive`) that will be linked to the item you supply. For more information, see the tutorial for <a href="https://pipedrive.readme.io/docs/adding-a-remote-file" target="_blank" rel="noopener noreferrer">adding a remote file</a>.; Files
Add a new filter: Adds a new filter, returns the ID upon success. Note that in the conditions JSON object only one first-level condition group is supported, and it must be glued with 'AND', and only two second level condition groups are supported of which one must be glued with 'AND' and the second with 'OR'. Other combinations do not work (yet) but the syntax supports introducing them in future. For more information, see the tutorial for <a href="https://pipedrive.readme.io/docs/adding-a-filter" target="_blank" rel="noopener noreferrer">adding a filter</a>.; Filters
Add a new goal: Adds a new goal. Along with adding a new goal, a report is created to track the progress of your goal.; Goals
Add a lead: Creates a lead. A lead always has to be linked to a person or an organization or both. All leads created through the Pipedrive API will have a lead source and origin set to `API`. Here's the tutorial for <a href="https://pipedrive.readme.io/docs/adding-a-lead" target="_blank" rel="noopener noreferrer">adding a lead</a>. If a lead contains custom fields, the fields' values will be included in the response in the same format as with the `Deals` endpoints. If a custom field's value hasn't been set for the lead, it won't appear in the response. Please note that leads do not have a separate set of custom fields, instead they inherit the custom fields' structure from deals. See an example given in the <a href="https://pipedrive.readme.io/docs/updating-custom-field-value" target="_blank" rel="noopener noreferrer">updating custom fields' values tutorial</a>.; Leads
Add a lead label: Creates a lead label.; LeadLabels
Add a note: Adds a new note.; Notes
Add a comment to a note: Adds a new comment to a note.; Notes
Add or update role setting: Adds or updates the visibility setting for a role.; Roles
Add a new organization field: Adds a new organization field. For more information, see the tutorial for <a href="https://pipedrive.readme.io/docs/adding-a-new-custom-field" target="_blank" rel="noopener noreferrer">adding a new custom field</a>.; OrganizationFields
Add a follower to an organization: Adds a follower to an organization.; Organizations
Create an organization relationship: Creates and returns an organization relationship.; OrganizationRelationships
Add a new person field: Adds a new person field. For more information, see the tutorial for <a href="https://pipedrive.readme.io/docs/adding-a-new-custom-field" target="_blank" rel="noopener noreferrer">adding a new custom field</a>.; PersonFields
Add a follower to a person: Adds a follower to a person.; Persons
Add person picture: Adds a picture to a person. If a picture is already set, the old picture will be replaced. Added image (or the cropping parameters supplied with the request) should have an equal width and height and should be at least 128 pixels. GIF, JPG and PNG are accepted. All added images will be resized to 128 and 512 pixel wide squares.; Persons
Add a new product field: Adds a new product field. For more information, see the tutorial for <a href="https://pipedrive.readme.io/docs/adding-a-new-custom-field" target="_blank" rel="noopener noreferrer">adding a new custom field</a>.; ProductFields
Add a follower to a product: Adds a follower to a product.; Products
Add a project: Adds a new project. Note that you can supply additional custom fields along with the request that are not described here. These custom fields are different for each Pipedrive account and can be recognized by long hashes as keys.; Projects
Add a role: Adds a new role.; Roles
Add role assignment: Assigns a user to a role.; Roles
Add a task: Adds a new task.; Tasks
Add a new team: Adds a new team to the company and returns the created object.; LegacyTeams
Add users to a team: Adds users to an existing team.; LegacyTeams
Add a new user: Adds a new user to the company, returns the ID upon success.; Users
Create a new Webhook: Creates a new Webhook and returns its details. Note that specifying an event which triggers the Webhook combines 2 parameters - `event_action` and `event_object`. E.g., use `*.*` for getting notifications about all events, `create.deal` for any newly added deals, `delete.persons` for any deleted persons, etc. See <a href="https://pipedrive.readme.io/docs/guide-for-webhooks-v2?ref=api_reference" target="_blank" rel="noopener noreferrer">the guide for Webhooks</a> for more details.; Webhooks
Archive a project: Archives a project.; Projects
Requesting authorization: Authorize a user by redirecting them to the Pipedrive OAuth authorization page and request their permissions to act on their behalf. This step is necessary to implement only when you allow app installation outside of the Marketplace.; Oauth
Delete an activity type: Marks an activity type as deleted.; ActivityTypes
Delete a call log: Deletes a call log. If there is an audio recording attached to it, it will also be deleted. The related activity will not be removed by this request. If you want to remove the related activities, please use the endpoint which is specific for activities.; CallLogs
Delete a channel: Deletes an existing messenger’s channel and all related entities (conversations and messages). To use the endpoint, you need to have **Messengers integration** OAuth scope enabled and the Messaging manifest ready for the [Messaging app extension](https://pipedrive.readme.io/docs/messaging-app-extension).; Channels
Delete a comment related to a note: Deletes a comment.; Notes
Delete a conversation: Deletes an existing conversation. To use the endpoint, you need to have **Messengers integration** OAuth scope enabled and the Messaging manifest ready for the [Messaging app extension](https://pipedrive.readme.io/docs/messaging-app-extension).; Channels
Delete a deal field: Marks a field as deleted. For more information, see the tutorial for <a href="https://pipedrive.readme.io/docs/deleting-a-custom-field" target="_blank" rel="noopener noreferrer">deleting a custom field</a>.; DealFields
Delete multiple deal fields in bulk: Marks multiple deal fields as deleted.; DealFields
Delete a follower from a deal: Deletes a follower from a deal.; Deals
Delete a participant from a deal: Deletes a participant from a deal.; Deals
Delete a file: Marks a file as deleted. After 30 days, the file will be permanently deleted.; Files
Delete a filter: Marks a filter as deleted.; Filters
Delete multiple filters in bulk: Marks multiple filters as deleted.; Filters
Delete existing goal: Marks a goal as deleted.; Goals
Delete a lead: Deletes a specific lead.; Leads
Delete a lead label: Deletes a specific lead label.; LeadLabels
Delete mail thread: Marks a mail thread as deleted.; Mailbox
Delete a note: Deletes a specific note.; Notes
Delete an organization field: Marks a field as deleted. For more information, see the tutorial for <a href="https://pipedrive.readme.io/docs/deleting-a-custom-field" target="_blank" rel="noopener noreferrer">deleting a custom field</a>.; OrganizationFields
Delete multiple organization fields in bulk: Marks multiple fields as deleted.; OrganizationFields
Delete a follower from an organization: Deletes a follower from an organization. You can retrieve the `follower_id` from the <a href="https://developers.pipedrive.com/docs/api/v1/Organizations#getOrganizationFollowers">List followers of an organization</a> endpoint.; Organizations
Delete an organization relationship: Deletes an organization relationship and returns the deleted ID.; OrganizationRelationships
Delete a person field: Marks a field as deleted. For more information, see the tutorial for <a href="https://pipedrive.readme.io/docs/deleting-a-custom-field" target="_blank" rel="noopener noreferrer">deleting a custom field</a>.; PersonFields
Delete multiple person fields in bulk: Marks multiple fields as deleted.; PersonFields
Delete a follower from a person: Deletes a follower from a person.; Persons
Delete person picture: Deletes a person’s picture.; Persons
Delete a product field: Marks a product field as deleted. For more information, see the tutorial for <a href="https://pipedrive.readme.io/docs/deleting-a-custom-field" target="_blank" rel="noopener noreferrer">deleting a custom field</a>.; ProductFields
Delete multiple product fields in bulk: Marks multiple fields as deleted.; ProductFields
Delete a follower from a product: Deletes a follower from a product.; Products
Delete a project: Marks a project as deleted.; Projects
Delete a role: Marks a role as deleted.; Roles
Delete a role assignment: Removes the assigned user from a role and adds to the default role.; Roles
Delete a task: Marks a task as deleted. If the task has subtasks then those will also be deleted.; Tasks
Delete users from a team: Deletes users from an existing team.; LegacyTeams
Delete the link between a user and the installed video call integration: A video calling provider must call this endpoint to remove the link between a user and the installed video calling app.; Meetings
Delete existing Webhook: Deletes the specified Webhook.; Webhooks
Download one file: Initializes a file download.; Files
Duplicate deal: Duplicates a deal.; Deals
Find users by name: Finds users by their name.; Users
Get all activity fields: Returns all activity fields.; ActivityFields
Get all activity types: Returns all activity types.; ActivityTypes
Get all archived deals: Returns all archived deals.; Deals
Get archived deals summary: Returns a summary of all archived deals.; Deals
Get archived deals timeline: Returns archived open and won deals, grouped by a defined interval of time set in a date-type dealField (`field_key`) — e.g. when month is the chosen interval, and 3 months are asked starting from January 1st, 2012, deals are returned grouped into 3 groups — January, February and March — based on the value of the given `field_key`.; Deals
Get all archived leads: Returns multiple archived leads. Leads are sorted by the time they were created, from oldest to newest. Pagination can be controlled using `limit` and `start` query parameters. If a lead contains custom fields, the fields' values will be included in the response in the same format as with the `Deals` endpoints. If a custom field's value hasn't been set for the lead, it won't appear in the response. Please note that leads do not have a separate set of custom fields, instead they inherit the custom fields' structure from deals.; Leads
Get details of a call log: Returns details of a specific call log.; CallLogs
Get one comment: Returns the details of a comment.; Notes
Get all add-ons for a single company: Returns the add-ons for a single company.; Billing
Get all supported currencies: Returns all supported currencies in given account which should be used when saving monetary values with other objects. The `code` parameter of the returning objects is the currency code according to ISO 4217 for all non-custom currencies.; Currencies
Get current user data: Returns data about an authorized user within the company with bound company data: company ID, company name, and domain. Note that the `locale` property means 'Date/number format' in the Pipedrive account settings, not the chosen language.; Users
List updates about deal field values: Lists updates about field values of a deal.; Deals
Get one deal field: Returns data about a specific deal field.; DealFields
Get all deal fields: Returns data about all deal fields.; DealFields
List files attached to a deal: Lists files associated with a deal.; Deals
List followers of a deal: Lists the followers of a deal.; Deals
List mail messages associated with a deal: Lists mail messages associated with a deal.; Deals
List participants of a deal: Lists the participants associated with a deal. If a company uses the [Campaigns product](https://pipedrive.readme.io/docs/campaigns-in-pipedrive-api), then this endpoint will also return the `data.marketing_status` field.; Deals
List updates about participants of a deal: List updates about participants of a deal. This is a cursor-paginated endpoint. For more information, please refer to our documentation on <a href="https://pipedrive.readme.io/docs/core-api-concepts-pagination" target="_blank" rel="noopener noreferrer">pagination</a>.; Deals
List updates about a deal: Lists updates about a deal.; Deals
List permitted users: Lists the users permitted to access a deal.; Deals
Get deals summary: Returns a summary of all not archived deals.; Deals
Get deals timeline: Returns not archived open and won deals, grouped by a defined interval of time set in a date-type dealField (`field_key`) — e.g. when month is the chosen interval, and 3 months are asked starting from January 1st, 2012, deals are returned grouped into 3 groups — January, February and March — based on the value of the given `field_key`.; Deals
Get one file: Returns data about a specific file.; Files
Get all files: Returns data about all files.; Files
Get one filter: Returns data about a specific filter. Note that this also returns the condition lines of the filter.; Filters
Get all filter helpers: Returns all supported filter helpers. It helps to know what conditions and helpers are available when you want to <a href="/docs/api/v1/Filters#addFilter">add</a> or <a href="/docs/api/v1/Filters#updateFilter">update</a> filters. For more information, see the tutorial for <a href="https://pipedrive.readme.io/docs/adding-a-filter" target="_blank" rel="noopener noreferrer">adding a filter</a>.; Filters
Get all filters: Returns data about all filters.; Filters
Get result of a goal: Gets the progress of a goal for the specified period.; Goals
Find goals: Returns data about goals based on criteria. For searching, append `{searchField}={searchValue}` to the URL, where `searchField` can be any one of the lowest-level fields in dot-notation (e.g. `type.params.pipeline_id`; `title`). `searchValue` should be the value you are looking for on that field. Additionally, `is_active=<true|false>` can be provided to search for only active/inactive goals. When providing `period.start`, `period.end` must also be provided and vice versa.; Goals
Get one lead: Returns details of a specific lead. If a lead contains custom fields, the fields' values will be included in the response in the same format as with the `Deals` endpoints. If a custom field's value hasn't been set for the lead, it won't appear in the response. Please note that leads do not have a separate set of custom fields, instead they inherit the custom fields’ structure from deals.; Leads
Get all lead fields: Returns data about all lead fields.; LeadFields
Get all lead labels: Returns details of all lead labels. This endpoint does not support pagination and all labels are always returned.; LeadLabels
Get all lead sources: Returns all lead sources. Please note that the list of lead sources is fixed, it cannot be modified. All leads created through the Pipedrive API will have a lead source `API` assigned.; LeadSources
List permitted users: Lists the users permitted to access a lead.; Leads
Get all leads: Returns multiple not archived leads. Leads are sorted by the time they were created, from oldest to newest. Pagination can be controlled using `limit` and `start` query parameters. If a lead contains custom fields, the fields' values will be included in the response in the same format as with the `Deals` endpoints. If a custom field's value hasn't been set for the lead, it won't appear in the response. Please note that leads do not have a separate set of custom fields, instead they inherit the custom fields' structure from deals.; Leads
Get one mail message: Returns data about a specific mail message.; Mailbox
Get one mail thread: Returns a specific mail thread.; Mailbox
Get all mail messages of mail thread: Returns all the mail messages inside a specified mail thread.; Mailbox
Get mail threads: Returns mail threads in a specified folder ordered by the most recent message within.; Mailbox
Get one note: Returns details about a specific note.; Notes
Get all comments for a note: Returns all comments associated with a note.; Notes
Get all note fields: Returns data about all note fields.; NoteFields
Get all notes: Returns all notes.; Notes
List updates about organization field values: Lists updates about field values of an organization.; Organizations
Get one organization field: Returns data about a specific organization field.; OrganizationFields
Get all organization fields: Returns data about all organization fields.; OrganizationFields
List files attached to an organization: Lists files associated with an organization.; Organizations
List followers of an organization: Lists the followers of an organization.; Organizations
List mail messages associated with an organization: Lists mail messages associated with an organization.; Organizations
Get one organization relationship: Finds and returns an organization relationship from its ID.; OrganizationRelationships
Get all relationships for organization: Gets all of the relationships for a supplied organization ID.; OrganizationRelationships
List updates about an organization: Lists updates about an organization.; Organizations
List permitted users: List users permitted to access an organization.; Organizations
Get one permission set: Returns data about a specific permission set.; PermissionSets
List permission set assignments: Returns the list of assignments for a permission set.; PermissionSets
Get all permission sets: Returns data about all permission sets.; PermissionSets
List updates about person field values: Lists updates about field values of a person.; Persons
Get one person field: Returns data about a specific person field.; PersonFields
Get all person fields: Returns data about all person fields. If a company uses the [Campaigns product](https://pipedrive.readme.io/docs/campaigns-in-pipedrive-api), then this endpoint will also return the `data.marketing_status` field.; PersonFields
List files attached to a person: Lists files associated with a person.; Persons
List followers of a person: Lists the followers of a person.; Persons
List mail messages associated with a person: Lists mail messages associated with a person.; Persons
List products associated with a person: Lists products associated with a person.; Persons
List updates about a person: Lists updates about a person. If a company uses the [Campaigns product](https://pipedrive.readme.io/docs/campaigns-in-pipedrive-api), then this endpoint's response will also include updates for the `marketing_status` field.; Persons
List permitted users: List users permitted to access a person.; Persons
Get deals conversion rates in pipeline: Returns all stage-to-stage conversion and pipeline-to-close rates for the given time period.; Pipelines
Get deals in a pipeline: Lists deals in a specific pipeline across all its stages. If no parameters are provided open deals owned by the authorized user will be returned. This endpoint has been deprecated. Please use <a href="https://developers.pipedrive.com/docs/api/v1/Deals#getDeals" target="_blank" rel="noopener noreferrer">GET /api/v2/deals?pipeline_id={id}</a> instead.; Pipelines
Get deals movements in pipeline: Returns statistics for deals movements for the given time period.; Pipelines
Get deals where a product is attached to: Returns data about deals that have a product attached to it.; Products
Get one product field: Returns data about a specific product field.; ProductFields
Get all product fields: Returns data about all product fields.; ProductFields
List files attached to a product: Lists files associated with a product.; Products
List followers of a product: Lists the followers of a product.; Products
List permitted users: Lists users permitted to access a product.; Products
Get details of a project: Returns the details of a specific project. Also note that custom fields appear as long hashes in the resulting data. These hashes can be mapped against the `key` value of project fields.; Projects
Returns project activities: Returns activities linked to a specific project.; Projects
Returns project groups: Returns all active groups under a specific project.; Projects
Returns project plan: Returns information about items in a project plan. Items consists of tasks and activities and are linked to specific project phase and group.; Projects
Returns project tasks: Returns tasks linked to a specific project.; Projects
Get details of a template: Returns the details of a specific project template.; ProjectTemplates
Get all project templates: Returns all not deleted project templates. This is a cursor-paginated endpoint. For more information, please refer to our documentation on <a href="https://pipedrive.readme.io/docs/core-api-concepts-pagination" target="_blank" rel="noopener noreferrer">pagination</a>.; ProjectTemplates
Get all projects: Returns all projects. This is a cursor-paginated endpoint. For more information, please refer to our documentation on <a href="https://pipedrive.readme.io/docs/core-api-concepts-pagination" target="_blank" rel="noopener noreferrer">pagination</a>.; Projects
Get details of a board: Returns the details of a specific project board.; ProjectBoards
Get all project boards: Returns all projects boards that are not deleted.; ProjectBoards
Get details of a phase: Returns the details of a specific project phase.; ProjectPhases
Get project phases: Returns all active project phases under a specific board.; ProjectPhases
Get recents: Returns data about all recent changes occurred after the given timestamp.; Recents
Get one role: Returns the details of a specific role.; Roles
List role assignments: Returns all users assigned to a role.; Roles
List pipeline visibility for a role: Returns the list of either visible or hidden pipeline IDs for a specific role. For more information on pipeline visibility, please refer to the <a href="https://support.pipedrive.com/en/article/visibility-groups" target="_blank" rel="noopener noreferrer">Visibility groups article</a>.; Roles
List role settings: Returns the visibility settings of a specific role.; Roles
Get all roles: Returns all the roles within the company.; Roles
Get deals in a stage: Lists deals in a specific stage. If no parameters are provided open deals owned by the authorized user will be returned. This endpoint has been deprecated. Please use <a href="https://developers.pipedrive.com/docs/api/v1/Deals#getDeals" target="_blank" rel="noopener noreferrer">GET /api/v2/deals?stage_id={id}</a> instead.; Stages
Get details of a task: Returns the details of a specific task.; Tasks
Get all tasks: Returns all tasks. This is a cursor-paginated endpoint. For more information, please refer to our documentation on <a href="https://pipedrive.readme.io/docs/core-api-concepts-pagination" target="_blank" rel="noopener noreferrer">pagination</a>.; Tasks
Get a single team: Returns data about a specific team.; LegacyTeams
Get all users in a team: Returns a list of all user IDs within a team.; LegacyTeams
Get all teams: Returns data about teams within the company.; LegacyTeams
Getting the tokens: After the customer has confirmed the app installation, you will need to exchange the `authorization_code` to a pair of access and refresh tokens. Using an access token, you can access the user's data through the API.; Oauth
Get one user: Returns data about a specific user within the company.; Users
Get all call logs assigned to a particular user: Returns all call logs assigned to a particular user.; CallLogs
Get all user connections: Returns data about all connections for the authorized user.; UserConnections
List followers of a user: Lists the followers of a specific user.; Users
List user permissions: Lists aggregated permissions over all assigned permission sets for a user.; Users
List role assignments: Lists role assignments for a user.; Users
List user role settings: Lists the settings of user's assigned role.; Users
List settings of an authorized user: Lists the settings of an authorized user. Example response contains a shortened list of settings.; UserSettings
Get all teams of a user: Returns data about all teams which have the specified user as a member.; LegacyTeams
Get all users: Returns data about all users within the company.; Users
Get all Webhooks: Returns data about all the Webhooks of a company.; Webhooks
Link a remote file to an item: Links an existing remote file (`googledrive`) to the item you supply. For more information, see the tutorial for <a href="https://pipedrive.readme.io/docs/adding-a-remote-file" target="_blank" rel="noopener noreferrer">adding a remote file</a>.; Files
Merge two deals: Merges a deal with another deal. For more information, see the tutorial for <a href="https://pipedrive.readme.io/docs/merging-two-deals" target="_blank" rel="noopener noreferrer">merging two deals</a>.; Deals
Merge two organizations: Merges an organization with another organization. For more information, see the tutorial for <a href="https://pipedrive.readme.io/docs/merging-two-organizations" target="_blank" rel="noopener noreferrer">merging two organizations</a>.; Organizations
Merge two persons: Merges a person with another person. For more information, see the tutorial for <a href="https://pipedrive.readme.io/docs/merging-two-persons" target="_blank" rel="noopener noreferrer">merging two persons</a>.; Persons
Update activity in project plan: Updates an activity phase or group in a project.; Projects
Update task in project plan: Updates a task phase or group in a project.; Projects
Receives an incoming message: Adds a message to a conversation. To use the endpoint, you need to have **Messengers integration** OAuth scope enabled and the Messaging manifest ready for the [Messaging app extension](https://pipedrive.readme.io/docs/messaging-app-extension).; Channels
Refreshing the tokens: The `access_token` has a lifetime. After a period of time, which was returned to you in `expires_in` JSON property, the `access_token` will be invalid, and you can no longer use it to get data from our API. To refresh the `access_token`, you must use the `refresh_token`.; Oauth
Link a user with the installed video call integration: A video calling provider must call this endpoint after a user has installed the video calling app so that the new user's information is sent.; Meetings
Search leads: Searches all leads by title, notes and/or custom fields. This endpoint is a wrapper of <a href="https://developers.pipedrive.com/docs/api/v1/ItemSearch#searchItem">/v1/itemSearch</a> with a narrower OAuth scope. Found leads can be filtered by the person ID and the organization ID.; Leads
Update an activity type: Updates an activity type.; ActivityTypes
Update a comment related to a note: Updates a comment related to a note.; Notes
Update a deal field: Updates a deal field. For more information, see the tutorial for <a href=" https://pipedrive.readme.io/docs/updating-custom-field-value " target="_blank" rel="noopener noreferrer">updating custom fields' values</a>.; DealFields
Update file details: Updates the properties of a file.; Files
Update filter: Updates an existing filter.; Filters
Update existing goal: Updates an existing goal.; Goals
Update a lead: Updates one or more properties of a lead. Only properties included in the request will be updated. Send `null` to unset a property (applicable for example for `value`, `person_id` or `organization_id`). If a lead contains custom fields, the fields' values will be included in the response in the same format as with the `Deals` endpoints. If a custom field's value hasn't been set for the lead, it won't appear in the response. Please note that leads do not have a separate set of custom fields, instead they inherit the custom fields’ structure from deals. See an example given in the <a href="https://pipedrive.readme.io/docs/updating-custom-field-value" target="_blank" rel="noopener noreferrer">updating custom fields’ values tutorial</a>.; Leads
Update a lead label: Updates one or more properties of a lead label. Only properties included in the request will be updated.; LeadLabels
Update mail thread details: Updates the properties of a mail thread.; Mailbox
Update a note: Updates a note.; Notes
Update an organization field: Updates an organization field. For more information, see the tutorial for <a href=" https://pipedrive.readme.io/docs/updating-custom-field-value " target="_blank" rel="noopener noreferrer">updating custom fields' values</a>.; OrganizationFields
Update an organization relationship: Updates and returns an organization relationship.; OrganizationRelationships
Update a person field: Updates a person field. For more information, see the tutorial for <a href=" https://pipedrive.readme.io/docs/updating-custom-field-value " target="_blank" rel="noopener noreferrer">updating custom fields' values</a>.; PersonFields
Update a product field: Updates a product field. For more information, see the tutorial for <a href=" https://pipedrive.readme.io/docs/updating-custom-field-value " target="_blank" rel="noopener noreferrer">updating custom fields' values</a>.; ProductFields
Update a project: Updates a project.; Projects
Update role details: Updates the parent role and/or the name of a specific role.; Roles
Update pipeline visibility for a role: Updates the specified pipelines to be visible and/or hidden for a specific role. For more information on pipeline visibility, please refer to the <a href="https://support.pipedrive.com/en/article/visibility-groups" target="_blank" rel="noopener noreferrer">Visibility groups article</a>.; Roles
Update a task: Updates a task.; Tasks
Update a team: Updates an existing team and returns the updated object.; LegacyTeams
Update user details: Updates the properties of a user. Currently, only `active_flag` can be updated.; Users

FAQ

Pipedrive integration, answered

How do AI agents use Pipedrive through Open Connector?: Your user connects Pipedrive once with one of its cataloged authentication methods. Open Connector stores the credential in an encrypted vault and exposes Pipedrive tools to your agent over MCP or a typed API, with credentials injected server-side on each call.
Is this a Pipedrive MCP server?: Yes. Open Connector can serve Pipedrive as a named MCP server with a scoped allowlist and a per-user connection URL, so any MCP client can call Pipedrive actions with credentials injected server-side.
Where do Pipedrive credentials live?: In your own infrastructure. Open Connector keeps credentials in its own vault and injects them at call time, so they never leave your environment.

Give your agents Pipedrive — keep the keys.

Open source, self-hostable, with Pipedrive credentials that never leave your infrastructure. Run it from source today.

View source on GitHub How the MCP gateway works →