Pipedrive automation services for B2B sales teams

    We build Pipedrive workflow automations, with Make.com where Pipedrive stops, so follow-up and tasks run without anyone keeping track.

    Price
    From €2,200
    Invoicing
    Per phase, in advance

    Pipedrive Platinum PartnerPipedrive Platinum Partner

    For teams who recognise this

    • Reps log every activity and every next step by hand.
    • A deal sits still for three weeks and nobody gets a nudge.
    • After a deal is won, someone emails finance to send the invoice.
    • Someone built automations once, and nobody knows anymore what they do.

    What you get

    • Follow-up emails from Pipedrive
    • Tasks at every stage
    • Nudges when deals stall
    • Integrations through Make.com
    • A map of every automation

    What it delivered

    6 hours

    saved per person per week

    Every form submission becomes a deal by itself, with one call task that is due within 2 hours.

    Ontslagrecht Juristen Nederland, employment law

    What we build

    • Follow-up emails from Pipedrive

      An email from the deal owner's inbox, which stops as soon as the prospect replies.

    • Tasks at every stage

      Every stage creates the tasks that belong to it, with a fixed due date.

    • Nudges when deals stall

      When a deal stays in one stage too long, the owner gets a notification.

    • Integrations through Make.com

      Where Pipedrive stops, Make.com connects it to your quoting tool or your accounting.

    • A map of every automation

      Per automation: trigger, conditions, action and owner, so your team can still read it in a year.

    How it runs

    1. Audit

      In the first week you see the list of what we will build, and what we switch off, before anything gets built.

    2. Build

      We build the flows in Pipedrive and, where needed, in Make.com.

    3. Test

      We test with test deals and real examples, so no email goes to the wrong customer.

    4. Training

      Your team gets an explanation on its own pipeline. You also get the overview of every flow.

    What this did for a client

    Great experience

    “Bart really understood our needs and helped us improve our Pipedrive setup and automations in a practical and efficient way. Communication was always easy and quick, and he was very helpful throughout the process.”

    Inge Kleijkamp

    The Eyden Berg, Sep 2026

    Review on the Pipedrive Marketplace
    Pipedrive Platinum Partner

    Pipedrive Platinum Partner

    View partner profile

    Price

    What it costs

    From €2,200

    A project takes 2 to 3 weeks. At the time of writing, Pipedrive's workflow automation is available from the Growth plan; Make.com is added when you need it.

    To be honest

    When this is not the first step

    When your stages do not add up, you automate a process that already runs crooked. Then we start with setting up your pipeline.

    What can Pipedrive automations do natively?

    Pipedrive automations do a lot without any extra tool: they react to an event or a date in Pipedrive, check conditions, and then update records, create activities or send an email. Everything below comes from Pipedrive's own support article on workflow automation, which we read on 16 November 2026.

    An automation has three parts. A trigger starts it. A condition decides whether it continues. An action does the work. You can chain several actions, split the flow with if/else conditions and let it wait until a condition is met or an event happens.

    PartWhat Pipedrive offers natively
    Event triggersA deal, person, activity, lead, organisation or project is added, updated or deleted
    Date triggersA date field on a deal, person, activity or organisation, such as an expected close date or a contract end date
    ConditionsFilters on fields, if/else branches, and wait steps until a condition or event
    Actions on recordsCreate or update deals, persons, organisations, leads, activities, notes and projects
    CommunicationSend an email from Pipedrive, add someone to a campaign
    Outside PipedriveWebhooks, plus Slack, Microsoft Teams, Trello and Asana

    Two limits to know. At the time of writing, workflow automation is only available on the Growth plan and higher, so check your plan before you plan anything. And an automation that creates a deal fails at that step when you have reached your open deal limit. Plan names and limits change, so check Pipedrive's support page for the current state. For a wider view on what AI adds inside Pipedrive, read our guide on Pipedrive AI automation.

    When do you need Make.com on top?

    You need Make.com when a workflow has to read from or write to another system with more logic than a webhook gives you. As long as a flow starts and ends in Pipedrive, native is enough, and cheaper. We are a Make.com Certified Partner, and we still do not put anything in Make that Pipedrive can do itself. That only costs you an extra subscription.

    Use caseBest tool
    Stage changes, follow-up, internal tasksPipedrive native
    Conditional logic on deal fieldsPipedrive native
    A short email from a deal stagePipedrive native
    A simple notification in Slack or TeamsPipedrive native
    Filling a quote template and reacting to the signatureMake.com
    Creating an invoice in your accounting softwareMake.com
    Enrichment, API calls, data from several systems in one messageMake.com
    Sync to a data warehouse or an external dashboardMake.com

    Three examples where we add Make.com.

    Quote. When a deal reaches the proposal stage, Make.com fills a quote template from the deal fields, in Pipedrive Smart Docs or PandaDoc. When the customer signs, the deal moves to won on its own.

    Accounting. When a deal is won, Make.com creates the customer and a draft invoice in your accounting software, with the products from the deal. Finance checks and sends. Nobody retypes amounts.

    Slack. Pipedrive can post a message in Slack itself. Make.com comes in when that message needs data from several places, for example the deal value, the last email and the open invoices of that customer. More on the combination in our guide to Make and Pipedrive and on our Make.com page.

    The 10 Pipedrive automations we build most often

    These are the ten Pipedrive automations we build most often, with the trigger and the action. Not every team needs all ten.

    #AutomationTriggerAction
    1Owner for every new leadLead or deal addedAssign an owner in turn or by region, create a call task for today
    2Confirmation to the leadDeal added from a web formSend a short email from the owner's inbox
    3Tasks per stageDeal moves to a stageCreate the tasks that belong to that stage, with a due date
    4Follow-up after a meetingMeeting activity marked doneCreate a follow-up task for two working days later
    5Stalled deal alertDeal has had no activity for a set number of daysNotify the owner, and the manager after a second period
    6No next stepDeal has no open activityCreate a task asking the owner to plan the next step
    7Proposal reminderDeal in the proposal stage for a set number of daysCreate a call task and send a reminder email
    8Won deal handoverDeal marked wonCreate a project or onboarding activity and notify delivery
    9Lost deal reasonDeal marked lostCreate a task to fill in the lost reason and a nurture follow-up date
    10Renewal dateDate trigger on contract end dateCreate a renewal deal and a task a set time before the date

    In audits we mostly see number 6 missing. A deal without a next activity is a deal nobody is working on, and Pipedrive does not tell you that by itself. For the broader picture of what you can automate in sales, outside Pipedrive too, see sales automation. Twelve recipes with trigger and action are in our guide sales automation for B2B.

    How do you keep automations from breaking?

    You keep automations working by giving each one a clear entry, a clear exit, an owner and a written description. In broken setups we audit, the same causes come back: two automations that react to the same trigger, emails that keep going after a reply, and nobody who knows why a flow exists.

    • Entry condition. Every automation has a filter that says exactly which records it applies to, for example only deals in pipeline Sales and not the test pipeline.
    • Exit condition. Every email flow stops when the person replies, when a meeting is booked or when the deal changes stage.
    • One trigger, one owner. When two automations react to the same change, they get merged or they get clearly separated conditions.
    • Failure notice. Make.com scenarios send a message to a named person when a run fails, so a broken integration does not go unnoticed for weeks.
    • Documentation. A list of every automation with trigger, conditions, action, owner and the date it was last changed. Your team gets that list at handover.
    • Test before go-live. We test with test deals and with a copy of real examples, never by sending emails to real customers.

    Taking over automations someone else built? We start with an audit, switch off what works against each other, and only then build new ones.

    What does Pipedrive automation cost?

    Pipedrive automation costs from €2,200 and takes 2 to 3 weeks. That is one price, not a set of packages. Up front you get the list of what we build and the price per phase, and you pay each phase before it starts. Your Pipedrive plan and, when needed, a Make.com subscription come on top.

    Want to know what it saves you? Fill in your own numbers rather than trusting ours:

    1. Count the hours per week one rep spends on admin that follows a rule: logging, follow-up emails, tasks, handovers.
    2. Multiply by the number of reps.
    3. Multiply by what an hour of a rep costs you.
    4. Multiply by the number of working weeks in a year.
    5. Then estimate honestly which part of those hours an automation takes over. In the audit we count that per step.

    That last estimate is the one that matters, and it differs per team. That is why we count it in the first week instead of putting a percentage on this page. Not set up in Pipedrive yet? Then start with a Pipedrive implementation.

    Trial through our partner link

    Try Pipedrive free for 30 days

    Our partner link gives you 30 days instead of the usual 14.

    That is because we are a Pipedrive Platinum Partner. You get full access and you do not need a credit card. When the trial ends, you decide whether to take a subscription.

    • 30 days instead of 14
    • Every feature included
    • No credit card needed

    Trial

    30 days free

    The link opens the Pipedrive sign-up page.

    Start your trial

    The trial starts straight away through the partner link.

    In short

    Pipedrive automation, in short

    Pipedrive automations are rules inside Pipedrive: when a deal, person, lead or activity changes, something happens, such as a task, an email or a field update. We set them up, and add Make.com where a workflow crosses into other systems. We are a Pipedrive Platinum Partner. A project costs from €2,200 and is live in 2 to 3 weeks.

    Source: Sales Surge price list, checked on 16 November 2026. Prices exclude VAT.

    Frequently asked questions about Pipedrive automation

    Can Pipedrive send follow-up emails automatically?

    Yes. A Pipedrive automation can send an email when a deal changes stage, when a date comes up or when a record matches a filter. We set these up so the email comes from the deal owner's inbox, uses fields like name and company, and stops when the prospect replies. For longer sequences with branches across email and LinkedIn, we add Instantly or Make.com and trigger them from a stage change.

    What happens when Pipedrive changes a feature?

    Pipedrive adjusts its automations and plans from time to time. Usually you notice nothing, but a trigger or action can start to behave differently or move to another plan. That is why every automation is on the list you get at handover, with its trigger, conditions and action: you see quickly what is affected. During hypercare we keep an eye on that ourselves, and after that it can be part of a retainer.

    Which Pipedrive plan do you need for workflow automation?

    At the time of writing, Pipedrive's support article says workflow automation is available on the Growth plan and higher. Plan names and limits change, so check the current plan page before you start. In the intake we look at your plan first. Sometimes an upgrade is cheaper than building the same thing in Make.com, and sometimes it is the other way around.

    How long does it take to set up Pipedrive workflow automation?

    A project takes 2 to 3 weeks. The first week is the audit, so you see the list of what we build and what we switch off before anything is built. Then we build, test with test deals and train your team on its own pipeline. We work in your live Pipedrive account, so your team keeps working while we build.

    Do I need a developer to automate Pipedrive?

    No. Pipedrive's automations are built without code and Make.com has a visual builder, so most sales workflows need no developer. What you do need is someone who understands your sales process and sees where an automation creates new problems, such as two flows reacting to the same change. That is the part we do. Where custom API logic is needed, we write it ourselves.

    Can we change the automations ourselves later?

    Yes. Everything is in your own Pipedrive account, so you can get to it yourself. At handover we show how to change a condition or an email text without knocking over another flow. When you change a trigger, add the date and the reason to the list of automations, so you still know why a year from now. When a change touches several flows at once, it is worth having someone look over it first.

    See what your team can automate

    The free growth scan shows within 48 hours which manual work your team can drop.