---
name: linkedin-reverse-contact-integration
description: Connect LinkedIn Sales Navigator and Reverse Contact: 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 LinkedIn and Reverse Contact together, or asks why data is not moving between them.
---

# LinkedIn Sales Navigator and Reverse Contact

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

**What you have to buy first:** A Reverse Contact API key. No LinkedIn edition, no LinkedIn API access and no browser extension

**What moves:** contacts, companies, one way, out of LinkedIn.
**How it is built:** built on the api, zapier, make or n8n. **Effort:** minutes.

## The short version

Every other page on this hub answers what you are allowed to connect. This one does not connect to LinkedIn at all, which is both its appeal and the thing to be clear-eyed about. A profile URL resolves to a record for 1 credit without any Sales Navigator edition, any API approval or anything running in a rep's browser, and section 8.2 of the User Agreement still addresses information obtained from the Services through third parties such as data aggregators. The mechanical risk and the contractual question come apart here, and a reader deserves both rather than whichever one suits the publisher.

## The four categories, and what each one actually costs you

Rows: The category. Columns: What it costs you. This hub's rule is that every page says which category an integration is in before it says what it does, and this page is a category the hub did not originally have. The columns are the four things that decide whether a route is usable, and reading down the first two is more informative than reading across any row.

| The category | A Sales Navigator edition | Risk to a rep's own account | Addressed by section 8.2 as written | Somebody to escalate to |
|---|---|---|---|---|
| CRM Sync, through an approved partner | An Advanced Plus upgrade | No rep in the path | An authorised route | Both vendors |
| An embedded tile in a partner product | An Advanced Plus upgrade | No rep in the path | An authorised route | Both vendors |
| A browser extension over linkedin.com | No edition at all | Risk to a rep | Reached by the clause | Nobody |
| A third-party database, from a profile URL | No edition at all | No rep in the path | Reached by the clause | One vendor only |

- **An Advanced Plus upgrade.** CRM Sync, activity writeback, record matching and the partner tiles all require Sales Navigator Advanced Plus, which is quoted rather than listed and has to be priced across the whole seat count.
- **No edition at all.** No LinkedIn edition gates it, because nothing in the route authenticates against LinkedIn. For an extension that is because it borrows a rep's existing session; for a third-party database it is because LinkedIn is not in the path at all.
- **Risk to a rep.** LinkedIn's help centre says members using prohibited tools risk having their accounts restricted or shut down, and that the tools may stop working without notice. The account at stake belongs to a person rather than to the company.
- **No rep in the path.** No rep logs in and no software runs against LinkedIn's website, so there is no session to restrict. This is a statement about mechanism rather than a view on the clause in the next column.
- **An authorised route.** An approved integration is an agreement between two vendors, with consent and a support path, which is the arrangement the prohibitions are drawn around rather than aimed at.
- **Reached by the clause.** Section 8.2 covers developing or using crawlers, browser plugins and add-ons to scrape or copy the Services, and separately covers copying, using, displaying or distributing information obtained from the Services "whether directly or through third parties (such as search tools or data aggregators or brokers), without the consent of the content owner". The first describes an extension and the second reaches a database.
- **Both vendors.** Two vendors with a commercial relationship and a documented escalation path between them. When it breaks, somebody is accountable for fixing it.
- **One vendor only.** You have a contract with the data vendor and none with LinkedIn, so a problem with the data has an owner and a question about the terms does not.
- **Nobody.** Nobody is accountable. LinkedIn's own documentation says such tools may become non-operational without notice, which is as clear a statement of no support path as a company ever makes.

Counted off that grid, of sixteen pairings: two give you an Advanced Plus upgrade, two give you no edition at all, one gives you risk to a rep, three give you no rep in the path, two give you reached by the clause, two give you an authorised route, two give you both vendors, one gives you one vendor only, one gives you nobody.

The first two rows are identical, which says that the two authorised categories behave the same way and both cost an edition upgrade. The sharper reading is how the first and third columns cross: the two routes that need no edition are the two the agreement addresses, and the two covered by an agreement are the two you have to pay Advanced Plus for. There is no row that is free of all four costs, and a page that implied otherwise would be selling something.

## What actually syncs

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

| What | Direction | What that means in practice |
|---|---|---|
| A profile URL | One way, out | Copied, exported or already on the record. Nothing reads it from LinkedIn on your behalf. |
| The lookup | One way, out | POST /v2/fetch/persons for a profile URL at 1 credit, or /v2/enrich/persons from an email at 2. |
| The record | One way, out | Identity, current role, history and the company, on the same schema whichever identifier went in. |
| Nothing at all | One way, out | No data is written to LinkedIn, no connection is made and no message is sent. There is no inbound direction on this page. |

## Which field lands where

There is nothing to map in LinkedIn, because nothing is written to it. The map that matters here is the one between the identifier you happen to hold and what it costs, which is the only part of this page that varies by more than a rounding error.

| In LinkedIn | In Reverse Contact | What to know about the match |
|---|---|---|
| A LinkedIn profile URL | POST /v2/fetch/persons, 1 credit | The cheap direction, and unmetered from the $249 plan. A list exported from a profile source usually already carries this column. |
| An email address | POST /v2/enrich/persons, 2 credits | The reverse direction, and unmetered only from the $699 plan. This is the route for an old CRM record that has an address and no profile. |
| A first name, last name and company | POST /v2/enrich/persons, 2 credits | Same price as an email and a thinner identifier, so the confidence score matters more. Raise the precision threshold rather than accepting what comes back. |
| A company domain | POST /v2/enrich/companies, 2 credits | Firmographics from a domain, on the same schema. The enrich_company MCP tool takes a domain as well since November 2026, so an agent no longer has to search first. |
| currentPosition.title and companyName | Your CRM, on fields it owns | The two values a list sourced from profiles is most likely to have wrong, because a profile export is a snapshot and people move. |
| The position history | Context, not a field | Useful for a human writing a first line and poor as a filter. Store it if you will read it and skip it if you will not. |
| The confidence score | A branch, decided in advance | Returning null rather than a guess only helps if something downstream acts on it: another provider, a review queue, or writing nothing. |
| Anything at all | Not LinkedIn | No write, no connection request, no message, no activity. There is no inbound direction in this integration and no product surface that would take one. |

### What the identifier you hold is worth

Reverse Contact publishes which plan stops metering which family of calls, and the families are divided by the identifier rather than by volume. Each row below is a starting point somebody actually has, with what it costs and the plan at which it stops being counted.

| What you already hold | The cost, and where the metering stops |
|---|---|
| A LinkedIn profile URL | 1 credit as a cached lookup, and unmetered on Go at $249 a month. The cheapest identifier there is, and the one a profile-sourced list already has |
| An email, a name or a domain | 2 credits as a reverse lookup, and unmetered only on Max at $699 a month. The same build costs almost three times as much to run from here |
| A search, rather than an identifier | People and company search is 1 credit per profile delivered and unmetered on Plus at $449. The count endpoint that tells you how big a result set is costs nothing at all |
| Nothing, and you want to check freshness | Free on every plan, including the search count. This is what a sweep should run first, and it is paused below 2 credits along with everything else |
| A record that needs a live refresh | 2 credits, charged when the job is created and kept even if it finds nothing. The one endpoint here where a miss is billed, on every plan including Platform |
| A need for a phone number or a business email | 20 and 3 credits, charged only when one is found, on credits on every plan. Both are asynchronous and return a task id to poll |

**What does not cross:**

- Anything written to LinkedIn. No connection, no message, no InMail and no activity, and nothing in the product that would accept one.
- The LinkedIn API. Sales permissions require approval as a Sales Navigator Application Platform partner and LinkedIn says it is not currently accepting new partners, so this route does not involve it at all.
- A browser extension. Nothing is installed, no rep authenticates and no request reaches linkedin.com, which is the mechanical difference from the category most of this hub is about.
- Connections, followers or engagement data. The response carries a verification badge and a follower count, and neither is a seniority signal however convenient it would be.

## Connect it, in this order

**Who has to do it:** Whoever can create a Reverse Contact API key. There is no LinkedIn administrator in this build, which is the point.
**How long:** Minutes through the Clay, Zapier or Make app. An hour against the API directly.

### 1. Read section 8.2 with whoever owns that decision, before building anything

*Where:* LinkedIn: the User Agreement, and your own counsel

The clause covers information obtained from the Services directly or through third parties such as data aggregators or brokers, without the content owner's consent. This page states the clause and does not interpret it for you, and this is the step that cannot be undone after a list has been built on it.

### 2. Find out which identifier your records already carry

*Where:* Your CRM or your list

A profile URL is a 1-credit cached lookup and unmetered from the $249 plan. An email, a name or a domain is a 2-credit reverse lookup and unmetered only from $699. This single question changes the cost of a backfill by more than any other decision on the page.

### 3. Create the key and spend the trial credits on your own rows

*Where:* Reverse Contact: Workspace > API Keys

The trial takes no card and a new account starts with 500 credits, which is 500 profile-URL lookups or 250 reverse ones, and it runs until those credits are spent rather than for a number of days. The published 70%+ identity match rate is a global figure and Reverse Contact says to measure your own, so spend the trial on that rather than on a demo list.

### 4. Decide the precision threshold before you look at any results

*Where:* The request, as a parameter

Reverse Contact returns null with a confidence score rather than a guess, and the threshold can be raised on the request. Setting it after seeing the results is how a team talks itself into accepting thin matches, which on a list sourced from profiles is the main way this goes wrong.

### 5. Check before you fetch, on the endpoint that costs nothing

*Where:* POST /v2/fetch/persons/check

The free check says whether a profile is cached and when it was last updated. On a list you have enriched before, this is the difference between re-resolving everything and paying only for what has actually moved.

### 6. Compare the returned employer against what you already hold

*Where:* Your middle layer or your Clay table

A list built from profiles six months ago is a list of people some of whom have moved, and a disagreement between the returned current position and the account on your record is the most valuable thing in the response. It is also the only thing on this page that no LinkedIn integration will tell you, because CRM Sync moves data forward rather than auditing what is there.

### 7. Write to your own system, because there is nowhere else to write

*Where:* Your CRM, your sequencer or your warehouse

Nothing in this build writes to LinkedIn, makes a connection or sends a message, and there is no product surface in LinkedIn that would accept it. Treat the output as a record for your own systems and the page's shape follows from that.

### 8. Run 500 rows and count before anybody plans a campaign on it

*Where:* Clay, a sheet, or a script

On [the Clay route](pair:clay+reverse-contact) this costs Clay credits and no Reverse Contact account at all, which makes it the cheapest measurement available. Your own match rate on your own list is the number that decides everything downstream, and it is never the published one.

The first step is the only irreversible one and it is not technical. Everything after it is a single API call wrapped in whatever you already use, which is why the effort on this page is minutes rather than the days most of this hub requires.

## How to check it worked

- Take a profile URL for somebody whose job you know changed recently and run it. The returned current position is the test of whether the database is as fresh as the marketing says, measured on a case you can check.
- Run the same person from their email and from their profile URL. Compare the records and the cost, because one of those calls is half the price of the other and on most lists you have a choice.
- Set the precision threshold high and run fifty rows, then set it low and run the same fifty. The difference is the number of matches you would have accepted without a threshold, and it is usually larger than anybody expects.
- Confirm nothing in your build authenticates to LinkedIn. If a step asks a rep to log in, you have assembled a browser extension by accident and the risks on this page have changed.

## 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 |
|---|---|---|
| A list exported six months ago is full of wrong job titles | A profile export is a snapshot, and LinkedIn data ages faster than most because the field that matters most is the one people change. | Re-resolve from the profile URL rather than re-exporting, which costs 1 credit a row and is unmetered from the $249 plan. Run the free check first so you only pay for the rows that have actually moved. |
| The backfill cost nearly three times the estimate | The estimate assumed a cached lookup from a profile URL at 1 credit and the list actually held email addresses, which is a reverse lookup at 2 and unmetered only from the $699 plan. | Audit which identifier the list carries before pricing anything. Where both are present, send the profile URL, because the record that comes back is the same either way. |
| 429 DAILY_EXTRACTION_LIMIT_EXCEEDED on an Unlimited plan | The covered calls are unmetered up to 100,000 profiles per workspace per UTC day, after which they are refused until midnight UTC. | Spread the job across days and watch the clock, which is UTC rather than local. The minute limit is 100 on all three Unlimited tiers, so paying more buys unmetered families rather than throughput. |
| The matches look plausible and the campaign underperformed | A thin identifier such as a name and a company was accepted without a precision threshold, so low-confidence matches were written as facts. | Raise the threshold on the request and decide in advance what a null should do. Reverse Contact returns null with a confidence score rather than a guess, which is only useful if something branches on it. |
| Legal asked which agreement covers this and nobody had an answer | The build was treated as a technical choice. Section 8.2 addresses information obtained from the Services through third parties such as data aggregators or brokers, and that is a question for counsel rather than for an engineer. | Have the conversation first, which is step one of the checklist for this reason. A list already built on an unanswered question is the expensive version of this problem. |
| A rep's LinkedIn account was restricted | Not this build. LinkedIn restricts accounts over tools that scrape, modify the appearance of, or automate activity on its website in a member's own session. | Find the extension. If a step in your process asks a rep to log in to LinkedIn, that part is in a different category from the rest of this page and carries a different risk. |
| Everything stopped, including the calls that were free | Below 2 Reverse Contact credits the free Check endpoints are paused as well and answer 402 NO_CREDITS. | Watch quotas.workspace.credits.left on every response, and check GET /v2/usage on a schedule because it keeps answering whatever the balance. |

## What breaks, from the vendors' own docs

- **No LinkedIn edition is required, and that is the finding.** The embedded profile card runs on Advanced, and CRM Sync, activity writeback, record matching and the partner tiles all need Advanced Plus, which is quoted rather than listed. This route needs none of them, because nothing in it authenticates against LinkedIn.
- **Section 8.2 names third parties explicitly.** LinkedIn's own help centre quotes the clause as prohibiting members from copying, using, displaying or distributing information obtained from the Services "whether directly or through third parties (such as search tools or data aggregators or brokers), without the consent of the content owner". A separate sub-clause covers developing or using crawlers, browser plugins and add-ons to scrape or copy the Services. Read both and decide knowingly.
- **A rep's account is not in the path.** LinkedIn says members using prohibited tools risk having their accounts restricted or shut down, and that such tools may stop working without notice. Neither applies mechanically here, because no rep authenticates, nothing is installed in a browser and no request reaches linkedin.com. That is a real difference from the overlay category and it is not an answer to the clause above.
- **A profile URL is half the price of an email.** A cached lookup from a profile URL is 1 credit and unmetered from the $249 plan; a reverse lookup from an email, a name or a domain is 2 credits and unmetered only from $699. The identifier you already hold decides the bill, and on a list sourced from profiles that is a large difference.
- **The daily ceiling is 100,000 profiles.** On the Unlimited plans the covered calls cost nothing up to 100,000 profiles per workspace per UTC day, then return 429 DAILY_EXTRACTION_LIMIT_EXCEEDED until midnight UTC. The minute limit is 100 on all three tiers, so a million-row backfill is a seven-day job whatever you pay.
- **Nothing here backfills LinkedIn, because nothing writes to it.** The hub's warning that CRM Sync moves data only from the moment it is switched on does not apply to this route, and nor does its opposite: there is no history to import and no switch-on date. What you have is a lookup you can run on any record, at any time, including one from five years ago.
- **Under 2 credits the free checks stop too.** Below 2 Reverse Contact credits even the free check endpoints answer 402 NO_CREDITS, while GET /v2/usage and webhook polling keep answering. A sweep designed to check cheaply before spending fails at the check.

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

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

- LinkedIn: User Agreement, section 8.2: https://www.linkedin.com/legal/user-agreement
- LinkedIn Help: prohibited software and extensions: https://www.linkedin.com/help/linkedin/answer/a1341387
- LinkedIn: API rate limits: https://learn.microsoft.com/en-us/linkedin/shared/api-guide/concepts/rate-limits
- LinkedIn: getting API access: https://learn.microsoft.com/en-us/linkedin/shared/authentication/getting-access
- LinkedIn Help: Sales Navigator CRM Sync editions: https://www.linkedin.com/help/sales-navigator/answer/a8037044
- Reverse Contact API documentation: https://docs.reversecontact.com/getting-started
- Reverse Contact: credits: https://docs.reversecontact.com/guides/credits
- Reverse Contact: rate limits: https://docs.reversecontact.com/guides/rate-limits
- Reverse Contact pricing: https://www.reversecontact.com/pricing
- 14 practitioner threads read on 2026-10-28, summarised on the page: https://www.reversecontact.com/integrations-hub/linkedin-integrations/linkedin-reverse-contact-integration#reddit
- This pair, with the reasoning behind each step: https://www.reversecontact.com/integrations-hub/linkedin-integrations/linkedin-reverse-contact-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.*
