Menu
Mattering Automations connector

A Pipedrive MCP built on the current API, with honest deletes

Connect your company domain and API token, and deals, contacts, organizations, pipelines, activities, leads, and notes become workflow steps for visual automations and AI agents. Built on Pipedrive's current API v2 everywhere v2 exists, and every delete node states exactly how recoverable the deletion really is.

44 ready-made nodes One credential to connect Works with Claude, ChatGPT, and Matter

What the Pipedrive MCP connector does

The Pipedrive connector for Mattering Automations is 44 nodes across the CRM core: deals (list, search, get, create, update, move stage, delete), persons and organizations with the same full lifecycle, read access to pipelines and stages, activities (schedule, update, mark done, delete), notes, the lead inbox (capture, update, archive, delete), the company user list, and file metadata. Pipedrive's own move on the board, advancing a deal, gets a dedicated node in Pipedrive: Move Deal to Stage so the intent is explicit on the canvas.

Every node speaks MCP, the open protocol for connecting AI assistants to tools, so Claude, ChatGPT, and any MCP-capable assistant can use them, alongside Matter, the AI assistant built into the platform. An assistant can look up a contact from an email address, summarize which deals moved this week, and log a note on the right record without anyone opening the CRM.

Because Mattering is a work platform rather than middleware, CRM changes land somewhere useful by default: a deal reaching a new stage can open prep tasks in Mattering Productivity, a won deal can kick off an onboarding checklist, and a scheduled deal sweep can keep a Mattering database in sync with the pipeline. Mattering Sales is the platform's native CRM; the Pipedrive connector exists for teams already living in Pipedrive who want their deals wired into the same canvas.

The build is current-API by policy: deals, persons, organizations, activities, pipelines, stages, and all four search families run on Pipedrive's API v2, with v1 used only where no v2 surface exists (leads, notes, users, files). And the six delete nodes are honest about consequences: deal, person, and organization deletes are Pipedrive soft deletes recoverable in the Pipedrive UI for 30 days, while a lead delete is immediate and permanent, so each destructive node names the reversible alternative, like archiving a lead instead of deleting it.

One connection, three surfaces

  • Visual automations. Drag Pipedrive nodes onto the canvas and wire them to triggers, conditions, and other apps.
  • AI agents, yours or ours. These nodes speak MCP, the open protocol, so Claude, ChatGPT, and any MCP-capable assistant can use them, and Matter, the agent built into the platform, uses them natively.
  • The whole platform. Combine with native tasks, projects, and other connectors, no middleware in between.

Every Pipedrive node, ready to drop on the canvas

44 nodes, generated from the connector itself so this list always matches what ships. Expand a category to browse.

Read and query nodes 24

Pipedrive: Get Activity

Fetch one activity by id (API v2).

Pipedrive: Get Current User

Return the user the API token belongs to, with bound company data (company id, name, and domain). Needs no configuration, which makes it the connector's credential health check: a bad token or wrong company domain fails here before anything else runs.

Pipedrive: Get Deal

Fetch one deal by id (API v2). Ask for custom field values explicitly via the custom_fields parameter; v2 returns them nested under custom_fields, keyed by field API key.

Pipedrive: Get File

Fetch one file's METADATA by id (API v1): name, size, type, linked records, and download URL. The URL itself still requires Pipedrive authentication to fetch.

Pipedrive: Get Lead

Fetch one lead by its UUID (API v1).

Pipedrive: Get Note

Fetch one note by id (API v1). Content is HTML.

Pipedrive: Get Organization

Fetch one organization by id (API v2), including the structured address object. Ask for custom field values explicitly via the custom_fields parameter.

Pipedrive: Get Person

Fetch one person by id (API v2), with emails and phones as arrays of {value, primary, label} objects. Ask for custom field values explicitly via the custom_fields parameter.

Pipedrive: Get Pipeline

Fetch one pipeline by id (API v2).

Pipedrive: Get Stage

Fetch one stage by id (API v2).

Pipedrive: List Activities

List activities (calls, meetings, tasks) with API v2 cursor pagination, filterable by owner, linked deal, lead, person, or organization, and done state.

Pipedrive: List Deals

List deals (API v2, cursor paginated), filterable by owner, linked person or organization, pipeline, stage, status, a saved filter, or an updated-since window. Page through with additional_data.next_cursor.

Pipedrive: List Files

List file METADATA (API v1, offset paginated): name, size, type, the deal/person/organization each file is attached to, and its download URL. Metadata only; the binary download and multipart upload endpoints are not built because the canvas cannot carry file bytes.

Pipedrive: List Leads

List leads (API v1, offset paginated), filterable by owner, linked person or organization, a saved filter, or an updated-since window. Lead ids are UUID strings. Archived leads are not returned here (they live under a separate endpoint that is not built).

Pipedrive: List Notes

List notes (API v1, offset paginated with start + limit), filterable by author and by the deal, person, organization, or lead they are attached to. Note content is HTML.

Pipedrive: List Organizations

List organizations (companies) with API v2 cursor pagination, filterable by owner, a saved filter, or an updated-since window.

Pipedrive: List Persons

List persons (contacts) with API v2 cursor pagination, filterable by owner, organization, a saved filter, or an updated-since window.

Pipedrive: List Pipelines

List all pipelines (API v2). The usual first step for resolving the pipeline_id that deal nodes and the stage list need.

Pipedrive: List Stages

List stages (API v2), optionally scoped to one pipeline. This is where Move Deal to Stage gets its stage_id from.

Pipedrive: List Users

List every user in the company (API v1). The lookup table for the owner_id fields used across deal, person, organization, activity, and lead nodes.

Pipedrive: Search Deals

Full-text search across deals (API v2). Results come back as items with a result_score and the matched deal. Search endpoints have their own rate cap of 10 requests per 2 seconds.

Pipedrive: Search Leads

Full-text search across leads (the one lead endpoint that is API v2): titles, notes, and custom fields. Search endpoints are capped at 10 requests per 2 seconds.

Pipedrive: Search Organizations

Full-text search across organizations (API v2): names, addresses, notes, and custom fields. Search endpoints are capped at 10 requests per 2 seconds.

Pipedrive: Search Persons

Full-text search across persons (API v2): names, emails, phones, notes, and custom fields. The go-to lookup for finding a contact id from an email address. Search endpoints are capped at 10 requests per 2 seconds.

Action nodes 20

Pipedrive: Create Activity

Create an activity (call, meeting, task, deadline, email, or lunch by default; accounts can define more types) and link it to a deal, lead, person, or organization. The follow-up scheduling step for CRM automations.

Pipedrive: Create Deal

Create a deal (API v2). Only the title is required; link it to a person and organization, place it in a pipeline stage, and set value and expected close date in the same call.

Pipedrive: Create Lead

Create a lead (API v1). A lead must be linked to a person or an organization, so set person_id or organization_id (create the contact first if needed). The lead inbox entry point for inbound automation.

Pipedrive: Create Note

Create a note (API v1) attached to a deal, person, organization, or lead; at least one of those links is required. Content is HTML-formatted text (about 100 KB max). The standard way for an automation to log context onto a CRM record.

Pipedrive: Create Organization

Create an organization (company) with API v2. Only the name is required; the address is a structured object whose value field carries the full address string.

Pipedrive: Create Person

Create a person (contact) with API v2. Emails and phones are arrays of {value, primary, label} objects, so one person can carry work and home contact points from the start.

Pipedrive: Delete Activity

Delete an activity (API v2). Pipedrive soft delete: marked as deleted and PERMANENTLY deleted after 30 days. Unlike deals and contacts, the UI offers no Deleted-filter restore for activities, so treat this as effectively permanent; to close an activity without losing it, mark it done instead.

Pipedrive: Delete Deal

Delete a deal (API v2). This is Pipedrive's soft delete: the deal is marked as deleted, stays recoverable from the Deleted filter in the Pipedrive UI for 30 days, and is then PERMANENTLY deleted. To take a deal off the board without deleting it, set its status to lost or archive it instead.

Pipedrive: Delete Lead

Delete a lead (API v1). DESTRUCTIVE AND IMMEDIATE: unlike deal, person, and organization deletes, a lead delete is permanent with no 30-day window and no UI recovery. To remove a lead from the inbox reversibly, archive it with Update Lead (is_archived) instead.

Pipedrive: Delete Note

Delete a note (API v1). Destructive: the docs document no recovery window for notes, so treat the deletion as permanent.

Pipedrive: Delete Organization

Delete an organization (API v2). Pipedrive soft delete: marked as deleted, recoverable from the Deleted filter in the Pipedrive UI for 30 days, then PERMANENTLY deleted. Its persons and deals are unlinked, not deleted.

Pipedrive: Delete Person

Delete a person (API v2). Pipedrive soft delete: marked as deleted, recoverable from the Deleted filter in the Pipedrive UI for 30 days, then PERMANENTLY deleted along with the links to their deals and activities.

Pipedrive: Mark Activity Done

Mark an activity done (API v2 PATCH of the done flag; Pipedrive has no separate complete endpoint). Fully reversible: set done to false to reopen it.

Pipedrive: Move Deal to Stage

Move a deal to another stage (API v2 PATCH with stage_id): the pipeline-progression step for automations, kept separate from the general update node so the intent is explicit on the canvas. Set pipeline_id too when the target stage lives in a different pipeline.

Pipedrive: Update Activity

Update an activity (API v2 PATCH): only the fields you fill are sent. Reschedule with due_date/due_time, relink it, or flip done in the same call.

Pipedrive: Update Deal

Update a deal (API v2 PATCH): only the fields you fill are sent, everything else is left untouched. Set status to won or lost to close the deal (lost_reason applies to lost deals), or back to open to reopen it.

Pipedrive: Update Lead

Update a lead (API v1 PATCH): only the fields you fill are sent. is_archived moves the lead to or from the archive, which is the reversible way to tidy the inbox (unlike delete).

Pipedrive: Update Note

Update a note (API v1 PUT): change its content, move it to another record, or pin/unpin it. Only the fields you fill are sent.

Pipedrive: Update Organization

Update an organization (API v2 PATCH): only the fields you fill are sent, everything else is left untouched.

Pipedrive: Update Person

Update a person (API v2 PATCH): only the fields you fill are sent. Note that emails and phones REPLACE the person's existing arrays, so include every contact point you want to keep.

Connecting Pipedrive takes one credential

Pipedrive issues each user a personal API token under Personal preferences, then API, inside the Pipedrive app. The credential is two-part: the token plus your company domain, the yourcompany part of yourcompany.pipedrive.com, because Pipedrive routes API requests through the company host. Mattering sends the token as the x-api-token header on every request; it never appears in a URL. Only one token is active per user at a time, and regenerating it invalidates the old one.

1

In Pipedrive, open Personal preferences, then the API tab, and copy your personal API token. Note your company domain, the yourcompany part of yourcompany.pipedrive.com.

2

In Mattering Automations, open Connectors, click Add Connector, choose Pipedrive, and create a credential with the company domain as the username and the API token as the password.

3

Click Test Connection. Mattering calls Pipedrive's users/me endpoint through your company host and confirms the token authenticates, echoing back the user and company the token is bound to.

4

All 44 Pipedrive nodes appear in the canvas palette. Run Pipedrive: List Pipelines and Pipedrive: List Stages first: they resolve the pipeline and stage ids that the deal nodes need.

Common uses for the Pipedrive MCP

Moving deals through the pipeline

Pipedrive: Move Deal to Stage is the workhorse: an automation advances a deal the moment its condition is met, with Pipedrive: List Pipelines and Pipedrive: List Stages resolving the ids once. Pipedrive: Update Deal closes the loop by setting status to won or lost, and back to open to reopen.

Contact lookup an agent can do

Pipedrive: Search Persons finds a contact id from an email address, and Pipedrive: Search Deals, Pipedrive: Search Organizations, and Pipedrive: Search Leads cover the rest of the record types, all full-text and read-only. Search endpoints carry Pipedrive's own cap of 10 requests per 2 seconds, which matters for loops.

Inbound lead capture

A form submission becomes a CRM record in three steps: Pipedrive: Create Person for the contact, Pipedrive: Create Lead linked to that person (a lead must be linked to a person or an organization), and Pipedrive: Create Note to attach the submission details as context on the record.

Follow-ups that schedule themselves

Pipedrive: Create Activity schedules a call, meeting, or task and links it to the deal, person, or organization it belongs to. Pipedrive: Mark Activity Done closes it reversibly when the work happens, and Pipedrive: List Activities filtered by owner and done state powers a daily follow-up digest.

Pipeline sweeps into the platform

There is no inbound Pipedrive trigger, so the honest pattern is polling: run Pipedrive: List Deals on a schedule with an updated-since window, and route what changed into Mattering Productivity tasks or a Mattering database. A deal that reached a new stage opens its prep tasks; a deal marked won starts the onboarding checklist.

Notes as the audit trail

Pipedrive: Create Note is the standard way for an automation to log what it did onto the record it did it to: enrichment results, meeting summaries, or a link back to the Mattering task that handled the work. Content is HTML, and Pipedrive: Update Note can revise or pin what is already there.

Example: A won deal kicks off the onboarding checklist

Built on the Automations canvas in a few minutes, or described in plain language to Matter and built for you.

1

Trigger: a scheduled run fires, and Pipedrive: List Deals with an updated-since window returns every deal that changed since the last sweep.

2

A condition keeps only the deals whose status is now won.

3

Pipedrive: Get Person and Pipedrive: Get Organization pull the contact details and company record the onboarding needs.

4

Mattering Productivity opens the onboarding checklist as tasks, assigned to the delivery team with the deal value and contacts attached.

5

Pipedrive: Create Activity schedules the kickoff call against the deal so the sales side sees it on their calendar.

6

Pipedrive: Create Note logs a link to the checklist back onto the deal, so anyone opening the CRM record can see onboarding is underway.

Pipedrive MCP questions, answered

What Pipedrive operations are supported?

44 nodes: full lifecycle for deals (including a dedicated stage-move node), persons, organizations, activities, notes, and leads; read access to pipelines, stages, users, and file metadata; and full-text search across deals, persons, organizations, and leads. Deliberately not shipped: pipeline and stage writes (sales-process admin, not workflow automation), the products catalog, file upload and download (the canvas cannot carry file bytes), webhooks management, merge endpoints (a merge cannot be unmerged), and the Fields and Filters metadata APIs.

Does this work with Claude, ChatGPT, or other AI assistants?

Yes. Mattering exposes these nodes over MCP, an open protocol for connecting AI assistants to tools, so any MCP-capable assistant, including Claude and ChatGPT, can connect to your workspace and use them. Matter, the assistant built into the platform, uses the same nodes natively.

Which Pipedrive API version is this built on?

The current one, per resource. Deals, persons, organizations, activities, pipelines, stages, and all searches run on Pipedrive's API v2, which is the surface Pipedrive recommends and which costs fewer rate-limit tokens per request. v1 is used only where no v2 exists: leads, notes, users, and files. In practice that means cursor pagination and true partial updates (only the fields you fill are sent) on the v2 surface.

What actually happens when a node deletes something?

It depends on the record type, and each node says so. Deal, person, and organization deletes are Pipedrive soft deletes: recoverable from the Deleted filter in the Pipedrive UI for 30 days, then permanently deleted. A lead delete is immediate and permanent with no recovery window; archiving the lead via Pipedrive: Update Lead is the reversible way to tidy the inbox. A note delete has no documented recovery, and an activity delete has no UI restore path, so treat both as permanent and prefer Pipedrive: Mark Activity Done for closing activities.

Can a Pipedrive event trigger a workflow?

Not as a trigger node in this connector; there is no inbound Pipedrive trigger yet. The honest pattern today is polling: run Pipedrive: List Deals (or the person, organization, or lead list nodes) on a schedule with an updated-since filter and act on what changed. The lists support saved filters and owner scoping, so a sweep can be as narrow as one pipeline or one rep.

What credential do I need, and where do the two parts go?

Two things: your company domain (the yourcompany part of yourcompany.pipedrive.com) and your personal API token from Personal preferences, then API, in Pipedrive. The connect form uses a username and password pair: the company domain goes in the username field and the API token in the password field. Mattering sends the token as the x-api-token header on every request; it is never placed in a URL.

What are the rate limits?

Pipedrive meters api-token access two ways: a daily token budget that scales with plan and seats, where each request costs tokens (v2 requests cost less than v1), and a per-2-second burst window by plan. Search endpoints have their own cap of 10 requests per 2 seconds on every plan. Exceeding either returns a 429, and the connector does not invent retries, so schedule sweeps rather than tight loops.

Why did my connection suddenly start failing with 401s?

The most common cause is token regeneration: Pipedrive keeps only one API token active per user, so if the token was regenerated in Personal preferences, or by anything else that user connected, the old token dies instantly and every node fails at once. Copy the new token and update the credential on the connector. The connection test calls users/me, which also echoes the company the token is bound to, so a wrong company domain is diagnosed in the same step.

44 nodes waiting on the canvas

Put Pipedrive to work inside your workspace

Connect once, then use every node in visual automations and AI agent workflows across the Mattering platform.

All product names, logos, and brands are property of their respective owners and are used for identification purposes only. Use of these names, logos, and brands does not imply endorsement or affiliation. Pipedrive is a product of its respective owner; Mattering is an independent platform.

Start Free Explore our Products