Make.com Certified Partner

    Make.com partner for your Pipedrive integrations

    We build Make scenarios between Pipedrive and your other tools, and document them so your team can change them later.

    • Make.com Certified Partner since 2025
    • 17 Make organisations across eu1, eu2 and us2
    • 67 active scenarios at Vita Brevis Fine Art

    What we build in Make

    • Agreements before the build

      We write down which system is the source of truth and which fields nothing overwrites automatically.

    • Scenarios around Pipedrive

      We connect Pipedrive to your ads, accounting or project tool, so nobody retypes data by hand.

    • A review of what already runs

      If something already runs in Make or Zapier, we go through it first. Whatever stays becomes part of the design.

    • Versions and handover

      We work with versions and document every scenario. Someone who was not there can read and change it.

    In short

    Make.com partner, in short

    Sales Surge has been a Make.com Certified Partner since 2025. We build scenarios between Pipedrive and your ads, project tool, accounting and data sources. First we agree which system is the source of truth. Then we build, with logging and a named owner for every scenario. Setup falls under sales automation, from €2,200 in 2 to 3 weeks.

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

    Price

    What a Make project costs

    From €2,200

    2 to 3 weeks

    That is the price of our sales automation project. The Make scenarios around Pipedrive are part of it.

    See all prices

    To be honest

    When Zapier or n8n fits better

    If you have two small integrations that stay small, Zapier is cheaper. Then we are too much. If you want to host and run everything yourself, n8n fits better.

    Five Make scenarios we build around Pipedrive

    These are the five scenarios we build most often. For each one: what starts it, what it does, what goes wrong in real accounts and how we catch it. You can also read them as a checklist for scenarios you already run.

    Five Make scenarios we build around Pipedrive
    ScenarioTrigger and stepsWhat goes wrongHow we catch it
    Ad leads into the right pipelineA lead form from Meta or LinkedIn comes in. Make looks up the person and organisation, creates them if they are new and adds a deal to the pipeline that belongs to the campaign.Every lead becomes a new person, even when they already exist. Field names differ per form.Search on email first, create second. One field mapping per form, and an empty value falls back to a default.
    A won deal creates a project in AsanaA deal moves to won. Make picks the project template from the deal type and copies scope, contact and agreed dates into the project.Someone marks the deal won twice and you get two projects.The project ID is written back to a field on the deal. If that field is filled, the scenario creates nothing new.
    Invoice status from accounting back to the dealYour accounting tool reports a paid or overdue invoice. Make finds the deal by invoice number and writes status and date into Pipedrive.The invoice number is missing or wrong on the deal, so Make finds nothing.The number is written to the deal when the invoice is created. If Make finds no deal, the owner gets an alert instead of silence.
    Apollo enrichment for new organisationsA new organisation lands in Pipedrive. Make asks Apollo for data on the domain and fills only the fields Apollo is allowed to fill.Apollo overwrites what a rep typed in, or fills a field with noise.Rules per field: Apollo may fill empty fields, filled fields stay with people. A source field shows what came from Apollo.
    Cold email replies become deals in PipedriveSomeone replies to an Instantly email. Make creates a deal in Pipedrive with the email attached and a follow-up task for the owner.An out-of-office reply becomes a deal too, and the pipeline fills with noise.Only replies with a real status pass through. The rest stays in Instantly, and the sequence stops on any reply.

    How the connection works under the hood, with webhooks and the pitfalls per module, is in our guide connecting Make and Pipedrive. Which integrations you can set up without Make is on Pipedrive integrations.

    Make across many clients: how we work

    We work across 17 Make organisations, spread over the eu1, eu2 and us2 zones. That only works with fixed rules, because scenarios without an owner break without anyone noticing.

    These are the rules we keep in every organisation:

    • We keep data from different clients apart, in the zone that fits that data. Data and permissions do not mix.
    • Every scenario has one named owner. That person gets the error alerts and decides on changes.
    • We work with versions. Before a change we save the current blueprint, so we can roll back if something breaks.
    • Every scenario logs errors together with the record. An error without context cannot be fixed.
    • After every change to a webhook scenario we test it on a real run. A green tick in the editor proves nothing.
    • Scenarios nobody uses get switched off. Whatever runs is documented.

    After handover comes a hypercare period. Then you run the scenarios yourself or leave them with us on a retainer. Both work, and the written description per scenario is what makes the first option real.

    In practice: 67 Make scenarios at Vita Brevis Fine Art

    At Vita Brevis Fine Art, a portrait studio in Colorado Springs, we replaced Zapier with Make. We rebuilt the flows instead of copying them one to one. On 12 October 2026 there were 67 active Make scenarios.

    The bookers never see any of it, which is the point. The scenarios keep the deal, the studio's own apps inside Pipedrive, the calling campaigns and the reporting in line. The full story, from more than 70 pipelines down to 3, is in the Vita Brevis Fine Art case.

    Hiring a Make.com consultant: what it costs

    A Make project starts from €2,200 and takes 2 to 3 weeks. That is the price of our sales automation project, and the scenarios around Pipedrive are part of it. If Make is part of a full RevOps implementation, it falls under that price, from €9,500.

    Three things decide where you land: the number of scenarios, the number of systems involved and whether existing scenarios need cleaning up first. After the first call you get a fixed price per phase. Each phase is invoiced before it starts.

    Two costs are not included. You take out the Make subscription yourself, ideally through our partner link. And running the scenarios after hypercare is a separate choice. That can be a retainer, and you hear its price in the call.

    Frequently asked questions about Make.com

    What does a Make.com consultant at Sales Surge actually do?

    We start with your process, not the tool. First we agree which system is the source of truth and which fields stay with people. Then we build the scenarios and test them on your own records. At handover you get a written description per scenario, so someone who was not there can change it later.

    What does a Make.com partner cost?

    Setup falls under our sales automation project. It starts from €2,200 and takes 2 to 3 weeks. Where you land depends on the number of scenarios and systems. The Make subscription itself you take out with Make. Running the scenarios after handover can sit in a retainer, but that is optional.

    Where does Make sit between Pipedrive and your other tools?

    Make is the layer that passes events along. Pipedrive stays the place where deals and contacts live. Make listens to a webhook from Pipedrive, a form or your accounting tool, then sends the data to the system that needs it. Pipedrive keeps the overview, and nobody copies data between two screens.

    Why do you pick Make over Zapier?

    Make stays readable once a flow has more than a few steps. You see every step, you can catch an error per step and you can split a route on a condition. If you have two small integrations and that will not change, Zapier is cheaper and quicker to set up. We will tell you so.

    Can you take over scenarios someone else built?

    Yes, and we start with an audit. We go through every scenario: what triggers it, what it writes, who owns it and what happens on an error. Scenarios nobody uses get switched off. What stays gets a description. Taking over without knowing what runs is how things break, so we never skip that step.

    What happens when a Make scenario fails?

    That depends on the kind of error. If a system is briefly unreachable, the scenario retries later. If the data is wrong, it stops before it writes half of it, and an alert goes out with the record it was about. You see the error on the day it happens, not when a client calls.

    Have your Pipedrive integrations built in Make

    You hear what we would build and what it costs.