The original CRM Sync target, with the same Advanced Plus gate.
Sales Navigator Advanced Plus, and a Salesforce edition with API access
Contacts, Companies, Deals, Activities, two-way sync.
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.
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 |
|---|---|---|
| Leads and Contacts | Both ways | Auto-Save imports them into Sales Navigator lists; new records can be created from Sales Navigator. |
| Accounts | Both ways | 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. |
Two of those four rows move in both directions. The two that do not are Opportunities and Sales Navigator activity, and those are the rows that decide how you design around this rather than the ones in the brochure.
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. |
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 three 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 duplicate rule is the one with the longest tail: every duplicate contact in Salesforce is a record that silently has no LinkedIn functionality, and consolidating them is the only fix.
Three Salesforce editions against three LinkedIn ones, and what each pairing gives you. Pick the two you own and the grid marks the answer.
Pick an edition on each side.
| 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 |
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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/salesforce-linkedin/SKILL.md https://www.reversecontact.com/integrations-hub/skills/salesforce-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 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.
WhyThe 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.
WhyA 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.
WhyInitial 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.
WhyManaged 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.
WhyMatching 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.
WhyContact 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.
WhyThe 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.
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 2021 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.
Manual. Linkedin is only valuable because of their contact data. They intentionally make it difficult to extract into your crm.
r/salesforce·May 2026·5 points
Blunt and broadly right. What the integration gives you is LinkedIn's view inside the record and activity written back out; what it does not give you is the profile data itself as fields you own, which is the thing most of these threads are actually asking for.
update employment records in SF for 2000+ Contacts, people who graduated from our program
r/salesforce·February 2025·7 points
Data validation and the Not at Company flag are the part of this integration that speaks to it, and they stop at a flag: they tell you a record is wrong rather than what it should now say. For 2,000 records that is the difference between a report and a fix.
You've got to use multiple APIs to do this. There is no single API that can handle this. So basically, it's gonna be like a waterfall model where one API may give you five data points, and then you have to get the rest of the data from a second API.
r/salesforce·November 2025·7 points
A fair description of how this is actually solved, and the reason the enrichment layer sits underneath the CRM rather than inside it. Worth noting the same thread has a reply accusing another answer of being generated, which is the state of advice on this topic.
I'm trying to prevent sales reps from prospecting accounts that are already clients. Does anyone have advice on how to make it easy to see in Linked In who we are already working with?
r/sales·June 2021·5 points
This is exactly what CRM badges and CRM-aware search filters do, and it has been shipped the whole time. Five years on, the question is still being asked, which says more about how the feature is sold than about the feature.
The sales team in my organisation uses LinkedIn A LOT. For most of the reps it's their primary channel
r/salesforce·July 2022·6 points
The activity writeback half of this integration is the answer, and it is also the half with a per-user authentication that expires every 90 days. A rollout that does not plan for the re-prompt gets quietly half the coverage it paid for.
The threads are mostly people trying to get LinkedIn data into Salesforce by some route other than this one, which is the useful signal. What they want is almost always the same thing: current employment on records that are going stale. The integration answers part of that through data validation, and the part it does not answer is why these threads keep ending in a discussion of scraping, waterfalls and manual work.
Read together, the threads say the integration is better than its reputation and narrower than people hope: it surfaces LinkedIn inside Salesforce, and it does not hand you LinkedIn's data as your own.
Salesforce got CRM Sync first and it shows in the depth of the Salesforce side: matching, badges on search results, activity writeback and attribution reporting all landed here before they landed anywhere else. If you are comparing this pair against the HubSpot one, the Salesforce integration is the more complete of the two and the harder one to install.
The edition question is identical though, and it is worth stating plainly because it decides everything else. Advanced Plus is a quoted edition. If the quote comes back higher than the value of getting InMail activity onto the timeline, the correct answer is to not do this and to solve the activity problem another way, not to buy a cheaper edition and hope.
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 Salesforce, 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.
Yes, and the Salesforce side is the more mature of the two CRM Sync integrations because it shipped first. Leads and accounts auto-save into Sales Navigator lists, InMail and message activity writes back as Salesforce activities, and CRM badges show on search results so reps can see what is already owned.
Advanced Plus, for anything that writes. The embedded profile widget runs on Advanced; activity writeback, record creation and matching do not. This is the same gate as the HubSpot pair and it is the decision that settles the project.
One with API access. Editions without it cannot run this regardless of which Sales Navigator edition you hold, which rules out the lower editions before you reach any configuration screen.
Longer than the HubSpot equivalent, because the install touches Salesforce metadata. Expect a Salesforce admin, a sandbox pass and a change window rather than a marketplace click.
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.