---
name: apollo-linkedin-integration
description: Connect Apollo and LinkedIn Sales Navigator: what syncs, which editions carry it, the setup order, and the failures to expect. Covers contacts, companies. Use when the user wants to set up, audit or troubleshoot Apollo and LinkedIn together, or asks why data is not moving between them.
---

# Apollo and LinkedIn Sales Navigator

> Generated from https://www.reversecontact.com/integrations-hub/apollo-integrations/apollo-linkedin-integration
> Every tier requirement, sync direction and limit below was read from the vendors' own documentation on 2026-10-11.
> Vendors change these without notice. Re-check anything load-bearing before you rely on it.

**What you have to buy first:** A paid Apollo plan for the CRM hop, credits for each save, and a reading of LinkedIn's terms

**What moves:** contacts, companies, one way, into Apollo.
**How it is built:** native. **Effort:** minutes.

## The short version

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.

## What actually syncs

Direction is written from Apollo's point of view: out means out of Apollo, in means into it.

| 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. |

## Which field lands where

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. |

**What does not cross:**

- EU and UK contacts, filtered out. Apollo says plainly that it does not do this for you.
- Any LinkedIn field, as a field. You are getting Apollo's record for a person you found on LinkedIn, which is a different thing from LinkedIn's data about them.
- Automated actions on LinkedIn. Practitioners report that Apollo's automated LinkedIn outreach stopped, and the steps above deliberately keep sending inside Apollo.

## Connect it, in this order

**Who has to do it:** Whoever is doing the prospecting. There is no admin step, which is most of why this pair spreads through a team without anybody deciding to adopt it.
**How long:** Two minutes. Read the second step before you spend them.

### 1. Read LinkedIn's User Agreement before the extension, not after

*Where:* 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.

### 2. Decide who in the team is allowed to use it

*Where:* 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.

### 3. Install the Apollo Chrome extension

*Where:* 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.

### 4. Open a profile and choose how much you are revealing

*Where:* 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.

### 5. Decide the EU and UK question yourself

*Where:* 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.

### 6. Send from Apollo, not from LinkedIn

*Where:* 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.

## How to check it worked

- Check your credit balance before and after revealing one phone number. Apollo publishes the cost, and seeing it move is how a team learns the meter is real.
- Confirm a saved contact arrived in the Apollo list you expected rather than in a default one.
- Spot-check one revealed email against a reply, not against a verification badge. The number that matters is whether you got answered.
- If you operate in the EU or UK, pick ten saved contacts and check whether any of them should not have been saved. Apollo will not have done that for you.

## When it goes wrong

Each row is a symptom somebody reports, the documented reason, and the fix. Work down it before escalating to either vendor, because most of these are configuration.

| Symptom | Why it happens | What to do |
|---|---|---|
| The extension stopped returning anything on LinkedIn pages | LinkedIn 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. |
| Credits are gone and nobody did a bulk job | Phone 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. |
| Legal asked who approved this and nobody had | There 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. |
| EU contacts are in a sequence that should not have them | Apollo 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. |
| An email bounced that Apollo showed as verified | Verification 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. |

## What breaks, from the vendors' own docs

- **LinkedIn's terms prohibit the category.** Section 8.2 of the User Agreement forbids using software, scripts, browser plugins or add-ons to scrape or copy the Services including profiles, and a separate clause forbids bots or other unauthorised automated methods to access the Services, add or download contacts or send messages. LinkedIn's help centre states that members using prohibited tools risk having their accounts restricted or shut down. The exposure sits with the rep whose account it is, which is a management decision rather than a procurement one.
- **It can stop working without notice.** LinkedIn says prohibited tools may become non-operational without notice, and the mechanism is simply that the page changes. Any workflow built on an overlay of somebody else's website inherits that fragility, so a list build that has to complete this quarter should not have this as its only path. The data itself is available through Apollo's own search and API, which is the route that does not depend on a page layout.
- **No EU or UK filtering is applied for you.** Apollo states plainly that it does not remove EU-based or UK-based contacts from the Chrome extension, and recommends checking a prospect's location on LinkedIn before saving them so that you stay GDPR compliant. That makes compliance a per-save human judgement in the middle of a fast repetitive task, which is a poor place to put it. If your market includes Europe, build the check into the process rather than relying on the rep noticing.
- **Credits are the meter, and they expire.** Saving a contact or revealing an email or phone number consumes credits. Apollo pools credits across the team and grants them upfront each billing cycle, and unused credits expire rather than carrying over. A team that does its list building in one week a month therefore pays for a monthly allowance it uses unevenly, and the free plan does not include the CRM integrations that would get the saved contact anywhere useful.

## The APIs, if you are building around it instead

### LinkedIn Sales Navigator

- **Base:** `No public API for this workflow`
- **Auth:** CRM Sync is installed as an app, not called as an API.

**Rules that will cost you time if you skip them:**

- **CRM Sync requires Sales Navigator Advanced Plus**, not Advanced. The embedded profile card runs on Advanced and syncs nothing.
- **It does not backfill.** Only new and updated data syncs after switch-on; history needs an uninstall and reinstall.
- **Field mappings cannot be customised.** Every supported field syncs or none do.
- **Read your contract before extracting anything from search results.** The constraint is contractual rather than technical, so it does not announce itself when you cross it. An agent must not automate scraping here.

Docs: https://knowledge.hubspot.com/integrations/connect-hubspot-and-linkedin-crm-sync

## Filling the record this integration moves

The integration above moves a record between two systems. Neither of them creates what is in it, so a sync that works perfectly still carries whatever gaps the record arrived with. Reverse Contact resolves an email, a domain or a profile URL into a verified people and company record through one API, and returns null with a confidence score rather than a guess.

### Reverse Contact

- **Base:** `https://api.reversecontact.com/v2`
- **Auth:** `Authorization: Bearer rc_your_api_key`. Keys are created in Workspace > API Keys.

| Call | Request | What it does |
|---|---|---|
| `POST /v2/enrich/persons` | `{ "email": "j.okafor@northwind.io" }` | Resolve a person from an email, a name plus company, or a profile URL. Cached resolution, returns in the response. |
| `POST /v2/enrich/companies` | `{ "domain": "northwind.io" }` | Resolve a company from a domain or a name. |
| `POST /v2/fetch/persons` | `{ "linkedInUrl": "..." }` | Standard profile lookup from the database. |
| `POST /v2/fetch/persons/live` | `{ "linkedInUrl": "..." }` | Live on-demand resolution. ASYNCHRONOUS: returns a webhookId to poll, not a record. |
| `POST /v2/search/people` | `{ "filters": { "currentCompanyDomain": "northwind.io" } }` | Filtered people search. 1 credit a profile delivered, and /v2/search/people/count is free. It replaced /v2/search/persons, which returns 410 Gone since 13 October 2026. |
| `POST /v2/search/organizations` | `{ "filters": { "companyDomain": "northwind.io" } }` | Filtered company search. A domain can also go straight to a company through POST /v2/enrich/companies, or through the enrich_company MCP tool since November 2026. |
| `POST /v2/contact/email` | `{ "linkedInUrl": "..." }` | Find an email. ASYNCHRONOUS: returns a taskId to poll. 3 credits for a professional address, 5 for a personal one, 8 for both, refunded when neither is found. |
| `GET /v2/webhooks/:webhookId` | - | Poll an async job until status is "succeeded". Polling is free and does not count against the rate limit. |

Response shape:

```json
{
  "success": true,
  "data": {
    "person": {
      "fullName": "Jane Okafor",
      "headline": "VP Sales at Northwind",
      "location": "London, United Kingdom",
      "linkedInUrl": "https://linkedin.com/in/...",
      "currentPosition": { "title": "VP Sales", "companyName": "Northwind", "startDate": "2023-04" },
      "emails": [], "experience": [], "education": [], "skills": []
    },
    "company": { "name": "Northwind", "domain": "northwind.io",
                 "industry": "Software Development", "employeeCount": 220 }
  },
  "error": null,
  "metadata": { "requestId": "req_...", "executionTimeMs": 480, "updatedAt": "2026-09-01T..." },
  "quotas": { "creditsConsumed": 1, "workspace": { "credits": { "total": 10000, "used": 4521, "left": 5479 } } }
}
```

**Rules that will cost you time if you skip them:**

- A miss returns **null**, not a best guess. Every response carries a confidence score, and you can raise the precision threshold on the request. Branch on it: do not treat a low-confidence answer as a match.
- Use the cached endpoints anywhere that must answer inside one HTTP request. The `/live` endpoints return a task and need polling.
- `quotas.workspace.credits.left` is on every response. Log it, or you will find out about the balance from a 402.
- Credit costs per call are published and a dollar rate per lookup is not: 2 credits for a reverse lookup from an email, 1 for a cached profile lookup, 2 for a live refresh, 3 for a business email and 20 for a direct phone number, with the last two charged only when one is found. Checks and the search count endpoint are free. Credit packs expire after 3 months. Do not hard-code a dollar cost assumption.

**MCP server:** `https://api.reversecontact.com/mcp`

- Auth: OAuth 2.1 where the client supports it, otherwise `Authorization: Bearer rc_your_api_key`.
- Tools: `enrich_person`, `enrich_person_live`, `enrich_company`, `enrich_company_live`, `search_persons`, `search_companies`, `check_usage`, `check_task`
- Streamable HTTP, JSON-RPC 2.0. The `_live` tools return a task id that `check_task` polls.

Docs: https://docs.reversecontact.com/getting-started

## Sources

- Apollo knowledge base: prospect on LinkedIn with the Apollo Chrome extension: https://knowledge.apollo.io/hc/en-us/articles/4409229262093-Prospect-on-LinkedIn-with-the-Apollo-Chrome-Extension
- LinkedIn: User Agreement, section 8.2: https://www.linkedin.com/legal/user-agreement
- LinkedIn help centre: prohibited software and extensions: https://www.linkedin.com/help/linkedin/answer/a1341387
- Apollo: pricing and credits: https://www.apollo.io/pricing
- 14 practitioner threads read on 2026-10-11, summarised on the page: https://www.reversecontact.com/integrations-hub/apollo-integrations/apollo-linkedin-integration#reddit
- This pair, with the reasoning behind each step: https://www.reversecontact.com/integrations-hub/apollo-integrations/apollo-linkedin-integration

---

*Published by Reverse Contact, which appears in this directory as a data provider.
No other vendor pays for placement. Where a vendor publishes no public figure, this file says so
rather than estimating. Reverse Contact costs are stated in credits, which it publishes; no dollar
rate per lookup appears here, because none is published and dividing a pack price is not their number.*
