Sales Surge
    SALES SURGEAlign•Automate•Accelerate
    Automation1-2 days for the first scenarios setup time

    Make.com + Pipedrive Integration Guide 2026

    The automation layer that turns Pipedrive into a real revenue engine. Webhooks, scenarios, and zero-code workflows by a Make Certified Partner.

    TL;DR

    • Make.com is the automation layer Pipedrive needs once you outgrow native workflow automations
    • Cheaper, more flexible, and more reliable than Zapier for any non-trivial CRM workflow
    • Production setup takes 1-2 days for your first 3-5 scenarios, then days per new scenario
    • Replaces what HubSpot Operations Hub does for roughly 10 percent of the cost
    • Use Make for cross-tool flows. Use native Pipedrive automations for in-CRM logic. Mixing them is the most common mistake.
    Setup time
    1-2 days for the first scenarios
    Sync direction
    Bi-directional, event-driven
    ROI
    60-80% lower cost than custom development

    Why Make.com + Pipedrive: the automation layer

    Pipedrive's native workflow automation is excellent for in-CRM logic: move a deal, create a task, send a templated email, notify an owner. Where it stops is the moment your workflow needs to talk to another tool. Lead enrichment, calendar booking, proposal generation, invoicing, Slack notifications, dashboard refreshes, marketing automation handoff, every one of these lives outside Pipedrive.

    Make.com (formerly Integromat) is the visual automation platform that fills that gap. It connects 1,500+ apps, listens to Pipedrive webhooks in real time, and lets you build conditional, multi-step scenarios without writing code. For B2B sales teams, Make plus Pipedrive replaces what HubSpot Operations Hub does at roughly one tenth of the cost. We use Make on every Pipedrive RevOps stack we build.

    This guide covers what we have learned across 150+ B2B Pipedrive implementations: when Make is the right tool, when it is not, the 10 scenarios that pay back fastest, how to use webhooks correctly, error handling, cost math, and the mistakes that cause Make scenarios to silently break in production.

    Make vs Zapier for Pipedrive Users

    Lower cost at scale

    Make charges per operation, not per task. A Pipedrive scenario with 5 steps that runs 1,000 times a month costs roughly 1/3 of the Zapier equivalent.

    Up to 70% cheaper than Zapier

    Real conditional logic and routers

    Make's visual router and filter modules let you branch a single trigger into multiple paths. Zapier requires you to duplicate the whole Zap to get equivalent logic.

    1 scenario vs 4-5 Zaps

    Native iterators and aggregators

    Loop through arrays from the Pipedrive API, batch updates, and aggregate results in one scenario. Zapier needs paid add-ons or external code steps for this.

    Built in, no add-ons

    Better error handling

    Per-module error handlers, retry rules, and rollback logic are first-class in Make. Zapier's error handling stops at 'retry the whole Zap'.

    Granular retries

    What Most Make.com + Pipedrive Builds Get Wrong

    We have rebuilt dozens of Make.com setups that worked on day one and silently broke by month three. Five patterns explain almost all the failures:

    Mistake #1: Polling Pipedrive every 5 minutes instead of using webhooks

    Consequence:

    You burn 8,000+ Make operations per month on 'has anything changed?' polls. Worst of both worlds: high cost AND delayed reactions. Real-time scenarios behave like batch jobs.

    How to Fix It:

    Use Pipedrive webhooks for every event-driven scenario (deal created, stage changed, person updated). Reserve polling for snapshot reports that genuinely need a schedule, like a daily forecast 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, and the next 47 deal updates queue up forever or get silently dropped. You find out two weeks later when a customer asks why their deal is still in 'Negotiation'.

    How to Fix It:

    Add an error handler route to every external API call: log to a Google Sheet or admin Slack channel, set a 'Sync Failed' flag in Pipedrive, and route to a retry queue. Never let a scenario fail silently.

    Mistake #3: Triggering on every Pipedrive update instead of filtering early

    Consequence:

    A 'deal updated' webhook fires every time anyone touches a deal. If you filter inside Pipedrive only after running 4 modules, you pay for 4 ops on every irrelevant change. At scale, this is the single biggest cost driver.

    How to Fix It:

    Put a Filter module immediately after the trigger. Only proceed if the change matches your business condition (stage moved to X, value above Y, owner equals Z). Operations saved compound fast.

    Mistake #4: Hardcoding Pipedrive IDs (pipeline, stage, user) into modules

    Consequence:

    Six months later, sales adds a new stage. Every scenario referencing the old stage IDs breaks at the same time. Hours of debugging to find out why three workflows stopped on the same Tuesday.

    How to Fix It:

    Store IDs in a Make data store or a Pipedrive-side mapping table. Reference by name in the scenario, resolve to ID at runtime. New stages do not break existing flows.

    Mistake #5: Building one massive scenario that handles 10 things

    Consequence:

    Mega-scenarios become unfixable. Any change risks breaking unrelated logic. Debugging means scrolling through 40 modules. New team members cannot maintain it.

    How to Fix It:

    One scenario per business outcome. Use Make's 'Webhook Response' or 'Run Scenario' modules to chain when needed. Each scenario should fit on one screen and have one clear job.

    Expert Insight from Sander Vergouwen

    "The cheapest Make plan we run for clients is 9 USD per month. The most expensive is 299 USD. The difference is not feature use, it is scenario discipline. Clients with clean, filtered, webhook-driven scenarios stay cheap forever. Clients with sprawling polling-based scenarios end up on the Pro tier within 6 months and still complain about delays. Architecture beats plan tier every time."

    Setup: Connecting Make to Pipedrive (and Webhooks Deep Dive)

    Prerequisites

    • Make.com account (Free tier works for testing, Core or Pro for production)
    • Pipedrive account with admin access (any paid plan)
    • An admin Slack or email channel for error notifications
    • A documented list of business events you want to automate (do this BEFORE building)
    1

    Connect the Pipedrive app in Make

    In Make, add a Pipedrive module. Authenticate via API token (Pipedrive: Personal preferences, API). Use a dedicated 'Make Integration' user, not a real rep, so audit trails stay clean.

    Tool: Make.com + Pipedrive
    2

    Choose webhook over polling whenever possible

    Pipedrive supports webhooks for almost every entity (deal, person, organisation, activity, note). In Make, use the 'Watch Deals' (Instant) trigger, not the scheduled one. Make auto-creates the webhook in Pipedrive for you.

    Tool: Make.com
    3

    Filter immediately after the trigger

    Add a Filter module right after the webhook. Only let through events that match your business condition. Example: 'Stage = Won' or 'Value > 5000'. This is the single biggest cost lever.

    Tool: Make.com
    4

    Map IDs through a lookup, never hardcode

    Create a Make data store or a Google Sheet with Pipeline, Stage, and User name-to-ID mappings. Reference by name in scenarios, resolve to ID at runtime. Future-proof against renames.

    Tool: Make data store / Sheet
    5

    Add error handlers to every external API call

    Right-click each module, add an error handler route. Log the error to a 'Make Errors' Pipedrive activity, Google Sheet, or Slack channel. Never silently fail.

    Tool: Make.com
    6

    Test with a sandbox deal before turning the scenario on

    Create one test deal in Pipedrive. Run the scenario manually. Verify outcomes in Pipedrive, the third-party tool, and the error log. Only then enable the scenario.

    Tool: Pipedrive + Make.com
    7

    Monitor scenario health weekly

    In Make, set up email notifications for scenario failures. Check the History tab weekly for slow-running scenarios (over 30 seconds usually means too many polling calls).

    Tool: Make.com

    Verification

    • Trigger the scenario with a test deal and confirm the action fires within 60 seconds
    • Force an error (bad data, disconnected app) and confirm the error handler logs it
    • Update an irrelevant field on the test deal and confirm the filter rejects it
    • Check Pipedrive activity log to confirm the Make user is the one performing actions
    • Verify cost: check Make 'Operations used' before and after a 24-hour run

    Top 10 Make.com + Pipedrive Automation Scenarios

    1. Lead enrichment on deal creation

    New deal? Auto-pull company data from Apollo, Lusha, or Clarbit and write it back to the related organisation.

    1. 1Trigger: Pipedrive 'Watch Deals' (instant, on create)
    2. 2Filter: Organisation has email or domain present
    3. 3Apollo / Lusha module: Enrich by domain
    4. 4Filter: Update only empty Pipedrive fields
    5. 5Pipedrive: Update Organisation with industry, headcount, tech stack
    6. 6Error handler: log failures to 'Enrichment Errors' Sheet

    2. Stage transition notifications to Slack

    Deal moves to Negotiation or Won? Post a formatted message in the relevant Slack channel for the owner and manager.

    1. 1Trigger: Pipedrive 'Watch Deals' (on update)
    2. 2Filter: Stage changed AND new stage in [Negotiation, Won]
    3. 3Pipedrive: Get owner details
    4. 4Slack: Post message with deal name, value, owner, link
    5. 5Slack: Tag the manager if value above threshold

    3. Auto-create contacts from form submissions

    Webform, Typeform, or Tally submission becomes a Pipedrive Person and Deal in seconds, with deduplication.

    1. 1Trigger: Form webhook into Make
    2. 2Pipedrive: Search Person by email
    3. 3Router: existing Person update vs create new
    4. 4Pipedrive: Create or update Person and link Organisation
    5. 5Pipedrive: Create Deal in 'Inbound' pipeline at Stage 1
    6. 6Slack: Notify the assigned SDR

    4. Sync deals to invoicing systems

    Deal won? Push to Moneybird, Exact, Xero, or QuickBooks as a draft invoice with line items pre-filled from custom fields.

    1. 1Trigger: Pipedrive 'Watch Deals' (on stage = Won)
    2. 2Pipedrive: Get deal products and contact details
    3. 3Mapping: Convert Pipedrive products to invoice line items
    4. 4Invoicing app: Create draft invoice, attach customer
    5. 5Pipedrive: Write invoice URL back to deal as a custom field
    6. 6Slack: Notify finance with invoice link

    5. LinkedIn data enrichment

    Pull LinkedIn profile and company data via PhantomBuster, Lix, or Bright Data into the Pipedrive Person record.

    1. 1Trigger: Pipedrive 'Watch Persons' (on create)
    2. 2Filter: LinkedIn URL field is filled
    3. 3PhantomBuster / Lix: Scrape LinkedIn profile
    4. 4Parse: extract title, company, headcount, industry
    5. 5Pipedrive: Update empty fields only
    6. 6Tag enrichment status for audit

    6. Email parsing into Pipedrive

    Inbound prospect emails to a shared inbox get parsed and turned into Pipedrive activities or deals automatically.

    1. 1Trigger: Email Parser webhook (Make's built-in)
    2. 2AI module: Extract sender intent, deal value, requested timeline
    3. 3Pipedrive: Search for existing Person
    4. 4Router: Create new Lead or attach activity to existing deal
    5. 5Pipedrive: Set follow-up activity for the right owner

    7. Activity reminders via WhatsApp

    Reps get WhatsApp notifications for high-priority activities or stale deals, without relying on email.

    1. 1Schedule: Run every weekday at 08:30
    2. 2Pipedrive: Search activities due today, owned by active reps
    3. 3Iterator: Loop through activities
    4. 4WhatsApp Cloud API or Twilio: Send formatted reminder
    5. 5Pipedrive: Log a note that reminder was sent

    8. Dashboard refresh triggers

    Push Pipedrive data to Looker Studio, Power BI, or Google Sheets in real time so dashboards stay fresh without manual refresh.

    1. 1Trigger: Pipedrive 'Watch Deals' (on any change)
    2. 2Filter: Significant fields changed (value, stage, close date)
    3. 3Make data store or Google Sheet: Update the row for that deal
    4. 4BI tool reads live from the sheet or data store
    5. 5Optional: Trigger Looker Studio refresh API

    9. Multi-tool data sync

    Keep Pipedrive, your marketing automation tool (Encharge, ActiveCampaign, Customer.io), and your support tool (Intercom, Help Scout) in sync without dual entry.

    1. 1Trigger: Webhook from any of the three tools
    2. 2Router: branch by source
    3. 3Per branch: lookup matching record in the other tools by email
    4. 4Update only delta fields (avoid loops)
    5. 5Throttle module: Prevent infinite update loops

    10. Conditional follow-ups

    Open deal with no activity for 7 days? Auto-create a follow-up task. No reply for 14? Escalate to the manager.

    1. 1Schedule: Daily run at 06:00
    2. 2Pipedrive: Search open deals with no activity in last 7 days
    3. 3Router: 7-14 days vs 14+ days
    4. 47-14: Create follow-up activity for the owner
    5. 514+: Create activity for the manager and Slack notify
    6. 6Pipedrive: Log scenario action as a note for transparency

    FAQ

    How much does Make.com cost for a typical Pipedrive setup?

    Most B2B teams of 5-30 reps run on Make's Core plan at 9 USD per month (10,000 ops) or Pro at 16 USD per month (10,000 ops + advanced features). Larger teams running enrichment and full sync usually need 30,000-100,000 ops per month, which lands at 16-50 USD. Roughly 10 percent of what HubSpot Operations Hub costs for the same automation depth.

    Should I use Make.com or Pipedrive's native workflow automation?

    Use native Pipedrive automations for anything that lives entirely inside Pipedrive: stage-change tasks, owner assignment, follow-up reminders, internal notifications. Use Make for anything that crosses tools: enrichment, invoicing, WhatsApp, calendar sync, multi-tool data flow. The mistake is using Make for in-CRM logic (slower and costlier) or using Pipedrive automations to call external APIs (limited and brittle).

    Make.com vs Zapier, which is better for Pipedrive?

    Make for any serious Pipedrive setup. It is cheaper at scale, has real conditional logic and routers, and handles arrays natively. Zapier is fine for 1-step 'when X happens, do Y' flows. The moment you need branching, batching, or error handling, Make pulls ahead by a wide margin.

    How do Pipedrive webhooks work with Make?

    When you add a 'Watch Deals' (instant) trigger in Make, it auto-creates a webhook in your Pipedrive account pointing at a unique Make URL. Pipedrive then POSTs every matching event to that URL in real time, usually within 1-2 seconds. You can see the webhook in Pipedrive under Settings > Tools and apps > Webhooks.

    What happens if Make.com is down?

    Pipedrive will retry webhook deliveries for several hours. For critical scenarios, build idempotency (so re-runs do not double-create records) and consider a daily reconciliation scenario that catches any missed events. In 5+ years running Make in production we have never seen more than 30 minutes of downtime, but planning for it is cheap.

    Can Make.com handle our marketing automation handoff after migrating from HubSpot?

    Yes. The most common pattern is: marketing tool (Encharge, ActiveCampaign, Customer.io) sends a 'Lead Qualified' webhook to Make, which then creates the Pipedrive Person and Deal, applies routing logic, and notifies the owner. We replace HubSpot Sales Hub plus Operations Hub with Pipedrive plus Make plus a marketing tool for roughly 30 percent of the original bill.

    Do I need a Make Certified Partner to set this up?

    For the first scenario or two, no. The Make documentation is excellent. For production setups with error handling, monitoring, cost optimisation, and 5+ scenarios, a partner pays for itself within months by avoiding silent failures and runaway operation costs. Sales Surge is a Make Certified Partner and a Pipedrive Platinum Partner, which means we own both sides of the integration.

    Make.com vs Alternatives

    Zapier

    Pros

    • Easier learning curve for non-technical users
    • More native app integrations available
    • Better for 1-step workflows

    Cons

    • 3-5x more expensive at scale
    • Weak conditional logic
    • No native iterators or routers without Paths add-on
    Best for:Marketing teams running simple 1-step flows, or solopreneurs

    n8n (self-hosted)

    Pros

    • Self-hosted, full data control (GDPR friendly)
    • Open source
    • No per-operation cost

    Cons

    • Requires DevOps to host and maintain
    • Smaller app ecosystem than Make
    • No managed reliability
    Best for:Engineering-heavy teams with strict data residency requirements

    Custom code (Node.js + Pipedrive API)

    Pros

    • Maximum flexibility
    • No per-op costs
    • Can be integrated into existing apps

    Cons

    • Months of dev time vs days in Make
    • Maintenance burden falls on engineering
    • No visual debugging
    Best for:Product companies embedding Pipedrive logic into their own SaaS

    Want a Make Certified Partner to Build This for You?

    Sales Surge is both a Pipedrive Platinum Partner and a Make Certified Partner. We have built 150+ Make scenarios on top of Pipedrive across 50+ B2B clients. Book a call to scope your automation roadmap.

    Related reading

    Back to the knowledge hub

    Related guides

    Go deeper into adjacent topics.

    Pipedrive Guide

    Pipeline design, automation, integrations and reporting.

    View

    RevOps Guide

    Aligning sales, marketing and customer success.

    View

    Outbound Sales Guide

    Stack, cadences and playbooks for predictable outbound.

    View