Not an integration. A browser extension, against a user agreement that forbids one.
A paid Apollo plan for the CRM hop, credits for each save, and a reading of LinkedIn's terms
Contacts, Companies, one way, in.
Every other page in this directory describes an integration; this one describes a browser extension and a user agreement that prohibits the category it belongs to, and pretending otherwise would be the most useful thing we could get wrong. The capability is real: open a LinkedIn profile, see Apollo's data over it, save the person as a contact and put them in a sequence, all in a few seconds. The risks are also real and they are borne by the person with the LinkedIn account rather than by the vendor. Read LinkedIn's section 8.2 before you roll this out to a team, decide knowingly, and do not let anybody describe it internally as an integration with LinkedIn, because LinkedIn has not agreed to one.
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 |
|---|---|---|
| A LinkedIn profile to an Apollo contact | One way, in | Save contact or access email, or access email and phone. Both consume Apollo credits. |
| Apollo data over the page | One way, in | Rendered in your browser by the extension. Nothing is written to LinkedIn and nothing is stored there. |
| Saved contacts into sequences and lists | One way, in | Inside Apollo, from the extension. The sequencing happens in Apollo, not on LinkedIn. |
| Colleagues at the same company | One way, in | The extension surfaces similar profiles and colleagues, which is the part that makes it a list-building tool rather than a lookup. |
| Anything back to LinkedIn | One way, out | Nothing. There is no write path, no app and no API between the two companies. |
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.
There are no fields moving between two systems here, because the two systems are not connected. The extension reads a page you are looking at and writes into Apollo, and what it costs is published per action.
| In Apollo | In LinkedIn | What to know about the match |
|---|---|---|
| A LinkedIn profile you are viewing | An Apollo contact | Saved from the extension. Apollo prices a verified email at 1 credit. |
| The same profile, with a phone number | An Apollo contact with a direct dial | Apollo prices a verified phone number at 8 credits, which is eight times the email and the reason a team burns an allowance faster than it planned. |
| Contact and company enrichment | Filled fields on the Apollo record | Published at 1 to 8 credits depending on what comes back. |
| An AI research run | Insight on the Apollo record | 1 credit per run, so a workflow that researches every saved contact doubles the cost of saving them. |
| Anything at all | Back to LinkedIn | Nothing. No write path, no app, no API. The extension is a reader and LinkedIn is unaware of it. |
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: five field mappings and three documented exclusions, each one's note, and the four 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.
Reading the credit column rather than the plan price is the useful exercise here: a team that reveals phone numbers by habit is running an eight-times multiplier on its own allowance.
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.
LinkedIn: User Agreement, section 8.2
LinkedIn forbids using software, scripts, browser plugins or other means to access its services, and says prohibited tools may stop working without notice. Nothing on this page changes that, and every step below sits underneath it.
A policy, not a settings page
Because there is no admin install, the decision gets made by whoever installs the extension first. If your company has a view on scraping, this is the moment it needs to be written down rather than discovered.
Chrome Web Store
A per-user browser install with no connection between the two platforms behind it. Apollo renders its own data over the LinkedIn page in your browser; nothing is written back to LinkedIn and no API sits between them.
A LinkedIn profile, with the extension open
Save contact or access email saves the person and reveals an address. Access email and phone does both. Apollo prices these separately in credits, so this click is the spend.
Your own filtering, before the sequence
Apollo states that it does not remove EU-based or UK-based contacts for you. Whoever owns your lawful basis has to apply that filter somewhere downstream, and the extension is not the place it happens.
Apollo: sequences and lists
Saved contacts flow into Apollo sequences and lists. Keeping the sending inside Apollo is also the arrangement least likely to involve automating actions on LinkedIn itself, which is the part practitioners report getting shut down.
Four of the six steps are judgement rather than configuration, which is the honest shape of this pair: the install is trivial and the decision is not.
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/apollo-linkedin/SKILL.md https://www.reversecontact.com/integrations-hub/skills/apollo-linkedin.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.
WhyLinkedIn states that tools in this category may become non-operational without notice, and practitioners report exactly that happening.
There is no configuration fix. Treat continuity as a risk you carry rather than a service level, and keep the contacts you have already saved exported.
WhyPhone reveals. Apollo publishes a verified phone number at 8 credits against 1 for an email, and the cost is per click rather than per campaign.
Agree as a team when a phone number is worth revealing. The habit, not the volume, is what empties the allowance.
WhyThere is no admin install. One rep adds a browser extension and the company has adopted a tool.
Decide the policy explicitly. This is the only integration in the directory where the governance gap is the default state rather than a misconfiguration.
WhyApollo does not remove EU-based or UK-based contacts, and says so.
Filter before the sequence, in Apollo or in whatever sits downstream. Nothing upstream will do it.
WhyVerification is a claim about the address at some point in time, not a guarantee of deliverability today.
Measure your own bounce rate over a few hundred sends rather than trusting a per-record badge, and treat the rate as the number worth quoting internally.
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.
Apollo & Seamless has their entire company pages got deleted from Linkedin yesterday for violating their terms of service by scraping data
r/sales·March 2025·17 points
One practitioner's report rather than an announcement from either company, so read it as what the market believed rather than as a confirmed event. What it corroborates is the documented part: LinkedIn's User Agreement forbids this category, and it tells you what enforcement can look like when it comes.
ZoomInfo was not. They are very careful about how they source their data because they are a public company. I think they are too expensive but tbf, they do spend a lot on data too
r/sales·March 2025·8 points
The useful frame for anyone choosing. Sourcing is not a detail behind the price, it is the thing that decides whether your prospecting stack survives somebody else's enforcement action, and it is worth asking a vendor about directly.
Yes it seems like it's dead because they had to comply with LinkedIn. Lemlist or La Growth Machine still do automate LinkedIn actions I believe, I might go with them.
r/GrowthHacking·February 2026·4 points
Worth noticing where that reasoning goes next: the writer's response to one tool complying is to look for one that has not. The compliance question does not disappear by changing vendor, it just moves.
I am planning to do a signal based cold outreach for my startup and am confused about which tool to choose for identifying buying signals. So far I have come across Apollo and Sales Navigator
r/b2bmarketing·October 2026·4 points
The real comparison, and the two options are not the same kind of thing. One is a licence from the platform and the other is a tool the platform forbids, which is a procurement question as much as a feature one.
sales navigator is only good when you already know who you are looking for, the industry filters are super broad and it is sometimes hard to find the right the people if you only have a job title in mind
r/b2bmarketing·October 2026·5 points
Fair, and it explains the pull of the extension. Sales Navigator is strong at finding a named person inside a known account and weaker at building a list from a description, which is exactly the job people reach for Apollo to do.
This is the only pair in the directory where the threads are about whether the integration is allowed to exist. In March 2025 practitioners reported LinkedIn removing company pages belonging to tools in this category, and the conversation since has been about which vendors are exposed and which are not. Nobody is arguing the extension does not work. They are arguing about how long it will keep working and what it costs to be wrong.
If you take one thing from the threads rather than from the documentation, make it the sourcing question: it is the one that decides whether this part of your stack is still there next quarter.
The reason this page exists is that "apollo linkedin integration" is a question thousands of people ask every month, and every answer they find describes a browser extension as though it were a connector. The distinction is not pedantry. A connector is an agreement between two vendors with documented objects, a direction and a support path.
This is one vendor drawing its own data over another vendor's website in your browser, against a user agreement that explicitly names browser add-ons among the things members may not use to copy profiles. Those are different products with different failure modes, and only one of them can be escalated to anybody when it breaks.
None of which means do not use it. Plenty of competent teams do, knowingly, because a rep researching a named account on LinkedIn and saving the right person in two seconds is genuinely faster than any alternative.
The condition is that the decision is made by somebody who has read section 8.2, understands that the account at risk belongs to the rep rather than to the company, and has decided the trade is worth it for the volume involved. What is not defensible is a RevOps lead rolling this out to thirty reps as "the LinkedIn integration" and nobody ever reading the terms.
If the honest answer is that you need volume, the route changes shape entirely. Apollo's own search and API will build the list without touching LinkedIn's pages, which removes both the terms question and the fragility, and a Clay table will do the same job with waterfall enrichment behind it so a missing email falls through to another provider rather than to nothing. That is more work to set up and it does not depend on a page layout staying still. The prospecting layer is where that comparison belongs, and the general rule it produces is worth stating plainly: an overlay is a research tool, and a list build wants an API.
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 Apollo, LinkedIn 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.
Not in the sense the word is used everywhere else on this site. There is no API between them, no app in a marketplace and no agreement between the two companies. What exists is the Apollo Chrome extension, which draws Apollo data over LinkedIn pages in your browser and lets you save a profile as an Apollo contact. It is genuinely useful and it is a browser extension, which is a different kind of thing from a sync with a direction and a schedule.
LinkedIn's User Agreement section 8.2 says members will not develop, support or use software, devices, scripts, robots or any other means or processes, including crawlers, browser plugins and add-ons, to scrape or copy the Services, including profiles and other data. LinkedIn's help centre adds that it does not permit third-party software that scrapes its website, changes its appearance or automates activity on it, that members using such tools risk having their accounts restricted or shut down, and that the tools may become non-operational without notice. That is LinkedIn describing a category, not Apollo specifically, and it is the single most important fact on this page.
Credits. Apollo documents that saving a contact and accessing an email, or an email and a phone number, consumes credits from your plan. Apollo's pricing page states that credits are pooled across the team, granted upfront at the start of each billing cycle, and that unused credits expire and do not carry over. Apollo does not publish a per-credit price in a form worth quoting here, so model the monthly credit allowance against the number of profiles your team will actually save.
Only indirectly, and not on a free plan. The extension saves the prospect into Apollo; getting that record into HubSpot or Salesforce is Apollo's CRM integration doing the work, and Apollo's free plan does not include CRM integrations. So the honest chain is LinkedIn to your browser to Apollo to your CRM, with a paid Apollo plan required for the last hop and a separate set of limits on it.
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.