Apollo Pipedrive integration: how to set it up right

    How to let Apollo.io fill Pipedrive with verified data. Without burning credits and without overwriting what your reps typed.
    EnrichmentSander VergouwenUpdated: 16 November 2026

    In short

    You connect Apollo.io to Pipedrive in one of two ways. Apollo's native integration syncs contacts and accounts with field mapping. To fill only empty fields and enrich once when a lead is created, you need a Make.com scenario. Make also adds error handling and a log. A clean setup takes 2 to 4 hours.

    Source: Sales Surge, Apollo Fully Certified partner, from our own Apollo and Pipedrive buildsAs of: 16 November 2026

    In this article
    1. What is Apollo.io?
    2. Apollo or Pipedrive: what is the difference?
    3. Why connect Apollo.io to Pipedrive
    4. Native integration or Make: an honest comparison
    5. The five mistakes we see most in Apollo integrations
    6. Connecting Apollo to Pipedrive step by step
    7. Workflows we run in production
    8. What does Apollo enrichment cost per month?
    9. Apollo and GDPR
    10. Apollo next to the alternatives
    11. FAQ
    Setup time
    2 to 4 hours
    Sync direction
    From Apollo to Pipedrive

    What is Apollo.io?

    Apollo.io is a sales intelligence platform. It combines a database of 275M+ contacts with enrichment and sequences, plus intent data.

    For a RevOps team, Apollo does two jobs. It finds new leads that match your ICP. And it adds a verified email, phone number, job title and company data to the contacts you already have. Your CRM gets fuller without anyone typing.

    What Apollo does not do is decide who you want to talk to. And it will not find everyone. As a rule of thumb, expect 15 to 20 percent of B2B emails to be missing, and more in European or niche segments. That is normal, and your setup has to handle it.

    Apollo or Pipedrive: what is the difference?

    Apollo is where you find and enrich people. Pipedrive is where you sell to them. Apollo has its own CRM features and sequences. But in a Pipedrive team it works best as the data and prospecting layer, with Pipedrive as the system of record.

    The question usually comes up when a team notices that Apollo also has deals, tasks and a pipeline view. That overlap is real. A small team that only does outbound can run everything in Apollo for a while. Once inbound leads, quotes, renewals or a second team come in, Pipedrive takes over. That is where the pipeline, the products and the reporting live.

    ApolloPipedrive
    Main jobFinding and enriching contacts, sending sequencesManaging deals, activities and the pipeline
    DataA B2B database of 275M+ contactsYour own customers, deals and history
    EmailSequences for cold outreachOne to one email and templates
    ReportingProspecting and sequence activityPipeline, forecast and win rates
    Who works in itSDRs and growthThe whole sales team and management

    For where Apollo fits in a full outbound setup, read the outbound guide. How we work with Apollo as a certified partner is on the Apollo page.

    Why connect Apollo.io to Pipedrive

    The integration is worth it when a lead arrives in Pipedrive with nothing more than a name and an email.

    • Context before the first call. A new lead in Pipedrive gets company size, industry, tech stack and funding data before a rep picks up the phone.
    • Verified addresses. Apollo checks the email address, so invalid addresses stay out of your sequences and your domain reputation stays intact.
    • ICP scoring without manual work. With the enriched fields you score each lead against your Ideal Customer Profile on data instead of gut feeling.

    Native integration or Make: an honest comparison

    Apollo has its own Pipedrive integration, and for many teams it is enough. At the time of writing it syncs contacts and accounts, maps the standard fields automatically and lets you add custom fields. You can also map Pipedrive statuses to Apollo stages and limit which stages are pushed. It does not write activities such as emails, calls or sequence steps into Pipedrive.

    Make.com is the route when you need rules per field. Check the current feature list in the Apollo help center and the Pipedrive Marketplace before you decide, because it changes.

    Apollo native integrationMake.com scenario
    What syncsContacts and accountsWhatever you build: persons, organisations, deals, notes
    Field rulesField mapping, plus a choice of which stages are pushedPer field: always update, only when empty, or never
    NormalisationValues arrive the way Apollo has themA mapping table to your picklists before anything is written
    Activities in PipedriveNot syncedYour choice, for example replies only
    Error handlingSync status inside ApolloAn error route per module, with a log and an alert
    CostIncluded in your Apollo planMake credits on top, plus build time
    Best whenSmall team, few custom fields, Apollo as the main prospecting toolSeveral sources, strict data rules or other tools in the flow

    Our rule of thumb: start native when you fill fewer than ten custom fields and nobody else writes to them. Move to Make once reps notice data changing under their hands. The Make and Pipedrive guide shows how to build that layer.

    The five mistakes we see most in Apollo integrations

    We have audited a lot of Apollo setups. Most burn credits and make the data worse at the same time. These five mistakes come back every time.

    Mistake #1: Continuous sync instead of enrichment at creation.

    Consequence: You re-enrich the same contacts every month and pay for it every time. At volume that costs thousands per year for nothing. On top of that your CRM and Apollo start to disagree on basic facts like a job title.

    How to fix it: Enrich once, when the lead is created. Add a 'Last enriched' date field. Only re-enrich contacts flagged for review, or after 12 months.

    Mistake #2: Overwriting CRM data with Apollo data.

    Consequence: A rep updated a phone number after a call. The sync writes outdated data over it. From that moment nobody trusts the CRM.

    How to fix it: Only update empty fields. If the Pipedrive field is empty, Apollo writes. If it has a value, it stays. That keeps what a human has seen.

    Mistake #3: No validation layer between Apollo and Pipedrive.

    Consequence: Apollo returns 'CEO' while your Pipedrive uses 'C-Level Executive'. Six months later you have dozens of ways to say the same thing, and reporting on it stops working.

    How to fix it: Add a normalisation step in Make.com. Map each Apollo value to the value in your Pipedrive picklist before anything is written.

    Mistake #4: Treating email confidence as yes or no.

    Consequence: You put a lead with 60 percent email confidence in a sequence. It bounces. Your domain reputation takes a hit, and you do that a thousand times.

    How to fix it: Only set 'Email verified' to yes above 90 percent. Send 60 to 90 percent to a review queue. Below 60 gets the label 'Needs verification'.

    Mistake #5: Not logging failed enrichment.

    Consequence: Apollo does not find a contact and nobody notices. The lead sits on status unknown forever. Work disappears without a sound.

    How to fix it: Log the outcome of every attempt. Create a 'Not found' status and route those leads to manual research or another source, like LinkedIn.

    What Sander says about it

    "In the best setup we built, Apollo enriches new leads in batches, and a person checks the odd cases. In the worst setup we audited, the same file was enriched again every month. So that team kept paying for contacts it already had. The tool was the same in both. The difference was in how it was built."

    Connecting Apollo to Pipedrive step by step

    Plan 2 to 4 hours. Before you start, you need these four things.

    What you need

    • An Apollo plan that includes API access (check your plan, not every tier has it)
    • Admin rights in Pipedrive
    • A Make.com account, or Zapier, if you go beyond the native integration
    • A written field mapping: which Apollo field goes to which Pipedrive field
    1. Document your data model

      Map every Apollo field to its Pipedrive field. Decide per field whether it always updates or only when empty. This one document saves you an afternoon of searching later.

    2. Create custom fields in Pipedrive

      Add 'Apollo enriched' as a date, 'Email verified' as a dropdown, and 'Enrichment status' as a dropdown with Success, Partial, Failed and Not found. This is where you read back what happened.

    3. Build the enrichment scenario in Make.com

      Trigger on a new person in Pipedrive. Module 1 searches Apollo by email. Module 2 parses the response. Module 3 updates Pipedrive, and only the fields that are empty.

    4. Add a normalisation step

      Map the Apollo values to your picklists before you write. Industry 'Software' becomes 'Technology > SaaS' if that is your taxonomy.

    5. Configure error handling

      Add an error handler. If Apollo fails, log the error, set the status to Failed and send a notification. Things may break, but never silently.

    6. Set up a place to monitor it

      Build a Pipedrive filter with contacts from the last 7 days, grouped by enrichment status. Check it weekly. Below 85 percent success, something is wrong.

    How to check it

    • Create a test contact with only an email address
    • Check that the enrichment fires within 5 minutes
    • Check that company data and job title are filled, plus the phone number where Apollo has one
    • Check that 'Email verified' and 'Enrichment status' are updated
    • Repeat with an address that does not exist and check that 'Not found' is logged

    Workflows we run in production

    These are the three flows we run most often on top of the integration.

    Inbound lead enrichment

    A lead from the website form gets context straight away.
    1. A webhook receives the form submission
    2. Make.com creates the person in Pipedrive with the email and form data
    3. Make.com triggers the Apollo lookup
    4. Apollo adds the company size and industry, and the tech stack too
    5. An ICP score is calculated from the enriched data
    6. The lead goes to the rep that matches the score

    Outbound list building

    A targeted prospect list with the data already in it.
    1. Set your ICP filters in Apollo: title, company size, industry, tech
    2. Export the leads with the enrichment included
    3. Import them into Pipedrive by CSV with your field mapping
    4. Set 'Apollo enriched' to today on every record
    5. Skip these contacts in the automatic enrichment, or you pay twice

    Monthly database cleanup

    Records that are stale or half filled.
    1. Filter in Pipedrive on 'Apollo enriched' empty or older than 12 months
    2. Export the contacts that need a refresh, 500 per batch at most
    3. Run the batch through the enrichment in Make.com
    4. Fill empty fields only, here too
    5. Review the 'Not found' results by hand
    6. Update the 'Last enriched' dates

    What does Apollo enrichment cost per month?

    Apollo enrichment costs Apollo credits, and Make adds its own credits on top. At the time of writing (November 2026), an email enrichment costs about 1 Apollo credit. A mobile number costs several credits more, around 5 to 8 depending on your plan. Make counts roughly one credit per module that runs, and filters and routers are free.

    This is what that looks like for a team with a steady inbound and outbound flow. The numbers are rounded, so check apollo.io and make.com for the current prices before you budget.

    Price level November 2026, rounded. Apollo credits depend on your plan and the number of seats.
    ItemAssumptionPer month
    New leads100 per working day, 20 working days2,000 leads
    Email enrichment in Apollo1 credit per leadabout 2,000 credits
    Mobile numbers in Apollofor 1 in 5 leads, about 8 credits eachabout 3,200 credits
    Make runsabout 4 paid modules per runabout 8,000 Make credits
    Make planCore includes 10,000 creditsaround 9 to 11 dollars

    Two things move this number more than the plan you pick. The first is re-enrichment: a monthly sync of 10,000 existing contacts costs five times the example above. The second is mobile numbers, so only request them for leads a rep will actually call.

    If you would rather have us build it, an Apollo or Instantly outbound setup starts at €950 on our pricing page.

    Apollo and GDPR

    You can use Apollo for prospecting in Europe, but the responsibility for the data sits with you, not with Apollo. B2B prospecting under the GDPR usually rests on legitimate interest. You document why the contact is relevant, you tell people where you got their data at first contact, and you offer a clear way out.

    • Write down your legitimate interest assessment once per type of campaign.
    • Store the source of every contact in Pipedrive, for example Apollo, the campaign name and the date.
    • Sync opt-outs back to Apollo and to your sending tool, so nobody is mailed again after saying no.
    • Only enrich the fields you use. A mobile number you never call is data you hold without a reason.

    The outbound guide goes into cold outreach in more detail, and the Clay guide covers GDPR when you chain several data providers.

    Apollo next to the alternatives

    Apollo is not the right data tool for every team. This is how it compares to the three we get asked about most.

    Lusha

    Pros

    • A Chrome extension for looking up one contact at a time on LinkedIn or a company site
    • Phone numbers are the main focus, not sequences

    Cons

    • No sequences, so you need a sending tool next to it

    Best for: Reps who already picked their prospects and mainly need a direct phone number

    ZoomInfo

    Pros

    • Intent data and org charts in the same platform
    • Admin rules and seat management for large teams

    Cons

    • Usually an annual contract with a higher entry price than Apollo
    • Rolling it out is a project in itself

    Best for: Larger sales organisations that buy data centrally on an annual contract

    Cognism

    Pros

    • Strong coverage of European contacts
    • Phone numbers checked by people, not only by a model
    • Clear focus on GDPR and do-not-call lists

    Cons

    • Higher price than Apollo, usually on an annual contract
    • No sequences, so you need a sending tool next to it
    • Overkill if you mainly target the US

    Best for: Teams that call into Europe and need direct dials they can trust

    Need several sources in one chain? Then Clay is the next step up. The Clay and Pipedrive guide explains when that pays off and when Apollo alone is enough.

    FAQ

    How many Apollo credits does this integration use?

    At the time of writing, an email enrichment costs about 1 Apollo credit and a mobile number several more. If you process 100 new leads a working day, budget around 2,000 credits a month for email alone. Most of the waste comes from enriching the same contact twice. So store a 'Last enriched' date and skip anyone enriched in the last 12 months.

    Should I use the native Apollo-Pipedrive integration or Make.com?

    Start with the native integration if you only need contacts and accounts in sync and fill a handful of custom fields. It maps fields and lets you choose which stages are pushed. Move to Make.com when you need rules per field, such as only filling empty fields, normalising values to your picklists or keeping an error log. Make adds its own credits on top of Apollo.

    Apollo or Pipedrive: do I need both?

    If you only do outbound with one or two SDRs, Apollo alone can work for a while. Once you have inbound leads, quotes, renewals or more than one team, Pipedrive becomes the system of record. Apollo then stays the data and prospecting layer. Then switch off deal creation in Apollo, so a deal only lives in one place.

    What if Apollo doesn't find a contact?

    Log it. Create a 'Not found' enrichment status and route those leads to manual research or another source. As a rule of thumb, expect 15 to 20 percent of B2B emails to be missing, and more in European or niche segments. That is normal, as long as your setup records it instead of leaving the lead on unknown.

    How do I handle job title standardisation?

    Build a mapping table in Make.com. Apollo's 'VP of Sales' becomes your 'VP Sales', and 'Chief Executive Officer' becomes your 'C-Level'. That takes about an hour up front. Without it you end up with dozens of versions of the same title, and no report you can filter on.

    Can I enrich existing Pipedrive contacts retroactively?

    Yes, but do it in batches of 500 at most. Export the contacts with missing data, run them through Apollo and write back with 'update if empty' logic, so nothing a rep typed is overwritten. Budget those credits separately from your ongoing enrichment, because a one-off cleanup of a large database can use a month of credits in a day.

    Is using Apollo data GDPR compliant?

    It can be, but you carry the responsibility. B2B prospecting in Europe usually rests on legitimate interest. Document why the contact is relevant and store the source in Pipedrive. Say where you found the person at first contact, and honour every opt-out in all your tools. This is not legal advice, so check your own case with a privacy lawyer.

    Sander Vergouwen

    About the author

    Sander Vergouwen

    Co-founder of Sales Surge

    LinkedIn

    Want us to build this for you?

    Start with the growth scan, or book an introduction call. Sales Surge is a Pipedrive Platinum Partner and Apollo Fully Certified for 2025 and 2026. An Apollo or Instantly outbound setup starts at €950. We put the data rules in from day one. Your ICP is yours to define, because you know it better than we do.