In short
Source: Sales Surge, Make Certified Partner 2025, from more than 150 CRM implementationsAs of: 16 November 2026
In this article
- Why Make.com next to Pipedrive
- Make or Zapier for Pipedrive users
- Where most Make and Pipedrive builds go wrong
- Pipedrive webhooks: how they work and when you need them
- Connecting Make to Pipedrive in seven steps
- What does Make cost for a team of ten reps?
- Pipedrive with Power BI, Shopify, Wix and Intercom: native, Make or custom?
- Ten Make scenarios for Pipedrive that pay back first
- Hiring a Make partner for your Pipedrive integration
- Make next to the alternatives
- FAQ
- Setup time
- 1 to 2 days for the first scenarios
- Sync direction
- Both ways, through webhooks
Why Make.com next to Pipedrive
Pipedrive's own workflow automation works well for logic inside the CRM. Move a deal, create a task, send a template, notify an owner. It stops the moment your workflow has to talk to another tool.
Enrichment, calendar booking, proposals, invoicing, Slack alerts, dashboards and the handoff to marketing automation all live outside Pipedrive. That is the gap Make.com fills.
Make.com, formerly Integromat, is a visual automation platform. It connects thousands of apps and listens to Pipedrive webhooks in real time. You build scenarios with conditions and several steps, without code. For a B2B sales team, Pipedrive plus Make covers much of what HubSpot Operations Hub does, for a fraction of the price.
We use Make on every Pipedrive stack we build. This guide is what we took from more than 150 CRM implementations.
For the background, read about our Make.com partnership, or see how we run Pipedrive workflow automation for clients.
Make or Zapier for Pipedrive users
Zapier is easier for a one-step flow. Once a workflow has conditions or more steps, Make wins on four points.
- Lower cost at volume. Make charges credits, roughly one per module that runs, and filters and routers are free. Zapier counts a task for every action step. A Pipedrive scenario with 5 steps that runs 1,000 times a month is usually much cheaper in Make.
- Conditions and routers. With the router and filters in Make you split one trigger into several paths, on every plan. Zapier can branch with Paths, but only on the more expensive plans.
- Iterators and aggregators built in. Loop through lists from the Pipedrive API and update in batches. Results combine in the same scenario. Zapier loops with its built-in Looping by Zapier step, and every repeated action counts as a task.
- Error handling per step. Make has an error route per module, with its own retry and rollback rules. In Zapier you mostly get a notification and a replay of the failed step.
| Make.com | Zapier | |
|---|---|---|
| How you pay | Credits, about one per module that runs | Tasks, one per action step |
| Branching | Router and filters on every plan | Paths, only on higher plans |
| Lists and batches | Iterators and aggregators built in | The Looping by Zapier step, with a task for every repeated action |
| Error handling | An error route per module, with retry and rollback | Notifications and a replay of the failed step |
| Data hosting | Choice of an EU or a US zone | Hosted in the US |
| Learning curve | Steeper, visual and technical | Lower, step by step |
Where most Make and Pipedrive builds go wrong
We regularly rebuild Make setups that worked on day one and broke without a sound by month three. Five patterns explain almost all of it.
Mistake #1: Polling Pipedrive every 5 minutes instead of using webhooks.
Consequence: A trigger that checks every 5 minutes runs 8,640 times a month, and every check costs a credit. So you pay more and you react later. A scenario that should be live behaves like a nightly batch.
How to fix it: Use Pipedrive webhooks for every scenario that reacts to an event: deal created, stage changed, person updated. Keep polling for reports that run on a schedule, like a daily pipeline roll-up.
Mistake #2: No error handler on any module.
Consequence: An API hiccup at 03:00 fails one Pipedrive update. The whole scenario stops. The next 47 deal updates wait forever or disappear. You find out two weeks later, when a customer asks why their deal still says Negotiation.
How to fix it: Add an error route to every external API call. Log to a Google Sheet or an admin Slack channel, set a 'Sync failed' flag in Pipedrive and send it to a retry queue.
Mistake #3: Triggering on every update and filtering late.
Consequence: A 'deal updated' webhook fires every time someone touches a deal. If you filter after 4 modules, you pay 4 credits for every change that does not matter. At volume this is the biggest cost driver.
How to fix it: Put a filter straight after the trigger. Only continue when the change matches your condition, such as a stage move or a value above a threshold.
Mistake #4: Hardcoding Pipedrive IDs in modules.
Consequence: Six months later, sales adds a stage. Every scenario that uses the old stage IDs breaks at the same moment. Then you spend hours finding out why three workflows stopped on the same Tuesday.
How to fix it: Store the IDs in a Make data store or a mapping table. That goes for pipelines and stages, and for users too. Refer to the name in the scenario and look up the ID at runtime. A new stage then breaks nothing.
Mistake #5: One huge scenario that does ten things.
Consequence: A mega-scenario becomes impossible to fix. Every change can break something unrelated. Debugging means scrolling through 40 modules, and a new colleague cannot maintain it.
How to fix it: One scenario per business outcome. Chain them with Webhook Response or Run Scenario when you need to. Each scenario fits on one screen and has one job.
What Sander says about it
"Two clients with the same Pipedrive and the same tools can pay very different amounts for Make. The difference is scenario discipline, because the features are the same. Clients with filtered scenarios on webhooks stay on a small plan. Clients with polling everywhere move up a plan within months and still complain about delays."
Pipedrive webhooks: how they work and when you need them
A Pipedrive webhook is a message Pipedrive sends to a URL the moment something changes. You need one whenever a scenario has to react to an event, such as a new deal, a stage change or an updated person. For reports that run on a clock, polling is fine.
Every webhook listens to an object and an action. The objects include deals, persons, organisations, activities, notes, products and leads. The actions are added, updated and deleted, and you can also listen to all of them at once. Pipedrive then posts a payload to your URL. That payload is a JSON message with the current data of the record. For an update it also holds the previous values, so you can see what changed.
In Make you rarely create the webhook by hand. The instant version of a Pipedrive trigger creates it for you, and you see it back in Pipedrive under the webhook settings. If Make does not answer, Pipedrive retries the delivery for a while. So build scenarios that can run twice without creating a record twice.
| Instant trigger (webhook) | Polling trigger | |
|---|---|---|
| When it runs | Within seconds of the change | On a schedule, for example every 15 minutes |
| Credits | Only when something happens | On every check, also when nothing changed |
| Best for | Stage changes, new leads, alerts | Daily roll-ups and scheduled clean-ups |
| Watch out for | Updates firing on every small edit, so filter early | Delays and a credit bill that grows with the interval |
One webhook on 'deal updated' sees every edit, also a typo fix in the title. That is why the filter straight after the trigger matters more than the trigger itself.
Connecting Make to Pipedrive in seven steps
Write down which business events you want to automate before you build anything. Then you need these four things.
What you need
- A Make.com account. Free works for testing. For production you take Core or Pro
- Admin rights in Pipedrive, on any paid plan
- A Slack channel or email address for error notifications
- A written list of the events you want to automate
Connect the Pipedrive app in Make
Add a Pipedrive module in Make and authenticate with an API token. You find it in Pipedrive under Personal preferences and then API. Use a dedicated 'Make Integration' user instead of a real rep, so the audit trail shows what a person did and what the integration did.
Choose a webhook over polling whenever possible
In Make, use the instant version of Watch Deals instead of the scheduled one. How Pipedrive webhooks work, and when polling is fine, is in the webhook section above.
Filter straight after the trigger
Add a filter right after the webhook. Only let through events that match your condition, for example stage is Won or value above 5,000. This is the biggest cost lever.
Look IDs up, never hardcode them
Create a Make data store or a Google Sheet with every name next to its ID, for pipelines and stages and users. Refer to the name in the scenario and resolve the ID at runtime.
Add error handlers to every external API call
Right-click a module and add an error handler route. Log the error to a Pipedrive activity or a Google Sheet. A Slack channel works too. Never let it fail silently.
Test with a sandbox deal before you switch it on
Create one test deal in Pipedrive and run the scenario by hand. Then check the result in Pipedrive, in the other tool and in the error log. Only then switch the scenario on.
Check scenario health weekly
Turn on email alerts in Make for failed scenarios. Check the History tab weekly for slow runs. A run over 30 seconds usually means too many polling calls.
How to check it
- Trigger the scenario with a test deal and check that the action fires within 60 seconds
- Force an error with bad data or a disconnected app and check that it gets logged
- Change a field that does not matter and check that the filter stops it
- Check the Pipedrive activity log: the actions should run under the Make user
- Compare the credits used in Make before and after a 24 hour run
What does Make cost for a team of ten reps?
For a team of ten reps with six common scenarios, expect roughly 10,000 Make credits a month. At the time of writing (November 2026), the Core plan includes 10,000 credits for around 9 to 11 dollars a month. Pro starts around 16 to 19 dollars. Check make.com for the current prices.
This is the calculation behind that estimate. Every scenario uses webhooks and a filter straight after the trigger.
| Scenario | Volume per month | Credits per month |
|---|---|---|
| Form submission to person and deal | 300 leads at about 5 credits | about 1,500 |
| Enrichment of new organisations | 300 lookups at about 4 credits | about 1,200 |
| Stage changes to Slack | 400 changes at about 3 credits | about 1,200 |
| Won deal to draft invoice | 40 deals at about 6 credits | about 240 |
| Daily follow-up check on open deals | 22 runs over about 50 deals | about 2,300 |
| Deal changes to a dashboard sheet | 2,000 changes at about 2 credits | about 4,000 |
| Total | about 10,400 |
Put the same scenarios on a polling trigger and you pay for every check, also when nothing changed. That alone can double the bill, as the first mistake above shows. The dashboard sync is usually the first place to save: send only the changes that touch value, stage or close date.
Pipedrive with Power BI, Shopify, Wix and Intercom: native, Make or custom?
Start with what exists in the Pipedrive Marketplace or in the other tool. Add Make when you need rules. Choose custom work only when volume or reporting needs go beyond both. This is how we decide for the four integrations we get asked about most.
| Integration | First choice | When Make | When custom |
|---|---|---|---|
| Power BI | A data connector app from the Marketplace | When a few figures in a sheet are enough for Power BI to read | When you report across several sources or need history |
| Shopify | A Marketplace app that turns orders into persons and deals | When only some orders count, for example B2B above an amount | At high order volume, or with an ERP in between |
| Wix | A Wix form that sends a webhook | Almost always, to map fields and prevent duplicates | Rarely needed |
| Intercom | Intercom's own Pipedrive app | When a conversation should create a deal by rules | Rarely needed |
For reporting across objects that native Pipedrive cannot do, we built our own product, Surge Reports. For forms that write straight into Pipedrive, there is Surge Forms. Both are an alternative to a home-made Make flow when the same need comes back at every client.
Ten Make scenarios for Pipedrive that pay back first
These ten pay back fastest in the Pipedrive stacks we build. Each one is a separate scenario with one job.
1. Lead enrichment on deal creation
- Trigger: Pipedrive Watch Deals (instant, on create)
- Filter: the organisation has an email or domain
- Apollo or Lusha module: enrich by domain
- Filter: update only empty Pipedrive fields
- Pipedrive: update industry and headcount on the organisation, plus the tech stack
- Error handler: log failures to an 'Enrichment errors' sheet
2. Stage notifications to Slack
- Trigger: Pipedrive Watch Deals (on update)
- Filter: stage changed and the new stage is Negotiation or Won
- Pipedrive: get the owner details
- Slack: post the deal name, value, owner and link
- Slack: tag the manager when the value is above a threshold
3. Contacts from form submissions
- Trigger: form webhook into Make
- Pipedrive: search the person by email
- Router: update the existing person or create a new one
- Pipedrive: create or update the person and link the organisation
- Pipedrive: create the deal in the Inbound pipeline at stage 1
- Slack: notify the assigned SDR
4. Deals to invoicing
- Trigger: Pipedrive Watch Deals (on stage Won)
- Pipedrive: get the deal products and contact details
- Mapping: turn Pipedrive products into invoice lines
- Invoicing app: create the draft invoice and attach the customer
- Pipedrive: write the invoice URL back to a custom field on the deal
- Slack: notify finance with the invoice link
5. Enrichment from a LinkedIn URL
- Trigger: Pipedrive Watch Persons (on create)
- Filter: the LinkedIn URL field is filled
- Apollo or another provider: look up the person by LinkedIn URL
- Parse: title, company, headcount and industry
- Pipedrive: update empty fields only, and store the source and date
- Tag the enrichment status for audit
6. Email parsing into Pipedrive
- Trigger: Email Parser webhook (built into Make)
- AI module: extract the intent and deal value, plus the timeline
- Pipedrive: search for the existing person
- Router: create a new lead or attach an activity to the existing deal
- Pipedrive: set a follow-up activity for the right owner
7. Activity reminders via WhatsApp
- Schedule: every weekday at 08:30
- Pipedrive: search activities due today for active reps
- Iterator: loop through the activities
- WhatsApp Cloud API or Twilio: send the reminder
- Pipedrive: log a note that the reminder went out
8. Dashboard refresh triggers
- Trigger: Pipedrive Watch Deals (on any change)
- Filter: value or stage changed, or the close date
- Make data store or Google Sheet: update the row for that deal
- The BI tool reads live from the sheet or data store
- Optional: call the Looker Studio refresh API
9. Multi-tool data sync
- Trigger: a webhook from any of the connected tools
- Router: branch by source
- Per branch: look up the matching record in the other tools by email
- Update only the fields that changed
- Throttle module: prevent endless update loops
10. Conditional follow-ups
- Schedule: daily at 06:00
- Pipedrive: search open deals with no activity in the last 7 days
- Router: 7 to 14 days, or more than 14
- 7 to 14 days: create a follow-up activity for the owner
- More than 14 days: create an activity for the manager and post in Slack
- Pipedrive: log the action as a note
Hiring a Make partner for your Pipedrive integration
You can build your first scenario yourself, and the Make documentation is good. A partner pays off once you run five or more scenarios in production, with error handling, monitoring and a credit budget to watch.
At Sales Surge, Make.com or Zapier workflows start at €750, and a set of five automations also starts at €750. Those are the prices on our pricing page. We are a Make Certified Partner 2025 and a Pipedrive Platinum Partner, so we build both sides of the integration.
- We start with the list of events you want to automate, not with the tool.
- Every scenario gets an error route, a log and a named owner on your side.
- You get the scenarios in your own Make account, so you are never locked in.
See how we run Pipedrive workflow automation for clients, or read the sales automation guide for the bigger picture. For outbound, the Apollo and Instantly guides build on the scenarios above.
Make next to the alternatives
Make is not the right layer for every team. This is when one of the other three fits better.
Zapier
Pros
- Easier to learn for non-technical users
- More native app integrations
- Better for one-step workflows
Cons
- Usually more expensive at volume, because every action step is a task
- Branching with Paths only on the more expensive plans
- In a loop, every repeated action counts as a task
Best for: Marketing teams with simple one-step flows, or a solo founder
n8n (self-hosted)
Pros
- Self-hosted, so you control the data (GDPR)
- Open source
- No cost per run
Cons
- Needs DevOps to host and maintain
- Fewer apps than Make
- Nobody else watches the uptime
Best for: Engineering-heavy teams with strict data residency requirements
Custom code (Node.js + Pipedrive API)
Pros
- Any logic you can write
- No cost per run
- Can live inside your existing apps
Cons
- Months of development instead of days in Make
- Maintenance falls on engineering
- No visual debugging
Best for: Product companies that build Pipedrive logic into their own SaaS
FAQ
How much does Make.com cost for a typical Pipedrive setup?
Make charges credits, roughly one per module that runs. A team of ten reps with six common scenarios on webhooks uses about 10,000 credits a month. At the time of writing (November 2026), that fits the Core plan at around 9 to 11 dollars a month. Pro starts around 16 to 19 dollars. Polling triggers and late filters are what push teams onto bigger plans.
Should I use Make.com or Pipedrive's native workflow automation?
Use Pipedrive's own automations for anything that stays inside Pipedrive, such as tasks on a stage change, owner assignment and reminders. Use Make for anything that crosses tools: enrichment, invoicing, WhatsApp, calendar sync or data between several systems. Using Make for in-CRM logic is slower and costs credits, and Pipedrive automations are too limited to run complex calls to other tools.
Make.com vs Zapier, which is better for Pipedrive?
Make, for any setup with conditions, several steps or volume. It has routers on every plan, handles lists natively, gives you an error route per module and lets you host in the EU. Zapier is easier to learn and fine for a one-step 'when X, do Y' flow. It is not a bad tool, but at volume and with branching Make is usually cheaper and easier to keep stable.
How do Pipedrive webhooks work with Make?
When you add an instant Pipedrive trigger in Make, Make creates a webhook in your Pipedrive account that points to a unique Make URL. Pipedrive then posts every matching event to that URL within seconds. The payload holds the current data of the record and, for an update, the previous values. You can see the webhook in Pipedrive under the webhook settings of your company.
What happens if Make.com is down?
Pipedrive retries a failed webhook delivery for a while, so short outages rarely lose data. For scenarios you rely on, make every run safe to repeat, so a retry does not create a record twice. Add a daily reconciliation scenario that compares Pipedrive with the other tool and catches anything that slipped through. That costs little and covers longer outages too.
Can Make.com handle our marketing automation handoff after migrating from HubSpot?
Yes. A common pattern: your marketing tool, such as Encharge, ActiveCampaign or Customer.io, sends a webhook to Make when a lead qualifies. Make creates the person and the deal in Pipedrive, applies your routing rules and notifies the owner. The trade-off is that you work in three tools instead of one, so agree up front which tool owns which field.
Do I need a Make Certified Partner to set this up?
For the first scenario or two, no, because the Make documentation is good. For production setups with error handling, monitoring, a credit budget and five or more scenarios, a partner usually pays off by avoiding silent failures. Sales Surge is a Make Certified Partner 2025 and a Pipedrive Platinum Partner. Make workflows start at €750 on our pricing page.
