Resources · Make integration

Pipedrive CRM Make integrationAutomate Pipedrive CRM with Make.

Can your pipeline update itself while your reps keep selling? The Pipedrive CRM Make integration gives you 108 modules, 15 of them triggers, to move deals, leads and contacts without code. This guide connects your account and walks you through a first working scenario.

Verified Trustpilot reviews · AI, automation & growth agency

What you can automate

What does the Pipedrive CRM Make integration let you automate?

The Pipedrive CRM Make integration links your CRM to the other tools you use, inside a scenario: the automation you build in Make, a chain of modules where each module is one brick (a trigger, an action or a search). Pipedrive can start the scenario, and Make can then read, create or change deals, leads, persons and organizations for you.

Every signup lands as a clean record. A web form sends a contact, Search Persons checks whether it already exists, then Create a Person and Create a Deal open a clean file with nothing typed by hand.

No new deal goes without a next step. New Deal Event reacts as soon as a deal appears and Create an Activity puts a call on the owner's calendar, so nothing sits untouched in the first stage.

Your reporting sheet fills itself. List Deals in a Pipeline or Get Deals Summary feed a spreadsheet, so the sales review starts with the data already in rows.

Know the limits before you start. The Pipedrive API v1 modules are deprecated: if an older scenario still uses one, move that step to the v2 modules. Turning on Extend output makes extra API calls, which costs more operations (one module run on one item, what Make counts on your plan) and eats into your Pipedrive daily API limit. Dates go in as UTC and come back in the user's time zone.

Pipedrive also has a node in n8n: the Pipedrive CRM n8n integration page covers it, and n8n vs Make helps you pick. If you would rather learn the editor properly first, the Make training starts from zero.

Connect

How do you connect your Pipedrive CRM account to Make?

  1. 01

    Add a Pipedrive module

    In your scenario, add any Pipedrive CRM module and click Create a connection. A connection is your Pipedrive account linked to Make once, then reused by every Pipedrive module you add later.

  2. 02

    Name it clearly

    Naming the connection is optional, but worth it. If you manage more than one Pipedrive company, a name like the company or the team saves you from writing into the wrong CRM later.

  3. 03

    Authorize and save

    Grant Make access on the Pipedrive page that opens, or paste the key Pipedrive gives you if Make asks for one, then click Save. The module can now list your pipelines, stages and records.

First scenario

Your first scenario: a follow-up call for every new deal

GoalWhen a deal is added in Pipedrive CRM, Make creates a follow-up activity on it.

  1. 01

    Create the scenario

    Open the Scenarios page, create a new scenario and click the big +. Search for Pipedrive CRM and pick Watch New Events as the first module.

  2. 02

    Connect and choose the event

    Click Create a connection and authorize your account. Then select deals as the object and the add event, so the scenario only wakes up for brand new deals.

  3. 03

    Add the follow-up

    Click the + on the right of the trigger and add Create an Activity. Map the deal coming from the first module so the call is attached to the right deal.

  4. 04

    Test it with Run once

    Click Run once, then add a test deal in Pipedrive. Open the bubbles to read the bundle each module received: one bundle is one item, here one deal, passing from module to module.

  5. 05

    Switch it on

    Delete the test deal and the test activity, then switch the scenario on. With an instant trigger, Pipedrive calls Make as each deal is added, so there is no interval to tune.

Triggers

Which Pipedrive CRM triggers can start a scenario?

15 modules start a scenario when something happens in Pipedrive CRM. A scheduled trigger is checked by Make on the scenario's schedule; an instant one is called by Pipedrive CRM as soon as it happens.

Pipedrive CRM1Watch New Events

Watch New Events

Instant trigger

In MakeTriggers when selected event of the selected object occurs.

One trigger for many cases: you pick an object in Pipedrive and the event you care about, and the scenario starts right when that event happens. It spares you from choosing among the object-specific event triggers when you just need one precise signal.

How it fires
instant: Pipedrive calls Make through a webhook as soon as it happens.
When to use it
you want a scenario that reacts to one clear moment, such as a deal being added, and nothing else.
Watch out
the object and event you pick decide everything this trigger will ever send, so confirm the pair with Run once and a test record before going live.
Pipedrive CRM2Watch Deals

Watch Deals

Scheduled trigger

In MakeTriggers when a new deal is added or updated.

A steady feed of deals that were created or edited since the last check, each arriving as its own bundle. Good for syncing the pipeline to another tool when a short delay is fine.

How it fires
scheduled: Make checks the app on the scenario's schedule, every 15 minutes by default on a new scenario.
When to use it
you mirror deals into a spreadsheet or a billing tool and only need the latest state of each one.
Watch out
an edit to an old deal counts too, so a scenario that should only handle fresh deals needs a way to tell them apart.
Pipedrive CRM3Watch Leads

Watch Leads

Scheduled trigger

In MakeTriggers when a new lead is added or updated.

Brings every lead that was added or changed into your scenario, so the people who handle qualification hear about it without opening Pipedrive. Each lead arrives as a separate bundle.

How it fires
scheduled: Make checks the app on the scenario's schedule.
When to use it
your SDR team works from a shared chat channel and wants a message for each lead that shows up or moves.
Watch out
on the Free plan the shortest interval is 15 minutes, so a lead can wait that long before Make sees it.
Pipedrive CRM4Watch Organizations

Watch Organizations

Scheduled trigger

In MakeTriggers when a new organization is added or updated.

Keeps an outside system in step with your company records: each organization added or edited in Pipedrive reaches the scenario as its own bundle on the next check.

How it fires
scheduled: Make checks the app on the scenario's schedule.
When to use it
your accounting or support tool needs the same list of client companies as the CRM, and nobody wants to copy them over.
Watch out
a busy CRM sends many updated organizations, and every module after the trigger runs once per bundle, which adds operations to your plan.
Pipedrive CRM5Watch Persons

Watch Persons

Scheduled trigger

In MakeTriggers when a new person is added or updated.

Hands your scenario each contact person that was created or modified, ready to push into an email tool or a newsletter list. Persons here are the customers you do deals with, not the users of your Pipedrive account.

How it fires
scheduled: Make checks the app on the scenario's schedule.
When to use it
a marketing list must reflect the contacts your sales reps add or correct in Pipedrive.
Watch out
a small change, like a fixed phone number, also sends the person again, so make the next step safe to repeat.
Pipedrive CRM6Watch Products

Watch Products

Scheduled trigger

In MakeTriggers when a new product is added or updated.

Lets your catalog changes travel: when a product is added to Pipedrive or edited, the scenario receives it and can copy it to a store, a quote tool or a price sheet.

How it fires
scheduled: Make checks the app on the scenario's schedule.
When to use it
product owners edit the catalog in Pipedrive and the rest of the company should not have to ask for the latest version.
Watch out
updates and additions arrive through the same door; if only new products matter, test a few edits with Run once to see what you receive.
Pipedrive CRM7Watch Notes

Watch Notes

Scheduled trigger

In MakeTriggers when a new note is added or updated.

Catches the notes your team writes on deals, persons or organizations, whether new or edited, so what a rep learns on a call can reach a manager or another system.

How it fires
scheduled: Make checks the app on the scenario's schedule.
When to use it
account managers want call notes posted into the client's shared channel without copying them by hand.
Watch out
a note that gets edited comes back a second time; if you post notes somewhere, expect duplicates unless the next step updates instead of adding.
Pipedrive CRM8Watch Activities

Watch Activities

Scheduled trigger

In MakeTriggers when a new activity is added or updated.

Feeds your scenario with calls, meetings and tasks as they are planned or changed in Pipedrive, which is handy for mirroring the sales agenda somewhere else.

How it fires
scheduled: Make checks the app on the scenario's schedule.
When to use it
a shared team calendar or a planning sheet should show every meeting booked in the CRM.
Watch out
dates come back in the user's time zone while Pipedrive expects UTC as input; keep that in mind when you write a time back into Pipedrive.
Pipedrive CRM9Watch Emails

Watch Emails

Scheduled trigger

In MakeTriggers when a new email is added to Inbox.

Spots each new email that lands in your Pipedrive inbox, so a client reply can set off a follow-up, a task or an alert without anyone refreshing the mailbox.

How it fires
scheduled: Make checks the app on the scenario's schedule.
When to use it
you want the deal owner pinged in chat whenever a prospect writes back through the synced inbox.
Watch out
it only watches the inbox; sent messages and other folders are for the Mail modules, such as List Mail Threads.
Pipedrive CRM10New Activity Event

New Activity Event

Instant trigger

In MakeTriggers when a new activity is added, updated or deleted.

Reacts right away when an activity is created, changed or removed, which lets you keep a calendar or a to-do tool exactly in line with Pipedrive, deletions included.

How it fires
instant: Pipedrive calls Make through a webhook as soon as it happens.
When to use it
your team books demos in Pipedrive and the booking must also appear, move or disappear in another calendar.
Watch out
three kinds of events share this trigger; look at the bundle in Run once and route deletions separately so you do not recreate a cancelled meeting.
Pipedrive CRM11New Deal Event

New Deal Event

Instant trigger

In MakeTriggers when a new deal is added, updated or deleted.

Your fastest way to act on the pipeline: the scenario runs the moment a deal is created, edited or deleted, with no polling in between.

How it fires
instant: Pipedrive calls Make through a webhook as soon as it happens.
When to use it
a won deal must open a project in your delivery tool without anyone having to ask for it.
Watch out
deletions trigger it as well; before creating anything downstream, check which event came in, otherwise a deleted deal could spawn a new project.
Pipedrive CRM12New Note Event

New Note Event

Instant trigger

In MakeTriggers when a new note is added, updated or deleted.

Pushes a note to your scenario the second it is added, edited or deleted in Pipedrive, so feedback from the field reaches the right people while it is still fresh.

How it fires
instant: Pipedrive calls Make through a webhook as soon as it happens.
When to use it
product or support teams want every customer remark logged by sales, without waiting for a scheduled check.
Watch out
a note deleted in Pipedrive still sends an event; decide whether your scenario should remove the copy or simply ignore it.
Pipedrive CRM13New Organization Event

New Organization Event

Instant trigger

In MakeTriggers when a new organization is added, updated or deleted.

Gets you a live signal each time a company record is added, changed or removed, which keeps a billing or support tool from drifting away from the CRM.

How it fires
instant: Pipedrive calls Make through a webhook as soon as it happens.
When to use it
a new client company should get its folder, its account in the invoicing tool and its channel as soon as sales creates it.
Watch out
removals come through too; creating a folder on a deletion event is the classic mistake to test away with Run once.
Pipedrive CRM14New Person Event

New Person Event

Instant trigger

In MakeTriggers when a new person is added, updated or deleted.

Moves contact changes out of Pipedrive the instant they happen, adds, edits and deletions alike, which matters when another tool must honor an unsubscribe or a correction quickly.

How it fires
instant: Pipedrive calls Make through a webhook as soon as it happens.
When to use it
your email platform should drop a contact when a rep deletes that person from the CRM.
Watch out
persons are the customers you sell to, not your Pipedrive users; team members changing roles will not show up here.
Pipedrive CRM15New Product Event

New Product Event

Instant trigger

In MakeTriggers when a new product is added, updated or deleted.

Tells your scenario straight away about any product created, updated or deleted in Pipedrive, so a catalog elsewhere never offers something the sales team removed.

How it fires
instant: Pipedrive calls Make through a webhook as soon as it happens.
When to use it
an online shop or a quote generator reads the same catalog as the CRM and must follow every change.
Watch out
treat the three event types differently in the next modules; the same update logic will not work for a deleted product.
Modules

What can Make do in Pipedrive CRM?

Pipedrive CRM gives you 93 modules in 18 groups. For each one: what it does for you, when to reach for it, and what to watch out for.

Deals

13 modules
Pipedrive CRM1

Search Deals

Search

In MakeRetrieves your deals filtered by criteria.

Checks your pipeline for the deals that fit what you are looking for, instead of pulling everything. As a search module, it can hand back zero, one or several bundles, one per deal found.

When to use it
before a form creates a deal, check whether that prospect already has one open.
Watch out
finding nothing is a normal result, so test that case with Run once too.
Pipedrive CRM2

List Deals

Search

In MakeSearches for deals.

Pulls your deals out of Pipedrive in bulk, each one arriving as its own bundle, which is the raw material for a report or a copy in another tool.

When to use it
a finance sheet needs every deal as a row, not just the ones matching a keyword.
Watch out
every module after it runs once per deal, and each run is an operation counted on your plan.
Pipedrive CRM3

List Deals for a Product

Search

In MakeReturns data about deals that have a product attached to them.

Shows you which deals carry a given product, so you can reach every open opportunity touched by a change in that product.

When to use it
a product is being withdrawn or repriced and the owners of related deals must be warned.
Watch out
only deals with the product actually attached come back; deals that merely mention it in a note stay invisible.
Pipedrive CRM4

List Deal Fields

Search

In MakeLists all fields in Deals.

Gives you the full inventory of fields on your deals, the standard ones and the ones your team added, so you know exactly what a scenario can read and write.

When to use it
you are about to map form answers into deals and need to see which fields exist.
Watch out
this describes the fields themselves, not the values stored in any particular deal.
Pipedrive CRM5

Get a Deal

Action

In MakeReturns details of a specific deal.

Fetches everything Pipedrive holds on one deal you already know, which fills the gaps when a previous module only passed along a reference.

When to use it
an activity or a note arrives and you need the full deal behind it before notifying the owner.
Watch out
it needs the deal's identifier; with only a title in hand, run Search Deals first.
Pipedrive CRM6

Get a Deal Field

Action

In MakeGets a Deal field.

Reads how a single deal field is set up in your account, useful when a scenario must write into it correctly instead of guessing.

When to use it
a custom field was edited by an admin and you want to check its setup before an update module writes into it.
Watch out
it targets one field by its ID; use List Deal Fields when you do not know that ID yet.
Pipedrive CRM7

Get Deals Summary

Action

In MakeGets deals summary.

Hands you a summary of your deals in one module run, instead of pulling every deal and adding them up yourself further down the scenario.

When to use it
a chat digest for the sales manager or a dashboard only needs the big picture of the pipeline, not each deal.
Watch out
the doc does not detail what the summary contains, so run it once and read the bundle before you map anything.
Pipedrive CRM8

Create a Deal Field

Action

In MakeCreates a new deal field.

Adds a brand new field to every deal in your Pipedrive account, straight from a scenario, which helps when a setup must be repeated across several accounts.

When to use it
an agency preparing Pipedrive for a new client wants the same custom fields created every time.
Watch out
each run creates another field, so keep it out of scenarios that process many bundles or you will end up with look-alike fields.
Pipedrive CRM9

Create a Deal

Action

In MakeCreates a deal.

Opens a new deal in your pipeline from whatever happened elsewhere, a form, a booked call or a signed quote, so no opportunity depends on someone remembering to type it in.

When to use it
a demo request on your website should become a deal in the first stage.
Watch out
without a check before it, a prospect who writes twice gets two deals; put Search Deals in front.
Pipedrive CRM10

Update a Deal

Action

In MakeUpdates a deal.

Changes an existing deal when the news comes from another tool, so the pipeline reflects reality without a rep editing it by hand.

When to use it
a contract signed in your e-signature tool should move the matching deal forward.
Watch out
the module needs to know which deal to touch; get it from a trigger or from Search Deals, never from a guess.
Pipedrive CRM11

Update a Deal Field

Action

In MakeUpdates Deal field by its ID.

Changes how a deal field is set up, found by its ID. The value stored in each deal stays as it is: that is the job of Update a Deal.

When to use it
you maintain several Pipedrive accounts and a field setup must change in all of them the same way.
Watch out
the change applies to every deal in the account at once.
Pipedrive CRM12

Delete a Deal Field

Action

In MakeDeletes a deal field by its ID.

Clears out a field nobody fills in anymore, found by its ID, without a trip to the settings screen.

When to use it
a template account was set up with fields a client does not need.
Watch out
a delete module cannot be rolled back from Make, so test on a copy and keep this out of any scenario that runs unattended.
Pipedrive CRM13

Delete a Deal

Action

In MakeDeletes a deal.

Keeps the pipeline free of test entries and duplicates that would skew your figures: the deal is erased for good.

When to use it
a duplicate check with Search Deals has flagged a second deal for the same prospect.
Watch out
there is no undo from Make; make sure the ID really points to the duplicate before running it on live data.

Leads

6 modules
Pipedrive CRM14

Search Leads

Search

In MakeRetrieves your leads filtered by criteria.

Tracks down the leads that match your criteria, so a scenario can decide whether it is looking at someone new or someone already in your leads inbox.

When to use it
an event registration comes in and you want to avoid opening a second lead for the same contact.
Watch out
several leads can match; decide which one the next module should act on.
Pipedrive CRM15

List Leads

Search

In MakeRetrieves all your leads.

Retrieves all your leads, one bundle each, which is what you need to export them, score them in another tool or review them in a sheet.

When to use it
the marketing team wants the full leads inbox in a spreadsheet to check the sources.
Watch out
on a large inbox, every downstream module multiplies the operations; filter the flow as early as you can.
Pipedrive CRM16

Get a Lead

Action

In MakeGets a lead.

Loads one lead with its details, which is the step to add when a trigger or a search only told you which lead is concerned.

When to use it
Watch Leads flags a change and you need the complete lead before writing to your emailing tool.
Watch out
it works on a single lead you can identify; for a batch, a list or search module comes first.
Pipedrive CRM17

Create a Lead

Action

In MakeCreates a lead.

Drops a fresh lead into Pipedrive from any source Make can read, so prospects who are not ready for a deal still get recorded.

When to use it
someone downloads a white paper and sales should see them, without cluttering the pipeline with deals.
Watch out
the same person can fill in two forms; a Search Leads step before it saves your reps from double calls.
Pipedrive CRM18

Update a Lead

Action

In MakeUpdates a lead.

Brings a lead up to date with what another tool learned, a newly opened email, a filled survey, a changed company, without anyone retyping it.

When to use it
your emailing platform records that a lead clicked a pricing link and sales should know.
Watch out
map only the fields you mean to change, and check the lead identity comes from a trustworthy module.
Pipedrive CRM19

Delete a Lead

Action

In MakeDeletes a lead.

Honors an erasure request or clears the junk left by spam forms: the lead is gone for good.

When to use it
a contact asks to be forgotten and every trace in the CRM must go.
Watch out
Make cannot bring a deleted lead back, so test with a dummy lead before the scenario handles real ones.

Lead Labels

4 modules
Pipedrive CRM20

List Lead Labels

Search

In MakeLists Lead labels.

Shows the labels available for your leads, the tags your team uses to sort them, so a scenario can pick an existing one rather than inventing a new one.

When to use it
you are setting up a form flow and need to see which labels already exist.
Watch out
labels belong to the account; one renamed by an admin will look different on the next run.
Pipedrive CRM21

Create a Lead Label

Action

In MakeCreates a new lead label.

Gives a campaign or an event its own tag on leads, without a detour through the Pipedrive settings.

When to use it
a trade show is starting and all leads from it should carry their own label.
Watch out
each run adds a label, so this belongs in a one-off setup scenario, not in the flow that handles every lead.
Pipedrive CRM22

Update a Lead Label

Action

In MakeUpdates lead label by its ID.

Keeps your lead tags in line with the words the team uses today: the label is renamed or adjusted in place, found by its ID.

When to use it
a campaign changes its name and the label should match the new one.
Watch out
you need the label ID; List Lead Labels gives it to you before this module runs.
Pipedrive CRM23

Delete a Lead Label

Action

In MakeDeletes lead label by its ID.

Tidies up the tag list once a campaign or a source no longer matters to the team: the label goes, found by its ID.

When to use it
old event labels pile up and the sales team no longer knows which ones are current.
Watch out
it cannot be undone from Make; confirm with List Lead Labels that the ID is the right one.

Products in a Deal

4 modules
Pipedrive CRM24

Add a Product to a Deal

Action

In MakeAdds a product to the deal.

Attaches a product from your Pipedrive catalog to a deal, so the deal shows what the client is actually buying instead of a lone amount.

When to use it
a configurator or a checkout form lists items and each one should land on the matching deal.
Watch out
the product must exist in the catalog first; Create a Product or Search Products belongs before this step.
Pipedrive CRM25

Update Product Attachment Details

Action

In MakeUpdates product attachment details of the deal-product (a product already attached to a deal).

Adjusts a product that is already sitting on a deal, the deal-product link, without detaching and re-adding it.

When to use it
a client revises an order in your quote tool and the lines on the deal must follow.
Watch out
it edits the link on that deal only; the product in your catalog stays untouched, which is Update a Product's job.
Pipedrive CRM26

Delete an Attached Product

Action

In MakeDeletes a product attachment from a deal.

Takes a product off a deal while leaving the product itself in your catalog, which keeps deals honest when an item drops out of the order.

When to use it
a client removes an option from a signed quote and the deal must show it.
Watch out
removing the wrong line cannot be reversed from Make; use List Products in a Deal to target it first.
Pipedrive CRM27

List Products in a Deal

Search

In MakeLists products attached to a deal.

Returns every product attached to a deal, one bundle per line, which is exactly what an invoice or a delivery order needs.

When to use it
a won deal should produce an invoice draft in your accounting tool with each product as a line.
Watch out
the modules after it run for each product, so a deal with many lines uses more operations.

Participants in a Deal

2 modules
Pipedrive CRM28

List Participants of a Deal

Search

In MakeLists the participants associated with a deal.

Tells you who else is involved in a deal beyond the main contact, so your messages reach the full buying group.

When to use it
a proposal is sent and every stakeholder on the deal should receive the follow-up email.
Watch out
the main contact may not be listed the way you expect; List Persons in a Deal covers everyone, whatever their role.
Pipedrive CRM29

Add a Participant to a Deal

Action

In MakeAdds a participant to a deal.

Links an extra person to a deal, which keeps the whole buying committee visible on the deal rather than scattered in notes.

When to use it
a meeting tool reports that a new attendee joined the demo and they should be attached to the deal.
Watch out
the person must already exist in Pipedrive; Search Persons, then Create a Person if needed, comes before.

Files in a Deal

1 module
Pipedrive CRM30

List Files in a Deal

Search

In MakeLists files associated with a deal.

Retrieves the files stored on a deal, each as a bundle, so contracts and quotes can be copied or archived somewhere else.

When to use it
a won deal should have its signed documents moved into the client folder on your cloud drive.
Watch out
this lists the files; getting the content itself takes Download a File, and the Free plan caps files at 5 MB.

Organizations

7 modules
Pipedrive CRM31

Search Organizations

Search

In MakeRetrieves your organizations filtered by criteria.

Finds the companies in your CRM that match your criteria, so a scenario links new data to the right client rather than creating a twin.

When to use it
a signup comes in with a company name and you want the existing organization if there is one.
Watch out
similar company names can return more than one bundle; decide which result wins.
Pipedrive CRM32

List Organizations

Search

In MakeSearches for organizations.

Brings every organization out of Pipedrive as separate bundles, a straightforward way to build an account list elsewhere.

When to use it
customer success needs the complete client list in its own tool before a migration.
Watch out
long lists mean many operations in the following modules; filter as soon as possible.
Pipedrive CRM33

Get an Organization

Action

In MakeReturns details of an organization.

Loads all the details of a single company you have already identified, handy when a deal or a person only points to it.

When to use it
a new deal event arrives and the invoice tool needs the client's full company record.
Watch out
without the organization ID, add Search Organizations first.
Pipedrive CRM34

Create an Organization

Action

In MakeCreates an organization.

Registers a new company in Pipedrive from outside data, giving every future deal and contact a proper home.

When to use it
a B2B signup names a company your CRM has never seen.
Watch out
a quick Search Organizations beforehand avoids two records for the same company, which quietly splits your history.
Pipedrive CRM35

Update an Organization

Action

In MakeUpdates an organization.

Refreshes a company record with what another system knows, so the CRM keeps up after a move, a rename or a change of owner.

When to use it
your billing tool gets a new address for a client and Pipedrive should match.
Watch out
if the value lives in a custom field, Update an Organization Field Value may be the simpler module.
Pipedrive CRM36

Update an Organization Field Value

Action

In MakeUpdates an organization field value.

Writes a new value into one field of an organization, a targeted edit when you only have that one piece of information to change.

When to use it
a health score computed in another tool should land in a dedicated field on the client company.
Watch out
it changes the value, not the field definition; check the field exists with a quick Run once.
Pipedrive CRM37

Delete an Organization

Action

In MakeDeletes an organization.

Clears the duplicates left by a merge of two lists or a spam wave on your forms, by taking the company out of the CRM.

When to use it
a data cleanup scenario has identified a company created twice.
Watch out
Make cannot restore it; confirm the target with Get an Organization before letting it run on real records.

Persons

6 modules

Persons are the customers you are doing deals with — not users.

Pipedrive CRM38

Search Persons

Search

In MakeRetrieves your persons filtered by criteria.

Looks up contacts by your criteria, so a scenario can match an incoming email or phone call to someone already in Pipedrive. Persons are the customers you do deals with, not your account's users.

When to use it
a support ticket arrives and you want the matching client contact.
Watch out
no match returns no bundle; plan the create path.
Pipedrive CRM39

List Persons

Search

In MakeSearches for persons.

Exports your contact persons one bundle at a time, the base for syncing a whole address book into a newsletter or a support tool.

When to use it
you set up a new emailing platform and need all CRM contacts in it once.
Watch out
it returns all your contacts, one after the other. For a single contact you already know, use Get a Person.
Pipedrive CRM40

Get a Person

Action

In MakeReturns details of a person.

Returns the full record of one contact, which gives the next module the phone, email and company it needs to act.

When to use it
a deal event only carries the contact's reference and a text message must go to that person.
Watch out
you need the person ID; if you only have an email address, Search Persons comes first.
Pipedrive CRM41

Create a Person

Action

In MakeCreates a person.

Every new contact lands in Pipedrive as a proper person record, ready to be linked to a deal. In Pipedrive, a person is a customer you sell to, not a teammate who logs in.

When to use it
a demo request arrives from your website form and you want the prospect in the CRM before a rep calls back.
Watch out
place Search Persons before it, so a returning contact does not end up as a duplicate.
Pipedrive CRM42

Update a Person

Action

In MakeUpdates a person.

Keeps a contact record current without anyone retyping it: a new phone number or a new job title flows straight into the existing person.

When to use it
your support tool learns that a customer changed roles, and sales should see it before the next call.
Watch out
which person? The module has to know, so put Search Persons in front of it.
Pipedrive CRM43

Delete a Person

Action

In MakeDeletes a person.

Handles the moment a contact record should no longer exist, for example after someone asks to be erased from your files.

When to use it
erasure requests reach you through a form and you want the removal to follow the same path every time.
Watch out
treat it as final. Test it with Run once on a dummy contact and check which record reaches the module before you switch the scenario on.

Products

6 modules
Pipedrive CRM44

Search Products

Search

In MakeRetrieves your products filtered by criteria.

Finds the products in your Pipedrive catalog that match what you type, so a scenario can pick the right item before building a quote.

When to use it
an order comes in with a product name and you need the matching catalog entry to attach it to a deal.
Watch out
a search can return zero, one or several bundles (the items passed to the next module), so plan for the empty case.
Pipedrive CRM45

List Products

Search

In MakeSearches for products.

Pulls your product catalog out of Pipedrive in one go, one bundle per product, so another tool can receive the whole list.

When to use it
you want to copy the catalog into a spreadsheet or an online shop and have no specific product in mind.
Watch out
every product that flows onward costs operations in each module after it, and a large catalog adds up quickly on your plan.
Pipedrive CRM46

Get a Product

Action

In MakeReturns data about a specific product.

Hands you the full record of one product you already know, with everything Pipedrive stores about it ready to map into the next module.

When to use it
a deal event mentions a product and the next step needs its name to write a line in your invoicing tool.
Watch out
it works from the product ID. If all you have is a name, Search Products is the module to use instead.
Pipedrive CRM47

Create a Product

Action

In MakeCreates a product.

Adds a new item to the Pipedrive catalog from outside the CRM, so sales can attach it to deals right away.

When to use it
your team launches an offer in the e-commerce back office and the CRM catalog should follow without a manual copy.
Watch out
check with Search Products that the item does not exist yet, or the catalog fills up with near-identical entries.
Pipedrive CRM48

Update a Product

Action

In MakeUpdates a product.

Aligns a catalog entry with the source you trust, changing the existing product instead of creating a second one next to it.

When to use it
an offer gets renamed in your billing tool and reps should see the new wording in Pipedrive.
Watch out
to change a product already attached to one specific deal, the right module is Update Product Attachment Details, not this one.
Pipedrive CRM49

Delete a Product

Action

In MakeDeletes a product.

Takes a discontinued item out of the Pipedrive catalog so nobody adds it to a new deal by mistake.

When to use it
an offer is retired in your back office and the CRM should stop proposing it to the sales team.
Watch out
consider it permanent. Run it once on a test product before letting the scenario touch real items.

Notes

5 modules
Pipedrive CRM50

List Notes

Search

In MakeSearches for notes.

Brings back the notes stored in Pipedrive, each one as its own bundle, ready to be copied, summarized or archived elsewhere.

When to use it
you want to feed call notes into a shared document or an AI step that writes a digest for the team.
Watch out
several notes mean several bundles, and each bundle costs an operation in every module that follows.
Pipedrive CRM51

Get a Note

Action

In MakeReturns details about a specific note.

Gives you the full content of one note when an earlier step only handed you its ID.

When to use it
New Note Event fires and you want the complete text before posting it in a team chat.
Watch out
without a note ID the module has nothing to fetch; List Notes is the way to find notes you cannot point to yet.
Pipedrive CRM52

Create a Note

Action

In MakeCreates a note.

Writes context into Pipedrive automatically, so the story of a customer stays in the CRM instead of being scattered across inboxes.

When to use it
a support ticket closes and the rep who owns the account should find the summary in Pipedrive.
Watch out
map the text from the previous module rather than typing a fixed sentence, or every note will read exactly the same.
Pipedrive CRM53

Update a Note

Action

In MakeUpdates a note.

Corrects or completes a note that already exists, so the CRM keeps one clean record instead of a pile of versions.

When to use it
an AI step turns a raw call transcript into a short recap and you want it to replace the draft.
Watch out
you need the ID of the note to change; grab it from Create a Note or New Note Event earlier in the flow.
Pipedrive CRM54

Delete a Note

Action

In MakeDeletes a note.

Clears out a note that should not stay in Pipedrive, such as a duplicate left behind by an earlier test.

When to use it
your first tests with Run once left dummy notes behind and you want to tidy them up through a scenario.
Watch out
there is no way back from inside the module, so double-check which note ID reaches it.

Activities

5 modules
Pipedrive CRM55

List Activities

Search

In MakeSearches for activities.

Collects the activities your team logs in Pipedrive, one bundle each, so you can report on them outside the CRM.

When to use it
you want the open follow-ups pushed into a team channel or a sheet the managers already read.
Watch out
Pipedrive converts dates to UTC on input and returns them in the user's time zone, so check the hours before comparing them with another tool.
Pipedrive CRM56

Get an Activity

Action

In MakeReturns details of a specific activity.

Fetches the whole record of one activity you already point to, so the next module can use anything Pipedrive stores about it.

When to use it
New Activity Event fires and your reminder email needs the full record, not just the fact that something changed.
Watch out
it works from the activity ID. When you only know roughly what you are looking for, List Activities is the better start.
Pipedrive CRM57

Create an Activity

Action

In MakeCreates an activity.

Puts the next step on a rep's Pipedrive agenda without them typing it, so no follow-up depends on memory.

When to use it
a prospect books a demo through your scheduling tool and the rep should see the meeting in the CRM.
Watch out
the date and time you send are converted to UTC, then shown in the user's time zone; test with Run once and check the hour.
Pipedrive CRM58

Update an Activity

Action

In MakeUpdates an activity.

Moves or completes an activity from another tool, so the Pipedrive agenda matches what really happened.

When to use it
a meeting gets rescheduled in the calendar app while the CRM still shows the old slot.
Watch out
keep the activity ID from the moment it was created; without it the scenario cannot target the right one.
Pipedrive CRM59

Delete an Activity

Action

In MakeDeletes an activity.

Wipes an activity that no longer has a reason to exist, keeping the agenda free of ghost tasks.

When to use it
a demo is cancelled on the booking side and the matching Pipedrive meeting should disappear with it.
Watch out
if the history matters to your team, keep the activity and change it with Update an Activity instead.

Mail

6 modules
Pipedrive CRM60

List Mail Threads

Search

In MakeReturns mail threads in specified folder ordered by most recent message within.

Shows you the email conversations of one Pipedrive mailbox folder, the most recent message first, each thread as a bundle.

When to use it
you want to spot threads waiting for an answer and push them into a task list.
Watch out
the module reads the folder you pick, not the whole mailbox, so choose it carefully.
Pipedrive CRM61

List Messages in a Thread

Search

In MakeGet mail messages inside specified mail thread.

Opens a conversation and returns each email inside it as its own bundle, so you can follow the exchange message by message.

When to use it
you want to archive the full back-and-forth with a client in a shared drive.
Watch out
it works inside one thread, so get the thread ID first with List Mail Threads.
Pipedrive CRM62

Get a Mail Thread

Action

In MakeReturns specific mail thread.

Returns one email conversation as a single record, handy when the scenario already knows which thread matters.

When to use it
you stored a thread ID earlier and need its current state before acting on it.
Watch out
it gives you the thread, not the emails inside; for the messages themselves, use List Messages in a Thread.
Pipedrive CRM63

Get a Message

Action

In MakeReturns data about specific mail message.

Retrieves one specific email from Pipedrive, so a later module can read it, summarize it or save it elsewhere.

When to use it
a message from a key account should be summarized by an AI step and posted to the sales channel.
Watch out
you need the message ID, which List Messages in a Thread gives you.
Pipedrive CRM64

Update a Mail Thread Details

Action

In MakeUpdates the properties of a mail thread.

Changes the properties of an email conversation from a scenario, so inbox housekeeping happens without opening Pipedrive.

When to use it
a deal is closed and the related threads should be reorganized without anyone clicking through them.
Watch out
once the connection exists, Make shows which properties the module accepts; read that list before mapping anything.
Pipedrive CRM65

Delete a Mail Thread

Action

In MakeMarks mail thread as deleted.

Clears a conversation out of sight: Pipedrive marks it as deleted instead of erasing it.

When to use it
spam or test threads keep cluttering the shared inbox of the sales team.
Watch out
since nothing is erased, check in Pipedrive before relying on it for a data removal request.

Followers

3 modules
Pipedrive CRM66

List Followers

Search

In MakeList followers of an object of selected type (deals, organizations, persons, products, users).

Tells you who keeps an eye on a deal, an organization, a person, a product or a user, one bundle per follower.

When to use it
you want to notify everyone following a big deal when something important happens to it.
Watch out
pick the object type first: the list you get depends entirely on that choice.
Pipedrive CRM67

Add a Follower

Action

In MakeAdd follower to an object of selected type (deals, organizations, persons).

Subscribes a teammate to a deal, an organization or a person, so the updates reach them without anyone asking.

When to use it
a deal reaches a size that deserves attention and the sales manager should start following it.
Watch out
products and users are not on the list for this module, even though List Followers can read them.
Pipedrive CRM68

Delete a Follower

Action

In MakeDelete a follower from a deal.

Stops a teammate from following a deal once it no longer concerns them, which keeps their feed focused.

When to use it
an account changes owner and the previous rep does not need its updates anymore.
Watch out
the official description limits it to deals; for other objects, Make an API Call is the route.

Users

2 modules
Pipedrive CRM69

Get a User

Action

In MakeReturns data about a specific user within the company.

Identifies one user of your Pipedrive company, meaning a teammate with an account, and gives the scenario their details.

When to use it
a deal arrives with an owner and your chat message should show a real name instead of a number.
Watch out
users and persons are different things: persons are the customers you sell to.
Pipedrive CRM70

Search Users

Search

In MakeReturns data about all users or searches by name or email.

Looks up a teammate in Pipedrive by name or email, or lists every user, so the scenario can reach the right colleague.

When to use it
a form gives you a rep's email address and the next module needs that rep as a Pipedrive user.
Watch out
with no name or email filled in, you get every user as a separate bundle.

Files

2 modules
Pipedrive CRM71

Upload a File

Action

In MakeLets you upload a file, and associate it with a Deal, a Person, an Organization, an Activity or a Product.

Attaches a document to the right Pipedrive record, whether a deal, a person, an organization, an activity or a product, straight from another app.

When to use it
a signed contract comes back from your e-signature tool and should sit on the deal.
Watch out
on the Free plan Make handles files up to 5 MB, so check the size of a heavy scanned PDF before it reaches this step.
Pipedrive CRM72

Download a File

Action

In MakeDownloads a file.

Turns a file stored in Pipedrive into data inside the scenario, so the next module can save it, send it or read it.

When to use it
a proposal attached to a deal should be copied into the client's shared folder.
Watch out
the same size cap applies here: 5 MB per file on the Free plan.

Filter

2 modules
Pipedrive CRM73

List Filters

Search

In MakeLists all filters.

Reveals every saved filter of your Pipedrive account, which is where you find the ID another module asks for.

When to use it
you build a scenario around a view the sales team saved and need to locate it first.
Watch out
every filter comes out as its own bundle, so place the module only where the list is really needed.
Pipedrive CRM74

Get a Filter

Action

In MakeGets filter by its ID.

Explains what one saved Pipedrive filter selects, handy to document a view or check why a report looks off.

When to use it
the numbers behind a pipeline review seem wrong and you want to see the conditions of the filter used.
Watch out
you need the filter ID; List Filters is where you find it.

Other

4 modules
Pipedrive CRM75

Make an API Call

Action

In MakePerforms an arbitrary authorized API call.

Covers whatever the ready-made modules leave out: it calls any endpoint of the Pipedrive API with the connection you already have.

When to use it
you need an endpoint that none of the listed modules reaches and still want to stay inside Make.
Watch out
the Pipedrive API v1 modules are deprecated, so build your call on API v2 and read the Pipedrive API v2 migration guide first.
Pipedrive CRM76

Search for Items

Search

In MakePerforms a search from multiple item types.

Runs one search across several kinds of Pipedrive records at once, so you find a match without guessing whether it is a deal, a person or an organization.

When to use it
an incoming email address could belong to a contact or a company, and you want to check both in one step.
Watch out
results mix item types, so look at the type of each bundle before sending it to a module built for one kind.
Pipedrive CRM77

List Pipelines

Search

In MakeReturns data about all pipelines.

Maps out the sales pipelines of your account and gives you the IDs other modules expect.

When to use it
you set up List Deals in a Pipeline and need to know which pipeline to point it at.
Watch out
each pipeline is a separate bundle; if you only need one, pick it in the module that follows.
Pipedrive CRM78

List Stages

Search

In MakeReturns data about all stages.

Translates stage IDs into names people understand by returning all the stages of your account.

When to use it
a deal update carries a stage ID and your team message should say the stage name.
Watch out
stages from every pipeline come back together, so make sure you pick the one from the right pipeline.

Other modules

15 modules
Pipedrive CRM79

Add an Installment Subscription

Action

In MakeAdds a new installment subscription.

Sets up a payment plan in Pipedrive, so revenue split into several payments is tracked where sales work.

When to use it
A client signs and agrees to pay in several parts, and finance wants that schedule visible in the CRM.
Watch out
For a charge that repeats, Add a Recurring Subscription is the matching module.
Pipedrive CRM80

Add a Recurring Subscription

Action

In MakeAdds a new recurring subscription to a deal.

Records repeating revenue on a deal, so the CRM reflects a customer who pays again and again rather than once.

When to use it
A trial converts to a paid plan in your billing tool and the deal should show the subscription.
Watch out
It adds a new subscription each time it runs; check with Find Subscription By Deal first so a replayed scenario does not create a second one.
Pipedrive CRM81

Cancel a Recurring Subscription

Action

In MakeCancels a recurring subscription.

When a customer leaves, Pipedrive stops expecting their next charges: the repeating plan on the deal comes to an end.

When to use it
a client tells your account manager they are leaving, and a form or a status change should end their plan without anyone opening Pipedrive.
Watch out
it only works on recurring subscriptions. An installment plan has no cancel step here; use Delete a Subscription or update it instead.
Pipedrive CRM82

Delete a Subscription

Action

In MakeMarks an installment or a recurring subscription as deleted.

Cleans up a plan created by mistake or duplicated by an earlier scenario run: the subscription, installment or recurring, is flagged as deleted in Pipedrive.

When to use it
you want the plan gone from the deal entirely, not just stopped. For a customer who simply churns, Cancel a Recurring Subscription tells the story more honestly.
Watch out
treat it as final. Put a filter (a condition between two modules) in front of it so a wrong bundle never reaches this step.
Pipedrive CRM83

Get a Subscription

Action

In MakeReturns details of an installment or a recurring subscription.

Puts the whole picture of one subscription, installment or recurring, in your scenario, so the next modules reuse it without a second lookup.

When to use it
an invoice tool or a Slack message needs the plan's details, and you already know which subscription you are dealing with.
Watch out
if you only have the deal, start with Find Subscription By Deal. Dates come back in the Pipedrive user's time zone, while dates you send in are converted to UTC.
Pipedrive CRM84

Update an Installment Subscription

Action

In MakeUpdates an installment subscription.

Keeps the CRM matching what the customer actually agreed to pay: the split-payment plan on the deal changes without being rebuilt.

When to use it
a sales rep renegotiates the number or size of the installments and records it in a sheet or a form that your scenario watches.
Watch out
this module is for installment plans only. A recurring plan needs Update a Recurring Subscription, and Make will not switch between the two for you.
Pipedrive CRM85

Update a Recurring Subscription

Action

In MakeUpdates a recurring subscription.

After an upgrade or a price change, the running plan follows, which keeps the deal's revenue in Pipedrive in line with reality.

When to use it
a customer moves to a bigger package in your billing tool and you want the CRM to follow without a manual copy.
Watch out
to stop the plan rather than change it, Cancel a Recurring Subscription is the right module. Remember that date inputs are read as UTC.
Pipedrive CRM86

Find Subscription By Deal

Search

In MakeReturns details of an installment or a recurring subscription by the deal ID.

Answers a common question in one step: does this deal carry a subscription, and what does it look like? You give it the deal ID, it returns the installment or recurring plan linked to it.

When to use it
your trigger is a deal event (a deal added or updated) and you need the plan before deciding what to do next.
Watch out
as a search module it can return zero results. Add a filter after it so the scenario handles deals with no plan instead of failing further down.
Pipedrive CRM87

List Activities in a Deal

Search

In MakeLists activities associated with a deal.

Brings back the calls, meetings and tasks logged on a single deal, each one as its own bundle (a single item passed to the next module).

When to use it
before a renewal call, you want a summary of every touchpoint on the deal sent to the rep or written into a doc.
Watch out
one deal can hold many activities, and every module that follows runs once per bundle. Add an aggregator (a tool that groups bundles) if you want a single message.
Pipedrive CRM88

List Deals for a Person

Search

In MakeLists deals associated with a person.

Shows every deal a given contact is involved in, so you see the full relationship with one person instead of one deal at a time.

When to use it
a person emails support and you want the scenario to check their open deals before routing the ticket.
Watch out
Pipedrive calls the customers you sell to persons, not users. Users are your own team members, so point this module at a contact.
Pipedrive CRM89

List Deals in an Organization

Search

In MakeLists deals associated with an organization.

Gathers all deals tied to one company, which gives an account-level view: how many opportunities are open with that customer and where they stand.

When to use it
an organization changes status in another tool (contract signed, account at risk) and the owners of its deals should hear about it.
Watch out
the search can return many deals, and each one triggers the next modules separately, which costs one operation (a module run counted on your Make plan) each time.
Pipedrive CRM90

List Deals in a Pipeline

Search

In MakeLists deals in a specific pipeline across all its stages.

Isolates one sales process: every deal in that pipeline comes out, whatever its stage. Handy when your team runs several pipelines and only one matters.

When to use it
you feed a reporting sheet or a dashboard with the full content of the partner pipeline, without mixing in direct sales.
Watch out
for a big pipeline this can mean many bundles and many operations. List Deals in a Stage narrows it to a single column.
Pipedrive CRM91

List Deals in a Stage

Search

In MakeLists deals in a specific stage.

Targets a single column of your board: only the deals sitting in that stage come out, ready for a follow-up action.

When to use it
deals sitting in your proposal stage should get a reminder task or a check before the rep moves on.
Watch out
this module lists what is in the stage when the scenario runs. It does not react to a deal entering the stage; for that, start from a deal trigger.
Pipedrive CRM92

List Payments of a Subscription

Search

In MakeReturns all payments of an installment or recurring subscription.

Lays out the payment schedule of a subscription, installment or recurring, one bundle per payment, so you can compare what was planned with what reached your bank.

When to use it
finance wants each expected payment copied into an accounting sheet or cross-checked against the payment tool.
Watch out
each payment is a separate bundle. Use an aggregator if you want one line per subscription rather than one per payment.
Pipedrive CRM93

List Persons in a Deal

Search

In MakeLists all persons associated with a deal, regardless of whether the person is the primary contact of the deal, or added as a participant.

Fetches everyone attached to a deal, the main contact and the participants alike, so no stakeholder slips through when you notify or tag people.

When to use it
a deal is won and you want every contact on it added to an onboarding list, not only the primary one.
Watch out
unlike List Participants of a Deal, this module also returns the primary contact. Pick it when you want the whole group in one go.
Need help

Need help automating Pipedrive CRM with Make?

A person reads every message.

FAQ

Pipedrive CRM and Make: common questions

01Is the Pipedrive CRM Make integration free?
Yes, Pipedrive CRM is a standard app in Make, available from the Free plan. That plan lets you keep 2 active scenarios, with at least 15 minutes between two scheduled runs, up to 5 minutes of execution per run, files up to 5 MB and 512 MB of data transfer. Paid plans (Core, Pro, Teams and Enterprise) drop the interval to 1 minute, remove the cap on active scenarios and allow 40 minutes of execution, with usage counted in credits each month. Your Pipedrive subscription is a separate matter that Make does not cover.
02What do you need to connect Pipedrive CRM to Make?
A Pipedrive account and a Make account are all the doc asks for; it lists no other prerequisite. You add any Pipedrive CRM module, click Create a connection, optionally name it, authorize Make on the Pipedrive side or paste the key Pipedrive provides, then click Save. That single connection serves every Pipedrive module in all your scenarios. If you work with several Pipedrive companies, create one connection per company and give each a clear name, so a scenario never writes into the wrong CRM.
03Do Pipedrive CRM triggers in Make react in real time?
It depends on the trigger. Seven are instant: Watch New Events and the six event triggers (New Activity Event, New Deal Event, New Note Event, New Organization Event, New Person Event, New Product Event). Pipedrive calls Make through a webhook as soon as something happens. The eight others, such as Watch Deals, Watch Leads or Watch Emails, are scheduled: Make checks Pipedrive on the scenario's schedule, every 15 minutes by default, 15 minutes at the shortest on the Free plan and 1 minute on paid plans.
04What if the Pipedrive module you need is missing in Make?
Use Make an API Call. It calls any endpoint of the Pipedrive API from your scenario with the same connection, so the 108 listed modules are not a ceiling. Two limits from the doc are worth knowing. The API v1 modules are deprecated, so rebuild any step that still uses one with the v2 modules. And enabling Extend output triggers extra API calls, which costs more operations and counts against your Pipedrive daily API limit. If a scenario keeps failing, the Make troubleshooting guide on the site walks through the usual causes.
05Make or n8n for Pipedrive CRM?
Both can work, because Pipedrive exists in Make and has a node in n8n. The honest criterion is coverage of your use case: in Make, you get 108 modules, 7 instant triggers and Make an API Call for anything else. Write down the two or three Pipedrive actions your process needs, check them on this page and on the Pipedrive CRM n8n integration page, and pick the tool where your other automations already run.