Menu

Mattering Automations Pipedrive integration

Connect Pipedrive to Mattering Automations: deals, contacts, organizations, pipelines, activities, leads, and notes as workflow steps, authenticated with your company domain and API token.

The Mattering Automations Pipedrive integration adds Pipedrive to your automation canvas: list, search, create, update, and stage-move deals, manage persons and organizations, read pipelines and stages, schedule and complete activities, attach notes, capture and archive leads, and read users and file metadata. It is built on Pipedrive's current API v2 for every resource that has one, with v1 used only where no v2 exists (leads, notes, users, files).

Setup takes a few minutes: note your company domain, copy your API token from Personal preferences in Pipedrive, attach both as a credential in Mattering, and test the connection. This guide walks through each step and ends with the full node reference.

Deletes are labeled honestly. Deal, person, and organization deletes are Pipedrive soft deletes, recoverable in the Pipedrive UI for 30 days; a lead delete is immediate and permanent, with archiving via Pipedrive: Update Lead as the reversible alternative; note and activity deletes should be treated as permanent. Verify the integration with read nodes first, and keep the six delete nodes behind conditions or manual runs.

Before you start

  • A Pipedrive account. The API token carries its user's full access, so a trial account or sandbox works for testing before pointing automations at production data.
  • Your company domain: the yourcompany part of yourcompany.pipedrive.com, visible in your browser's address bar whenever you are logged in to Pipedrive.
  • Access to the API tab under Personal preferences in Pipedrive to copy the personal API token.
  • A Mattering workspace with access to the Automations app.

Get your Pipedrive company domain and API token

Mattering authenticates to Pipedrive with a two-part credential: your company domain, which becomes the host every API request is routed through, and your personal API token, which is sent as the x-api-token header on every request. The token never appears in a URL, so it cannot leak through logged request paths.

Note your company domain. It is the subdomain of your Pipedrive URL: for yourcompany.pipedrive.com, the domain is yourcompany. Only that part is needed; if you paste the full URL, Mattering normalizes it down to the subdomain.
In Pipedrive, click your profile picture, open Personal preferences, and select the API tab.
Copy the personal API token shown there.
The API token is tied to one user and carries that user's full access, and only one token is active per user at a time: regenerating it invalidates the old one instantly, which surfaces as every Pipedrive node failing with 401s at once. If several tools share one user's token, regeneration in any of them breaks the rest.

Connect Pipedrive to Mattering

In Mattering Automations, open Connectors and click Add Connector.
Choose Pipedrive from the list.
Click Create new credential. The form shows generic Username and Password fields: enter the company domain as the username and the API token as the password.
The credential is stored encrypted in Google Secret Manager and never appears in workflow logs. On the wire, the token travels only as the x-api-token header, never in a URL.
Click Test Connection: Mattering calls Pipedrive's users/me endpoint through your company host and reports the connected user. The response also carries the company id, name, and domain the token is bound to, so a typo in the domain fails here rather than in a workflow.
Click Connect. All 44 Pipedrive nodes appear in your canvas palette.

Verify it works

After connecting, open any automation canvas and check the palette: a Pipedrive section should list the query and action nodes. Drop Pipedrive: Get Current User onto the canvas and run a test step. It takes no configuration and is a safe, read-only call; a successful response returns the user the token belongs to along with the bound company id, name, and domain. Confirm the echoed domain matches the one you entered.

To confirm the wider surface, run Pipedrive: List Pipelines and Pipedrive: List Stages, which return the pipeline and stage ids that Pipedrive: Move Deal to Stage and the deal nodes need, then Pipedrive: List Deals for the deal surface itself. Everything in the verify path is read-only; nothing here can modify or delete a CRM record.

Node reference

44 nodes, generated from the connector itself so this reference always matches what ships.

Read and query nodes 24

Pipedrive: Get Activity

pipedrive_get_activity

Fetch one activity by id (API v2).

Pipedrive: Get Current User

pipedrive_get_me

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

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

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

pipedrive_get_lead

Fetch one lead by its UUID (API v1).

Pipedrive: Get Note

pipedrive_get_note

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

Pipedrive: Get Organization

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

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

pipedrive_get_pipeline

Fetch one pipeline by id (API v2).

Pipedrive: Get Stage

pipedrive_get_stage

Fetch one stage by id (API v2).

Pipedrive: List Activities

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

pipedrive_move_deal_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

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

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

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

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

pipedrive_update_organization

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

Pipedrive: Update Person

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.

Using the integration

On the automation canvas

Pipedrive nodes chain with every other node: a scheduled Pipedrive: List Deals sweep can open prep tasks in Mattering Productivity when a deal reaches a new stage, a deal marked won can kick off an onboarding checklist, and Pipedrive: Create Note can log what an automation did back onto the record it touched. Mattering Sales is the platform's native CRM; this integration is for teams already living in Pipedrive who want the pipeline wired into the same canvas.

From AI assistants over MCP

Every node speaks MCP, the open protocol for connecting AI assistants to tools. Claude, ChatGPT, and Matter can find a contact with Pipedrive: Search Persons, summarize pipeline movement from Pipedrive: List Deals, and log context with Pipedrive: Create Note through the same nodes your workflows use. The search and get nodes are read-only, which makes them the safest Pipedrive surface to hand an agent.

Built on the current API, per resource

Deals, persons, organizations, activities, pipelines, stages, and all four search families run on Pipedrive's API v2, the surface Pipedrive recommends, which also costs fewer rate-limit tokens per request. Leads, notes, users, and files have no v2, so those nodes use v1. The practical difference shows in pagination: v2 lists return additional_data.next_cursor and page with a cursor, while v1 lists page with start and limit offsets. Updates on the v2 surface are true partial updates: only the fields you fill are sent.

Deletes, and what actually comes back

Pipedrive: Delete Deal, Pipedrive: Delete Person, and Pipedrive: Delete Organization are Pipedrive soft deletes: the record is recoverable from the Deleted filter in the Pipedrive UI for 30 days, then permanently deleted. Deleting an organization unlinks its persons and deals rather than deleting them; deleting a person takes its deal and activity links with it. Pipedrive: Delete Lead is immediate and permanent with no recovery window, so archive with Pipedrive: Update Lead instead when reversibility matters. Pipedrive: Delete Note has no documented recovery, and Pipedrive: Delete Activity has no UI restore path, so treat both as permanent and prefer Pipedrive: Mark Activity Done to close an activity without losing it.

Reacting to changes without a trigger

There is no inbound Pipedrive trigger in this integration, so react by polling: run Pipedrive: List Deals on a schedule with its updated-since filter and act on what changed since the last sweep. The same pattern works for Pipedrive: List Persons, Pipedrive: List Organizations, and Pipedrive: List Leads, and the lists also accept saved filter ids and owner scoping, so a sweep can watch one pipeline or one rep instead of the whole account.

Field shapes worth knowing

Custom fields on the v2 surface are opt-in for reads: ask for them by API key via the custom_fields parameter, and they come back nested under a custom_fields object. On Pipedrive: Update Person, the emails and phones arrays replace what the person already has, so include every contact point you want to keep. Lead ids are UUID strings rather than integers, a lead must be linked to a person or an organization at creation, and a note must be attached to at least one deal, person, organization, or lead.

Troubleshooting

Test Connection fails with a 401
The token is invalid, picked up stray whitespace when pasted, or was regenerated. Pipedrive keeps only one API token active per user, so regenerating the token anywhere kills the old one instantly; if this integration worked before and every node now fails with 401s at once, regeneration is the first suspect. Copy the current token from Personal preferences in Pipedrive and update the credential on the connector.
Test Connection fails without a clear Pipedrive error
The company domain is probably wrong: requests go to yourdomain.pipedrive.com, so a typo fails at the host level before any API error can come back. The username field must hold only the subdomain, the yourcompany part of yourcompany.pipedrive.com; full URLs are normalized, but a misspelled subdomain cannot be. Confirm the value against your browser's address bar while logged in to Pipedrive.
Search nodes return 429s while other nodes work
Search endpoints have their own cap of 10 requests per 2 seconds on every plan, separate from the general burst window, so a loop that fans out over Pipedrive: Search Persons hits it long before anything else throttles. Space searches out, batch lookups into scheduled sweeps, and reuse ids you have already resolved instead of searching again.
Creating a lead or note returns a 400
Both have link requirements the API enforces. A lead must be linked to a person or an organization, so set person_id or organization_id on Pipedrive: Create Lead, creating the contact first with Pipedrive: Create Person if needed. A note must be attached to at least one deal, person, organization, or lead on Pipedrive: Create Note. An unlinked create is rejected by Pipedrive, not by the node.
Updating a person wiped their other emails or phones
On Pipedrive: Update Person, the emails and phones arrays replace the person's existing arrays rather than merging with them. Fetch the person first with Pipedrive: Get Person, carry the existing entries forward, and include every contact point you want to keep alongside the new one.
Custom fields are missing from deal, person, or organization responses
On the v2 surface, custom field values are opt-in: request them by field API key via the node's custom_fields parameter (up to 15 keys), and they come back nested under a custom_fields object keyed by API key, not flattened onto the record. If the parameter is empty, Pipedrive omits them, which looks like missing data but is just the default.
A record was deleted by mistake
For a deal, person, or organization, open the Pipedrive UI and use the Deleted filter: those deletes are soft for 30 days and the record can be restored there. For a lead there is no recovery, because a lead delete is immediate and permanent; going forward, archive leads with Pipedrive: Update Lead instead. Note and activity deletions should also be treated as unrecoverable, which is why all six delete nodes are flagged destructive and belong behind a condition or a manual run.
Lead nodes reject the id that worked for deals
Lead ids are UUID strings, unlike the integer ids used by deals, persons, and organizations, so a numeric id will not resolve on Pipedrive: Get Lead or the other lead nodes. Take the UUID from Pipedrive: List Leads or Pipedrive: Search Leads output rather than reusing an id from another record type.

Pipedrive is a trademark of its respective owner. Mattering uses platform names to identify the services these integrations connect to; no endorsement or affiliation is implied.

Start Free Explore our Products