A native provider column, and the cheapest first step in most waterfalls.
Any Clay plan, plus your own Apollo account. Clay's catalogue marks every Apollo action as needing one.
Contacts, Companies, one way, in.
Apollo is a native Clay provider, so this is a column rather than an integration project, and Clay lists the integration as included on all plans rather than behind Growth like the CRM ones. Its place in a stack is almost always the same: first step in a waterfall, because it resolves a large share of a normal list at the lowest unit cost of anything here, and whatever it misses goes to a specialist. What changed in 2026 is the metering: bringing your own Apollo key removes the Data Credit cost and still spends an Action per record, so the key is no longer the way to make a wide table cheap.
Object by object, with the direction each one moves in. This is the table to read before the feature list, because a capability that only moves one way is a different product from the one you think you are buying.
| What | Direction | What that means in practice |
|---|---|---|
| Clay to Apollo | One way, out | A native enrichment column, configured in the table rather than through an API. |
| Records back | One way, in | Contact and company data into columns, ready to route into a CRM write. |
| Credits | Event only | Either drawn from Clay credits or from your own Apollo key, which changes the economics. |
Nothing in that table moves in both directions. Whichever system you treat as the source of record, the other one is downstream of it, and a correction made in the wrong place does not travel.
Apollo in Clay is fourteen separate actions rather than one mapping, and which one you pick decides what you have to know first. The useful split is between the ones that take a string you already have and the ones that take an Apollo ID you have to fetch.
| In Clay | In Apollo | What to know about the match |
|---|---|---|
| Find People from Apollo | Job titles, optional domains, limit 1 to 1,000 | A table source rather than an enrichment column. This is the only Apollo action here that creates rows instead of filling them. |
| Enrich Person | Any of name, email, company, Apollo ID | Every input is optional, which means it will run on almost nothing and return almost nothing. Returns contact details, employment history, firmographics, department and seniority. |
| Enrich Company | Company domain, required | The one action with a single required input. Returns headcount by department, revenue, tech stack, offices, founded year and company type. |
| Find People at Company By Job Title | Job titles and company domains, limit up to 10 | A tighter limit than Find People. Include Contacts prioritises people already linked to your CRM when a limit is set, which changes what comes back rather than how much. |
| Find Open Jobs | Company ID or job search terms | Returns a postings array with title, URL, location, posted date and last seen date, plus a total count. Last seen is the field that makes this a signal rather than a snapshot. |
| Find Saved Contacts | Keywords, limit 1 to 10 | Searches your own Apollo workspace rather than the database. Clay recommends an email address as the keyword, and the output includes sequence enrolment status. |
| Find or Create Contact | Run Dedupe on by default, plus the fields | Dedupes on email, LinkedIn URL, or name plus organisation, and returns a was_existing flag. That flag is the only thing that tells you which of the two things the action did. |
| Add Contact to Sequence | Sequence ID, Contact ID, sending account ID | All three required, and the contact must already exist in Apollo. Five override flags default to false, and the output names the reason a contact was skipped. |
Worth knowing before you write a report against it, because the wording below is what you will be filtering and searching on rather than anything you choose.
| The action | How it reads on the record |
|---|---|
| Any enrichment, on Clay's key | One Action per record, plus Data Credits for the data itself |
| Any enrichment, on your own Apollo key | One Action per record, and no Data Credits |
| A row that returned nothing | The Action regardless, because it is charged per record rather than per result |
| Find People from Apollo as a source | Sourcing contacts does not consume an Action, by Clay's own list of what is free |
| A run stopped halfway | Requests already sent still consume their Data Credits |
Three things are worth knowing before you plan around this mapping, because each one is a decision somebody has to own rather than a setting to find.
Every row above travels as a file: eight field mappings, five action rows and three documented exclusions, each one's note, and the five vendor documents behind them. The CSV opens in a spreadsheet, the JSON is the shape an agent wants, and the Markdown is the table to paste into a ticket.
The division worth remembering is the one in the second table: the data half of the bill is avoidable with your own key and the platform half is not. That is why ordering the waterfall matters more here than anywhere else in the orchestration layer, and why a wide table is expensive even when every provider in it is cheap.
There is no edition grid on this pair, because Clay lists the Apollo integration as included on all plans and Apollo gates none of these actions by tier. What does gate them is state: four prerequisites, and which ones apply depends entirely on which of the fourteen actions you picked. Pick one on each side and the grid marks the answer.
Pick one on each side.
| What you are asking Apollo to do | Your own Apollo account | The contact already in Apollo | The contact already enrolled | A sending mailbox in Apollo |
|---|---|---|---|---|
| Enrich a person or company | Required first | Not required | Not required | Not required |
| Find people, jobs or saved contacts | Required first | Not required | Not required | Not required |
| Find or create a contact | Required first | Not required | Not required | Not required |
| Add a contact to a sequence | Required first | Required first | Not required | Required first |
| Change a sequence status | Required first | Required first | Required first | Not required |
Counted off that grid, of twenty pairings: nine give you required first, eleven give you not required. The first column reads the same all the way down, and that is the finding: Clay's catalogue marks every one of the fourteen Apollo actions as requiring your own Apollo account, so there is no version of this pair you can evaluate on Clay's credits alone. The staircase only starts once you ask Apollo to do something rather than to tell you something.
Every step below is from the two vendors' own setup documentation, in the order they document it. Two of them cost you an afternoon if taken late, so the order is the useful part rather than the clicks.
Clay: + Add account
Clay's integration catalogue marks all fourteen Apollo actions as needing your own account, and the setup is one click and an authentication. The integration itself is listed as included on all Clay plans, unlike the CRM integrations, which start on Growth.
Clay: Settings, Connections
A key added in Settings under Connections, or from Add Account in the enrichment panel, removes the Data Credit cost for that provider. The Action is charged either way, which is the part that changed when Clay split one meter into two.
Clay: column order
A waterfall is only cheap if the cheap provider runs first. Apollo resolves a large share of a North America heavy list at the lowest unit cost here, so a specialist ahead of it inverts the economics of the table without changing anything a reader of the interface would notice.
Clay: run settings, Only run if
Clay's own credit guide puts this first: reorder so disqualified rows are filtered out before the enrichment runs, and use Only run if on the column. A filtered view enriches only the rows in view, which is the same lever with less setup.
Clay: Add enrichment
Enrich Person takes any of name, email, company or Apollo ID, all optional, and returns contact details, employment history and firmographics. Find People from Apollo takes job titles and optional domains with a limit of 1 to 1,000, and is a table source rather than a column.
Clay: Find or Create Contact
It dedupes by default, on email, LinkedIn URL, or name plus organisation, and returns a was_existing flag telling you which happened. That flag is what a sequence step should branch on, because Add Contact to Sequence requires a contact that already exists.
Clay: Add Contact to Sequence
Sequence ID, Contact ID and Send Email From Email Account ID are all required. Five override flags default to false: add without email, add unverified email, add with job change, add active in other campaigns, add finished in other campaigns. Leaving them off is why rows come back skipped.
Clay: Auto-run
Clay recommends about ten rows for a new integration, and recommends turning auto-run off while building so rows added too early do not spend anything. The toolbar button reads Manual once it is off.
The order above is almost entirely about money rather than about plumbing: the connection is one click, and the other seven steps exist because every row costs an Action whether Apollo finds anything or not. That is the same discipline the Clay and HubSpot write loop needs for a different reason, and it is the whole skill of working in this layer.
The same sequence, the sync table, the documented limits and the error list ship as one agent skill. Point Claude Code, Cursor or anything that reads a file at this pair as a skill and it has the whole pair without reading two sets of vendor docs first.
curl -o .claude/skills/clay-apollo/SKILL.md https://www.reversecontact.com/integrations-hub/skills/clay-apollo.md
Every limit below is documented by one of the two vendors. They are here because they change decisions, not because they are flaws.
Each of those is documented behaviour rather than a fault, so none of them is going to be fixed by a support ticket. The ones that produce a symptom you would misread are below.
Each one below is a symptom somebody reports, the documented reason behind it, and the fix. Most are configuration rather than faults, which is why they survive a support ticket.
WhyEvery input on that action is optional, so it runs on whatever is populated. A row carrying only a first name is a valid call that cannot resolve.
Require a column before the action runs, with Only run if. An email or a company domain plus a full name is the combination that resolves; a name alone is an Action spent on nothing.
WhyThe output names the reason, and it is usually one of two: the contact has no email address, or they are already in that sequence. Five override flags govern the edge cases and all five default to false.
Read the skip reason rather than the row status, and decide each override deliberately: add without email, add unverified email, add with job change, add active in other campaigns, add finished in other campaigns.
WhySend Email From Email Account ID is a required input and it is the one people leave blank. The contact also has to exist in Apollo before this action, which is a separate prerequisite.
Fetch the sending account ID once and hold it in a column, then run Find or Create Contact ahead of the sequence step and branch on its was_existing flag.
WhyRun Dedupe was turned off, or the rows carry none of the three things it matches on: email, LinkedIn URL, or name plus organisation.
Leave Run Dedupe on, which is the default, and make sure one of those three is populated before the action. The was_existing flag in the output is how you check whether it is working.
WhyBoth require an Apollo ID, and nothing earlier in the table produced one. These are follow-up actions rather than entry points.
Run a search or an enrichment first and carry the ID forward. If you only have an email, Find Saved Contacts with the email as the keyword is the documented route into your own workspace.
WhyA key removes the Data Credit cost and not the Action. Clay's documentation says an Action is still consumed, and Actions neither roll over nor can be bought as top-ups.
Cut the row count rather than the data cost. Filtered views, Only run if, and a Lookup column against a table you already enriched are the three levers Clay documents for this.
WhyThat action caps the limit at 10, where Find People from Apollo goes to 1,000. They read like the same action and are not.
Use Find People from Apollo as a table source for discovery, and keep the per-company action for filling in a list you already have.
WhyClay documents that requests already sent still consume their Data Credits when actions are stopped partway through.
Stop by turning auto-run off before adding rows rather than by halting a running table. The toolbar reads Manual when it is off, which is the state to build in.
If none of those is it, the next thing to check is the thing most pairs fail on: whether the plan you are on carries the feature at all, which the grid above answers. The same symptom on another pair is often the same cause, so the directory indexes all of them by the message rather than by the integration.
The right-hand column is the one worth being honest about, because every item in it is a reason to spend the budget somewhere else in the stack rather than a reason to configure harder.
Searched for this pair by name, in the words a person would use. 14 threads from 2024 to 2026 were read in full on 11 October 2026, and the 5 below are the ones that carry a point. Each is one person's experience rather than a measurement, and the vendors' own documentation is what the rest of this page rests on.
Direct sequence enrollment via API - You can now add contacts to Apollo sequences straight from Clay using the "Add Contact to Sequence" action. No more exporting lists and manually importing them into Apollo.
r/UseApolloIo·November 2025·2 points
Posted by Apollo in its own subreddit, which makes it a vendor announcement rather than practitioner experience, and it is here because it names the order the actions are meant to run in: find people, enrich person, find or create contact, add to sequence. The same post claims rate limits five times higher without giving an absolute figure, so the number stays off this page.
The part that's catching people off guard is that Actions used to be free if you brought your own API keys. That's gone.
r/UseApolloIo·March 2026·4 points
It matches Clay's own documentation, which says a connected key eliminates the Data Credit cost and notes that an Action is still consumed. The post is written by somebody comparing the two products commercially, so read the comparison with that in mind; the mechanism is the part the vendor confirms.
The teams getting hit hardest: agencies running multi-step HTTP workflows, anyone who relied on BYOK to keep platform costs down, and smaller operators who were getting a lot of value out of the lower tiers.
r/UseApolloIo·March 2026·4 points
Follows directly from one Action per record per step. A four-column table on a thousand rows is four thousand Actions whatever any of the providers charge, which is the arithmetic behind the ordering advice in the setup list.
Clay is only worth when you utilize APIs from Apollo and other tools. The main thing is being able to use AI in your tables
r/LeadGeneration·July 2024·2 points
Answering somebody who already pays Apollo and cannot see what the table adds. It is the honest version of the answer, and it is also why fourteen Apollo actions exist rather than one: the integration is the product rather than a feature of it.
Clay/Apollo combo here too. teh duplicate thing killed us - we had contacts from 3 different sources (web forms, events, manual adds) all creating separate records.
r/CRM·April 2026·4 points
The typo is in the original. Run Dedupe on Find or Create Contact handles the Apollo side and nothing handles the CRM side, which is where those three sources were. Deduping before the table rather than inside it is the only version of this that saves an Action.
This is the one pair where the vendors and the threads are arguing about the same thing, and the subject is not the integration. Apollo announced the improvements in its own subreddit in 2025 and the replies are about Clay's pricing change rather than about the actions. The recurring complaint is specific and checkable: Actions used to be free if you brought your own key, and they are not any more, which changes who the integration is cheap for. The older threads are mostly people asking what Clay is for when they already pay Apollo, which is a fair question and has a clear answer.
Three of those five are about pricing rather than plumbing, which is an accurate reflection of what people discuss about this pair. The mechanism in all three is documented by Clay in a single sentence about keys and Actions, so the threads are useful for the consequence rather than the fact, and the figures in them are one vendor comparing itself to another.
The reason this pair matters to stack design is ordering. A waterfall is only cheap if the cheap provider goes first, and Apollo is usually the cheap provider. Putting a specialist first and Apollo second inverts the economics of the whole table without changing a single setting anyone would notice.
The second thing to decide is whose key runs it. Clay credits are frictionless and fine at low volume. Your own Apollo key costs less per row and adds a vendor relationship to manage. At a few hundred rows a month the difference is not worth a meeting; at tens of thousands it is most of the line.
Reverse Contact resolves an email, a domain or a profile URL into a verified people and company record, through one API with a consistent schema. It sits under Clay, Apollo and everything else in this directory, and it returns null with a confidence score rather than a guess.
Free trial, no card required, and 500 credits to start.
Yes, as an enrichment column configured in the table rather than through an API. That makes it a setting rather than an integration project, and it is why Apollo shows up as the first step in so many Clay waterfalls.
Clay credits are frictionless and fine at low volume. Your own key costs less per row and adds a vendor relationship to manage. At a few hundred rows a month the difference is not worth a meeting; at tens of thousands it is most of the line, and moving later means re-running rows.
First, on a North America heavy list, because it resolves a large share at the lowest unit cost available. Putting an expensive specialist ahead of it inverts the economics of the whole table without changing anything anyone would notice in the interface.
Then the same waterfall wants a different first step. Apollo is strongest on North American data, and assuming otherwise is how a table comes back half empty after you have already paid for the attempts.
Tier requirements, sync behaviour and limits read from each vendor's own documentation in September, October and November 2026. Vendors change these without notice.
Reverse Contact appears in this directory as a data provider and publishes it. Every other tool is here on merit and nobody pays for placement.