To send new Apollo.io prospects to your CRM automatically, create a Zap with Apollo's "New Contact" trigger, add a filter that keeps only people with an email, and finish with your CRM's create-or-update action matched on email. Connect Apollo to Zapier with a master API key named Zapier.
The Complete Excel Course with AI Integration
From formulas and pivot tables to Power Query, DAX, VBA and AI with Copilot, ChatGPT and Claude — hands-on from the first lesson.
By Sagnik Bhattacharya and Virginia Thorn, Primetime Emmy Award winner
Buy nowApollo has no saved-list trigger, so the Zap fires when a contact is saved, not when you add one to a list. That detail drives the rest of the design: you filter on a field rather than a list name, the duplicate check lives in the CRM step, and you need a paid Zapier plan as soon as a filter step is added.
What does Apollo expose to Zapier?
Apollo's Zapier integration offers four triggers, New Contact, Contact Updated, New Account and Account Updated, and no saved-list trigger, which shapes every Zap you build.
Apollo's Zapier article lists the integration's parts. Read the lists closely before you plan, because each missing piece shapes the Zap.
| Type | Name in Zapier | When it fires or what it does |
|---|---|---|
| Trigger | New Contact | You save a new contact in Apollo |
| Trigger | Contact Updated | You update an existing contact |
| Trigger | New Account | You save a new company |
| Trigger | Account Updated | You update an existing company |
| Action | Create / Update contact, account or deal | Writes to Apollo from another app |
| Action | Create task | Adds a task in Apollo |
| Action | Find contact; Find or create contact | Searches Apollo by email; the second creates the contact if missing |
Two consequences. First, "Contact Updated" is described by Apollo as firing when you update an existing contact, so expect it to fire on edits generally, and avoid it for a first Zap. Second, the Find actions search Apollo by email, which is the right tool for the reverse direction (CRM into Apollo), not for checking your CRM for duplicates. Apollo's article also says you can connect only with the apps on Zapier's own Apollo integrations page, and suggests sending a webhook through Apollo Workflows if no Zapier action fits your case.
How do you connect Apollo to Zapier?
Connect Apollo to Zapier by creating a master API key named Zapier in Apollo and using it when Zapier asks you to connect your Apollo account. The connection takes about five minutes, following Apollo's steps:
- In Apollo, go to Settings, then Integrations, then API, then API keys.
- Click Create new key, name it Zapier, set it as a master key, and click Create API key.
- Copy the key and keep it somewhere secure.
- In Zapier, open My Apps, click Add Connection, search for Apollo, paste the key and name the connection.
- Click Yes, Continue to Apollo.
A master key can do more than read contacts, so treat it like a password. Name it for the tool, never paste it in a chat or shared document, and revoke it if the person who set it up leaves. Apollo's article points to its permission profiles for locking down who may touch integrations; use them if more than one person has admin rights.
How should you map Apollo fields to a CRM before building the Zap?
Plan the field mapping on paper before you open Zapier: decide which Apollo fields fill which CRM fields, who owns each contact and where it came from.
Take a four-person marketing agency that sells retainers to independent online shops. The owner saves about 30 prospects a week in Apollo and wants each one in HubSpot as a contact with the right owner and a note about where it came from. HubSpot is the example CRM here because Zapier lists a "Create or Update Contact" action for it that matches on email; the pattern is the same for any CRM whose Zapier action has an upsert.
The mapping the owner wrote down (the Apollo labels vary, so pick whichever fields your test data shows):
| CRM property | Value from the Zap | Why it is there |
|---|---|---|
| Email (match key) | Apollo contact email | The only field Zapier's HubSpot action says it matches on |
| First name, last name | Apollo first and last name | Needed for any personalised message |
| Company name, website | Apollo organisation name and website | Lets the CRM associate the company |
| Job title | Apollo title | For routing and reporting |
| Lead source | Typed text: "Apollo (Zap)" | Separates these from enquiries and referrals |
| Source date | Zapier's own timestamp for the run | Shows when it entered the CRM |
| Consent note | Typed text, see the consent section below | Records on what basis you hold the contact |
Create the three custom properties (lead source, source date, consent note) in the CRM first, otherwise they will not appear in the Zap's field list. A few minutes here saves guessing later.
How do you build the Zap step by step?
Build the Zap in this order: the Apollo New Contact trigger, a filter that keeps contacts with an email, then your CRM's create-or-update action matched on email.
- Trigger. In Zapier choose Create, then Zaps, then Trigger, search Apollo, pick New Contact, choose your Apollo connection and click Test trigger. Zapier pulls a recent saved contact so you can see every field name.
- Filter. Add Filter by Zapier. Set a first rule: Email, exists. Add a second rule on a field that marks the leads you want. If your test data shows a contact stage or label, set it to match your "ready for CRM" value; if it does not, skip the second rule and read the next paragraph.
- Action. Add your CRM, choose Create or Update Contact, pick your account and map the table above. Use the Apollo values from the trigger for each field.
- Test. Click Test step. Zapier's help says testing steps uses no tasks, but testing an action performs the action in your app, so you will see a real contact appear in the CRM. Use one of your own throwaway records.
- Publish. Click Publish to switch the Zap on.
If the trigger's test data shows nothing that tells your chosen leads from the rest, a workable method is to set the contact stage to something specific (for example "Send to CRM") in Apollo, as part of how you save the contact, then filter on it. Apollo's CSV import screen lets you set a stage for every contact in the file, so the same field is usable for bulk imports. Do not rely on a name you guessed; confirm in the test data that the field is present and filled.
How do you stop duplicate contacts when Apollo syncs to a CRM?
Use a create-or-update action matched on email, and filter out contacts with no email first, because those cannot be matched. That handles people the CRM already holds; Apollo's own import setting and a monthly review catch the other two kinds of duplicate.
Duplicates arrive from three directions, and the Zap can only handle one of them.
- CRM already holds the person. This is the Zap's job. A create-or-update action matched on email updates the record that exists instead of making a second one. Zapier's HubSpot listing describes "Create or Update Contact" as working by email address and requires an email, which is why the filter step excludes email-less rows.
- Apollo holds the person twice. Apollo's CSV import checks for existing records with the same first name, last name, company, email or LinkedIn URL, and the setting "Update the existing record" merges instead of duplicating. Choose it every time.
- The same person with two emails. Neither tool catches this, because the match key differs. A work address and a personal address make two contacts. Review by company name once a month.
The "Find or create contact" action shows the other half of the duplicate story: it finds an Apollo contact by email and, if several share the address, Apollo returns the one you created first. That is how it avoids duplicating in Apollo, and it is useful if you also push CRM contacts back into Apollo.
A before and after from a single week
The agency owner saves 40 prospects in a week. Reading the CRM beforehand, six of them are already there as past enquiries. Without any duplicate rule, the CRM gains 40 contacts and six people appear twice, one with a cold-email history and one with a conversation history. With a create-or-update step, 34 are created and six are updated with the source and title, so each of the six has one record. The sums are illustrative, but the principle is what matters: the match rule belongs in the step that writes to the CRM.
The one risk to test is blanks. If a prospect's phone is empty in Apollo and your CRM record has one from a call, check whether the Zap overwrites it with a blank. Map only the fields you want Apollo to own, and leave the rest unmapped so existing CRM values survive.
Keep a consent record on every contact the Zap creates
Apollo gives you business contacts you did not collect yourself, and your CRM becomes the place that holds them. If you have customers in the EU, or sell to people covered by similar rules, data-protection law expects you to be able to say where a contact came from and to honour opt-outs. The tutorial on Apollo data sources and opt-outs covers what is public and what is not; this section is about the practical fields.
Add three properties to the CRM and fill them in the Zap:
- Lead source (typed text such as "Apollo (Zap)").
- Source date from Zapier's timestamp for the run.
- Contact basis note in a sentence you have agreed with an adviser, such as "Business contact found through a professional database for a relevant B2B offer".
Also create a "Do not contact" tick-box that your team, not the Zap, controls. Make sure your sending tool reads it, so a person who opts out in the CRM is excluded from later sequences. If you want the legal position checked for your business, ask a qualified adviser, because the right wording depends on who you sell to.
What the Zap costs in tasks and credits
Zapier's task-usage help says triggers never use tasks, and neither do Filter, Paths or Formatter steps. A successful action step uses one task per run. A search action set to proceed even when nothing is found uses a task; one set not to proceed when nothing is found uses none. The free plan allows 100 tasks a month and two-step Zaps; the cheapest Professional tier on the pricing page is $19.99 a month billed annually ($29.99 billed monthly) for 750 tasks.
| Weekly prospects | Tasks a month (1 action) | Plan that fits |
|---|---|---|
| 20 | About 87 | Free, if you can live without a filter step |
| 30 | About 130 | Paid, and a filter is needed anyway |
| 150 | About 650 | Professional's 750-task tier, with little headroom |
| 500 bulk-saved in one day | 500 at once | Watch your task allowance before bulk saves |
The last row is the trap. The trigger fires for every saved contact, so a 500-row import can burn most of a month's tasks in one afternoon. Switch the Zap off before a bulk import, or filter so that only contacts with your "send to CRM" stage pass.
The Zap adds no Apollo credits of its own as far as Apollo's help shows, because credits are spent on reveals and enrichment. Check this yourself under Settings, Credits and activity, Credit usage, by comparing a week before and after the Zap went live. For the credit sums on a first import, see importing, enriching and scoring your first 500 leads.
What to do with the contacts that have no email
Not every saved prospect arrives with an address, because revealing an email costs an Apollo credit and you may not have spent one yet. Say 9 of the agency's 40 weekly saves have none. The filter holds them back, which is correct, but they should not vanish. Keep them in Apollo under a list called "Needs email", and once a week open it, sort by score, and spend credits only on the top five. Revealing an email changes a contact you have already saved rather than saving a new one, so New Contact is unlikely to fire again for them; test it with one record before you count on it. Either export those five to the CRM by hand, or run a second Zap on Contact Updated with the same filters; the create-or-update step makes that safe, though it fires on every edit, so keep both filter rules. The other four wait until the numbers justify the cost. This keeps credit spend visible and stops the CRM filling with records you cannot email.
Routing each contact to the right owner with a Paths step
A four-person agency often wants prospects split between two people. Zapier's task help says Paths steps, like filters, never count as tasks, so routing costs nothing extra in tasks. Add a Paths step after the filter with two branches: one for contacts whose company size is under 50 staff, owned by the account manager who handles small shops, and one for the rest, owned by the founder. Each branch then holds its own Create or Update Contact action with a different owner value. Only the branch that runs spends a task, so the cost stays at one task per contact.
Here is how one test record reads when you open the Zap history (illustrative values):
Trigger New Contact -> first name: [first name], email: name@example-shop.com, title: Founder
Filter Email exists -> passed
Filter Stage = Send to CRM -> passed
Paths Company size < 50 -> branch A
Action HubSpot Create or Update Contact -> updated existing contact, owner: small-shops manager
Reading that line by line is the fastest way to see why a record did or did not arrive. If a step says "halted", the reason is printed beneath it, and a halted filter is the normal, free outcome for a contact you did not mean to send.
A second Zap for the reverse direction
Once the first Zap works, a small second one prevents Apollo working from stale data: when a deal is lost in the CRM, use Apollo's Find or create contact action to locate that person by email and an Update contact action to set their stage to "Do not prospect". It is two actions, so two tasks per lost deal, and it keeps your sequences from emailing someone your colleague has just spoken to. Add it only if you actually run sequences from Apollo, since otherwise the stage has no effect.
How do you test the Zap before using real prospects?
Test the Zap with five fake contacts before it touches a real prospect. Save five test contacts in Apollo with names such as "Test One" and addresses you control. Make one with no email, one that already exists in the CRM, one that has the "send to CRM" stage and two that do not. Wait for the polling interval (15 minutes on the free plan, per Zapier's pricing page) and check the Zap history. You should see three runs pass the filter and two stop at it, and in the CRM you should find the existing contact updated rather than duplicated. If any of those results is different, fix the filter before you save a single real prospect.
Then delete the five test records in both tools, so they do not skew reports.
The week it went quiet: finding a stopped Zap
Picture the agency owner two weeks in. No new contacts have reached the CRM since Tuesday. The usual causes, in the order I would check them:
- The connection expired or the key was revoked. Zapier shows the Apollo connection as needing reconnection. Create a fresh API key and reconnect.
- The filter field changed. Someone renamed the stage "Send to CRM" to "Ready". The filter now matches nothing. Open the Zap history, find a run that stopped at the filter and read the reason.
- The task allowance ran out. Open Task Usage in Zapier and compare it with your plan; a bulk save earlier in the month is the usual cause.
- The CRM step erroring. A required property was added to the CRM and the Zap does not fill it.
Add a standing monthly check: open Zap history, count runs, compare with the number of contacts saved in Apollo that month. A mismatch of more than a handful is worth reading.
If you want help setting up and debugging a flow like this around your own CRM, I offer one-to-one AI consultations for small businesses.
When the Zap is the wrong tool
If you only move 20 contacts a month, a CSV export and import into the CRM may take ten minutes and cost nothing. If your CRM is connected natively, Apollo's own CRM push (a tick-box on import, per Apollo's CSV help) may do the job with no Zapier plan. Choose the Zap when you save contacts continuously, want a filter, or need the extra fields and consent record written the same way every time. For a Zap that runs the other way, taking replies out of a sending tool and into Slack and the CRM, see Instantly AI and Zapier.
A good first target is one Zap, one CRM, one filter, one consent record, and a monthly check. Add a Slack alert or an AI-written note only after it has run cleanly for a month; each extra action costs another task per contact.
If the prospect list lives in a spreadsheet before it reaches the CRM, try The Complete Excel Course with AI Integration on Coding Liquids.
Apollo.io and Zapier: questions people ask
Is there a Zapier trigger for an Apollo saved list?
No. Apollo's help page lists four triggers: New Contact, Contact Updated, New Account and Account Updated. None is a saved-list trigger. Use New Contact, then add a filter step on a field that marks the leads you want, such as the contact stage, after checking which fields your test data shows.
Will the Zap use my Apollo credits?
Probably not. Apollo's help does not list the Zapier trigger as a credit-spending action. Credits go on email and phone reveals and enrichment. Check Settings, Credits and activity, Credit usage after the first week and filter by date to confirm the Zap added no spend of its own.
Can I run this on Zapier's free plan?
Only without a filter. Zapier's free plan allows 100 tasks a month and two-step Zaps only, with a 15-minute check interval. A trigger plus one create-or-update action fits, but a filter step makes it three steps, which needs a paid plan.
What stops a contact being created twice?
A create-or-update action matched on email. Use one, as HubSpot's Create or Update Contact action does. Rows with no email cannot be matched, so filter them out first and handle them by hand. A test run with five fake contacts shows whether an existing contact is updated rather than duplicated.
How do I connect Apollo to Zapier?
Create a master API key in Apollo, name it Zapier, then use it when Zapier asks you to connect your Apollo account. Then choose New Contact as the trigger and your CRM's create-or-update action as the finish. Apollo's Zapier help article lists each step of the connection.
Further reads
- Apollo.io Email Setup: Authenticate Your Domain Before Sending — Authenticate the domain before the new CRM contacts get emails.
- How to Send My AI Front Desk Calls to Google Sheets With Zapier — Another Zap that ends in a sheet or CRM.
- Apollo.io Pricing: Free, Basic, Professional, Organization — Which Apollo plan includes the credits you will use.
- Apollo.io for Startups: Set Up AI Prospecting Step by Step — A step-by-step Apollo.io setup for a small startup: plan and credit maths, searches, AI-drafted sequences, domain set-up and the consent rules.
Browse all AI-for-business tutorials
Sources: Apollo help-centre article on integrating Zapier, Zapier's task-usage help page, pricing page and HubSpot app listing, read on 17 Nov 2026.
