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

# Salesforce and LinkedIn Sales Navigator

> Generated from https://www.reversecontact.com/integrations-hub/salesforce-integrations/salesforce-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:** Sales Navigator Advanced Plus, and a Salesforce edition with API access

**What moves:** contacts, companies, deals, activities, both ways.
**How it is built:** native, marketplace app. **Effort:** hours.

## The short version

Sales Navigator's CRM Sync was built for Salesforce first and the Salesforce side is the more mature of the two. The edition requirement is identical to HubSpot's: Advanced Plus, not Advanced. What you get for it is leads and accounts auto-saved into Sales Navigator lists, InMail and message activity written back as Salesforce activities, and CRM badges on search results so reps can see what is already owned.

## Check the plan before anything else

Rows: Salesforce edition. Columns: Sales Navigator edition. Most of the reports that this integration is broken are a pairing from this grid that was never going to work.

| Salesforce edition | Core | Advanced | Advanced Plus |
|---|---|---|---|
| Professional | Nothing | Nothing | Only with API access and Chatter |
| Enterprise or Unlimited | Nothing | Nothing | The whole integration |
| Performance or Developer | Nothing | Nothing | The whole integration |

- **Nothing.** Nothing at all. Unlike the HubSpot pair, where the embedded card runs on Advanced, LinkedIn requires Advanced Plus here for CRM Sync, Embedded Profiles and data validation alike.
- **Only with API access and Chatter.** Professional is supported only with API Access and Chatter enabled, and LinkedIn notes that may carry an extra Salesforce fee. Price that before you price the LinkedIn side.
- **The whole integration.** CRM Sync, Embedded Profiles on all four objects, activity writeback, data validation and ROI reporting.

Counted off that grid, of nine pairings: six give you nothing, one gives you only with API access and Chatter, two give you the whole integration.

One column of that grid does anything, which makes this the simplest licensing question in the directory and the most expensive answer: Advanced Plus is quoted rather than listed, so the number arrives after the meeting.

## What actually syncs

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

| What | Direction | What that means in practice |
|---|---|---|
| Leads and Contacts | Two-way sync | Auto-Save imports them into Sales Navigator lists; new records can be created from Sales Navigator. |
| Accounts | Two-way sync | Matched, so account pages carry CRM context and searches can filter on ownership. |
| Opportunities | One way, in | Open pipeline visible in Sales Navigator, and the basis for revenue attribution reporting. |
| Sales Navigator activity | One way, out | InMails, messages and notes logged as Salesforce activities. |

## Which field lands where

Matching is score-based rather than keyed, so the useful thing to know is which records can be matched at all and what each match then carries.

| In Salesforce | In LinkedIn | What to know about the match |
|---|---|---|
| Lead and Contact | Sales Navigator lead | Matched automatically with a confidence score, correctable by hand through Match Correction. A LinkedIn profile links to exactly one CRM record, so with duplicates in Salesforce only one of them gets the integration. |
| Account | Sales Navigator account | Badged the same way, and the badge shows on records the user cannot actually open, which is expected rather than a permission leak: the content stays restricted. |
| Opportunity | Pipeline context and ROI reporting | Flows one way, into Sales Navigator, and is what the revenue attribution report is built on. You pick the field holding won value during setup. |
| InMail, message, note, Smart Link | Salesforce Task or Note | Writeback lands only on Account, Contact and Lead records, and on Accounts only notes are supported. Calls log only from the mobile app. |
| Not at Company flag | A field on the Contact | Data validation writes it in bulk, which is why a Contact validation rule that blocks the update silently halves your coverage. |

**What does not cross:**

- Anything a seller did before 23 June 2021. LinkedIn documents retroactive writeback as covering only data from that date on.
- Activity on an Opportunity. Only Account, Contact and Lead receive writeback at all.
- The old LinkedIn Task record type. It is retired, activity now writes as a standard Task, and reports built on the custom type return nothing.

## Connect it, in this order

**Who has to do it:** A Salesforce admin and a Sales Navigator contract admin. LinkedIn recommends connecting as a dedicated integration user rather than as a person.
**How long:** A day of admin work, then up to a week before the first full import finishes.

### 1. Check the Salesforce edition and turn on My Domain

*Where:* Salesforce Setup

Enterprise, Performance, Unlimited and Developer are supported outright. Professional works only if API Access and Chatter are enabled, which LinkedIn notes may carry an extra Salesforce fee. My Domain has to be on before the Lightning install, not after it.

### 2. Create a dedicated integration user to connect as

*Where:* Salesforce: Users

LinkedIn recommends this over a personal admin account, and the troubleshooting guide says why: when that person changes role or loses the permission, the sync disconnects and the fix is to un-sync and re-sync as a service user. Do it now rather than after an incident.

### 3. Pick the install option before you install anything

*Where:* Salesforce: Quick Find, LinkedIn Sales Navigator

The AppExchange Package is the recommended one: it carries data validation, the Not at Company flag, and works in Classic. The Native Integration is only needed if you want InMail or connection-request steps inside Salesforce Engagement cadences. Choosing the second and then wanting data validation means installing the first anyway.

### 4. Install, and choose who gets it

*Where:* The AppExchange Package tab

Install for All Users or for specific profiles, then finish the page layouts. On Classic you add the LinkedIn Member and Company sections to Lead, Contact, Account and Opportunity layouts by hand, with the Visualforce components set to 100% width and 675 height.

### 5. Assign the two permission sets, and clone them if they fight you

*Where:* Salesforce: Permission Sets

LinkedIn Sales Navigator Standard User goes to every non-admin who needs the embedded profile; Setup User goes to a non-CRM admin doing the install. Managed permission sets cannot be edited, so an insufficient-access error means cloning the set and adding field-level access: Website, Industry and BillingAddress on Account, and ConvertedAccountId, Company, Website, Industry and Address on Lead.

### 6. Connect the CRM from the Sales Navigator side

*Where:* Sales Navigator: Admin, Admin Settings, CRM, Production

Select Salesforce, sign in as the integration user, choose Business account, then set what imports and what exports: auto-save, creating and updating leads and contacts, and activity logging. ROI reporting is on the Advanced Settings page, where you also name the field holding won opportunity value and its currency.

### 7. Turn on writeback, and warn people about the 90 days

*Where:* Admin Settings: CRM, Exported to CRM

Switch on logging for messages and InMails, notes, calls and Smart Links. Each user then authenticates with Salesforce individually and has to do it again roughly every 90 days, which arrives as a surprise sign-in prompt a quarter after go-live. Calls only log from the Sales Navigator mobile app.

### 8. Turn on data validation last, and check your validation rules first

*Where:* Admin Settings: CRM, Production, Exported to CRM

Check the Contact validation rules in Object Manager before enabling Validate CRM Data, because a rule that blocks the bulk update makes the Not at Company flag land on some contacts and not others. Jobs can be scheduled from the LinkedIn Sales Navigator Assistant, which also shows what else is already running at that hour.

The two steps worth taking out of order are the integration user and the install option: both are cheap now and both are a re-install later.

## How to check it worked

- Open a Lead, a Contact, an Account and an Opportunity and confirm the embedded profile appears on all four. It is page-layout work, and it is normal for three to work and one to be missed.
- Check the last sync timestamp in Admin Settings. The first ingestion can take up to a week depending on the size of the org, and after that updates land every 12 hours, so "nothing has synced" on day one is expected rather than broken.
- Send one InMail with Add to CRM selected and find it in Salesforce. That tests writeback, matching and the user authentication in a single action.
- Have a non-admin do the same thing. An admin-only Sales Navigator licence can configure the integration and cannot verify that it works for the team, which LinkedIn states explicitly.

## 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 embedded profile does not appear on a record page | LinkedIn lists five causes in order, and page layouts are the usual one: the layout is not activated for that object, the Standard User permission set is missing, Apex classes and Visualforce pages beginning with LID are not enabled on a profile-restricted install, the licence is not Advanced Plus, or the browser is at fault. | Work down that order rather than guessing. Try another browser first because it costs nothing, then check the layout on all four objects. |
| The sync disconnected after somebody changed role | The refresh token belonged to a personal admin account that was revoked or had its permissions changed. | Un-sync and re-sync using a dedicated integration user. This is the failure the integration-user recommendation exists to prevent. |
| Everything stopped and there was no warning | A CRM auto-disconnect error. An inactive admin user, an expired refresh token, an inactive org or an IP restriction range that excludes LinkedIn all start a three-day buffer during which nothing syncs, after which the CRM disconnects itself. | Fix the cause, then click Disconnect and Connect. Three days is the whole warning you get, so put the integration user on the list of accounts nobody deactivates. |
| The first import looks half finished | Initial ingestion is still running. It can take up to a week depending on the size of the org, and only then does the 12-hour update cycle start. | Check the last sync timestamp in Admin Settings rather than counting records. Do not re-run the setup, which restarts the clock. |
| Insufficient access despite holding the permission set | Managed package permission sets cannot include certain standard fields used as URL parameters. | Clone the set and add field-level access: Website, Industry and BillingAddress on Account, and ConvertedAccountId, Company, Website, Industry and Address on Lead. |
| A record is matched to the wrong person | Matching is score-based and picks a best guess, which is occasionally the wrong one. | Use Match Correction from the embedded profile. The correction is shared across the contract, so one person fixing it fixes it for everybody. |
| Only some contacts get the Not at Company flag | Contact validation rules are failing the bulk API update for the rest. | Adjust the rules to allow the field update, or exclude the batch job owner from triggering them. Allow 48 hours before concluding anything, and expect a sandbox never to finish a full run. |
| Reports credit every activity to one person | The licence holder owns the shared information, so activity reports attribute to them rather than to the seat that did the work. | Report on the creator field instead. If your old reports return nothing at all, they are probably built on the retired LinkedIn Task record type and need moving to the standard Task with a subject-line filter. |

## What breaks, from the vendors' own docs

- **Advanced Plus or nothing, and the Salesforce gate is stricter than the HubSpot one.** LinkedIn's admin setup guide for Salesforce requires Advanced Plus for CRM Sync, Embedded Profiles and data validation alike. On the HubSpot pair the embedded card runs a tier down on Advanced; on this one it does not, so a team that compared notes with a HubSpot shop will have been told something that is true over there and false here.
- **API access is an edition feature.** Salesforce editions without API access cannot run this, which rules out the lower editions regardless of what Sales Navigator edition you hold.
- **Install touches Salesforce metadata.** Expect a Salesforce admin, a sandbox pass and a change window. This is not a marketplace click on the Salesforce side.

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

### Salesforce

- **Base:** `https://{instance}.my.salesforce.com/services/data/v60.0`
- **Auth:** OAuth 2.0 through a connected app. **API access is an edition feature**: editions without it cannot run any of this.

| Call | Request | What it does |
|---|---|---|
| `PATCH /sobjects/Contact/{id}` | `{ "RC_Title__c": "VP Sales" }` | Update a record. Custom fields carry the __c suffix. |
| `POST /composite/sobjects` | `{ "allOrNone": false, "records": [...] }` | Batch up to 200. `allOrNone: false` so one bad row does not roll back the batch. |
| `GET /query?q=SELECT+Id,Email+FROM+Contact+WHERE+Title=null` | - | SOQL for the filtered slice. |

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

- **Validation rules, required fields, duplicate rules and Apex triggers all apply to your writes.** A completed run is not a successful write. Read the per-record errors.
- **The daily API allocation is shared across the whole org**, set by edition and licence count. A row-by-row job competes with every other integration; the symptom of exhausting it is other people's integrations failing.
- Test in a sandbox with ten records before production. The rules you will hit were written years ago by somebody who has left.
- Installing anything usually needs Modify Metadata, Download AppExchange Packages and Customize Application. That is an admin on their own schedule.

Docs: https://developer.salesforce.com/docs/apis

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

- LinkedIn Sales Navigator: CRM Sync: https://www.linkedin.com/help/sales-navigator/answer/a8037044
- LinkedIn: admin setup guide for Sales Navigator and Salesforce: https://www.linkedin.com/help/sales-navigator/answer/a16260001
- LinkedIn: troubleshooting guide for Sales Navigator and Salesforce: https://www.linkedin.com/help/sales-navigator/answer/a16656004
- 14 practitioner threads read on 2026-10-11, summarised on the page: https://www.reversecontact.com/integrations-hub/salesforce-integrations/salesforce-linkedin-integration#reddit
- This pair, with the reasoning behind each step: https://www.reversecontact.com/integrations-hub/salesforce-integrations/salesforce-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.*
