How the LinkedIn Sales Navigator Salesforce Integration Changes Lead Handoff

The Sales Navigator Salesforce integration connects LinkedIn's prospecting platform to your CRM, automating the flow of account data, contact records, and activity logs between the two systems. According to Salesforce, the integration automatically imports accounts and contacts associated with open opportunities from Salesforce into Sales Navigator, logs InMail messages and notes directly into Salesforce, and installs a CRM widget that displays LinkedIn information inside Lead and Contact records.

For outreach teams, the integration changes lead handoff in three ways. First, it eliminates manual data entry by syncing records bidirectionally. Second, it enforces field mapping rules set by the Salesforce admin, which determines what information flows from Sales Navigator into the CRM. Third, it respects user permissions and assignment rules, so SDRs and AEs can only create or update records they have write access to in Salesforce.

The integration requires a Professional, Enterprise, Unlimited, Developer, or Performance edition of Salesforce with API access enabled, and Sales Navigator Advanced Plus with CRM Sync turned on. LinkedIn states that admins must authenticate the connection through OAuth, and individual users must sign into Salesforce from within Sales Navigator to create Lead records.

How does the Sales Navigator Salesforce sync work?

The sync operates in two directions. Salesforce pushes account, contact, and lead records associated with open opportunities into Sales Navigator, while Sales Navigator writes back activity logs, InMail messages, and newly created Lead records into Salesforce.

According to LinkedIn's technical documentation, admins configure the sync from the Admin Settings panel in Sales Navigator by scrolling to the CRM Settings section and clicking Change. The admin selects the opportunity stage that defines when an account enters the pipeline, and optionally sets a Lead Source value that will be applied to all Lead and Contact records created from Sales Navigator.

Once enabled, Sales Navigator imports accounts and contacts tied to opportunities that meet the stage criteria the admin selected. The system also surfaces suggested leads based on CRM data combined with LinkedIn's algorithms. LinkedIn notes that the Salesforce Import feature strictly pulls data into Sales Navigator and does not write customizations back to Salesforce unless the admin enables Lead or Contact creation.

What fields does Sales Navigator map to Salesforce during lead creation?

When a user creates a Lead record from Sales Navigator, the integration populates a predetermined set of standard Salesforce fields. LinkedIn's technical document specifies that the following fields are supported: First Name (required), Last Name (required), Company (required if it exists in LinkedIn data), Title, Mailing Country, Email, Phone, and Lead Source.

LinkedIn populates First Name, Last Name, Mailing Country, Title, and Company automatically from the LinkedIn profile. Email and Phone are pre-populated only if they have already been entered directly into Salesforce or Sales Navigator by the user. The Lead Source value is set by the admin during the initial CRM Settings configuration and applies to both Lead and Contact records.

The integration does not support custom field mapping. LinkedIn states that Lead Creation supports a predetermined set of standard fields which cannot be customized by the admin. If your Salesforce instance relies on mandatory custom fields or validation rules on unsupported fields, Lead Creation may fail unless you adjust those rules.

How do I enable Lead and Contact creation from Sales Navigator?

Only Sales Navigator admins on an Advanced Plus contract with CRM Sync already enabled can turn on Lead and Contact creation. LinkedIn's instructions require the admin to log into Sales Navigator, click Admin at the top of the page, select Admin Settings, scroll to the CRM Settings section, and click Change.

Inside the CRM Settings panel, the admin scrolls to the section labeled Allow lead creation from Sales Navigator and toggles it to Yes. The admin then selects a Lead Source value from the picklist, which represents existing values in Salesforce. LinkedIn recommends setting a Lead Source value, though it is optional. The same Lead Source will be applied to both Lead records and Contact records if Contact Creation is also enabled.

Once enabled, individual users must authenticate with Salesforce through the OAuth flow before they can create Lead records. LinkedIn specifies that users are restricted to signing into the same Salesforce instance that is already connected to CRM Sync and will receive an error message if they attempt to connect to a different instance. Users with read-only access in Salesforce can authenticate but cannot complete the Lead creation operation unless they have write access enabled.

What permissions do users need to write back leads and contacts?

According to LinkedIn, the Salesforce end-user must be allowed to authenticate via OAuth, have API access enabled at the Salesforce org level, and have read and write access to the standard contact fields and the contact record. OAuth will fail if the Salesforce admin has blocked the Sales Navigator Salesforce app.

Users also cannot have custom validation rules applied to unsupported fields on the Lead record. If a validation rule requires a custom field that Sales Navigator does not map, the Lead creation operation will fail. LinkedIn notes that a user with read-only access can still authenticate and proceed with Lead creation, but cannot complete the operation unless write access is enabled.

LinkedIn clarifies that Lead creation runs on behalf of each individual CRM user who must go through their own OAuth process. As a result, users cannot perform any action or write back any information they cannot do within Salesforce, and user activity is subject to whatever level of auditing comes with the user's Salesforce system.

How does lead ownership get assigned during handoff?

Sales Navigator respects the user assignment and ownership rules configured in Salesforce. LinkedIn states that leads are suggested to Sales Navigator license holders based on user assignment in the CRM. When a lead is imported from Salesforce into Sales Navigator, it is mapped directly to the same user account.

When a Sales Navigator user creates a new Lead record, the ownership is assigned according to Salesforce's default Lead assignment rules or directly to the creating user if no assignment rules are in place. LinkedIn's documentation does not mention an override mechanism within Sales Navigator, so ownership follows the rules already established in your Salesforce instance.

If your organization uses round-robin assignment, territory-based routing, or other automated assignment logic in Salesforce, those rules will apply to Lead records created from Sales Navigator just as they would to leads created directly in Salesforce.

What activity gets logged back into Salesforce?

The integration logs InMail messages and notes from Sales Navigator directly into Salesforce, according to Salesforce's integration overview. This allows sales managers to see the full conversation history without switching between platforms.

LinkedIn notes that matching a Sales Navigator profile to an existing Salesforce Lead or Contact record does not trigger a logged event in Salesforce, because no data is updated during the match. However, sending an InMail, creating a Lead, or updating a Contact will create an activity record in Salesforce that reflects the action taken in Sales Navigator.

LinkedIn's technical document specifies that Sales Navigator uses Salesforce's REST API to create Lead records and retrieve required custom fields, lead source values, and mailing country code picklists. The Create a record API is used to create new Lead records, and the SObject Describe API is used to fetch picklist values and custom field requirements.

How do I verify the sync is working correctly?

After enabling the integration, admins can verify sync status from the CRM Settings section in Sales Navigator Admin Settings. LinkedIn states that you will be able to see which CRM is synced with Sales Navigator and the last synced date.

To check individual user connections, users should navigate to Settings in Sales Navigator and scroll to the CRM settings section at the bottom. This panel shows which Salesforce instance the user is signed into and provides a sign-out option if they need to reconnect to the correct instance.

If Lead Creation is not working, LinkedIn recommends verifying that the user is authenticated to the same Salesforce instance connected to CRM Sync, that they have write access to the standard Lead fields, and that no custom validation rules are blocking the operation on unsupported fields.

Field and ownership checklist for clean handoff

Use this checklist to verify that your Sales Navigator Salesforce integration is configured for clean lead handoff between SDRs, AEs, and relationship managers.

• Admin configuration: Confirm that CRM Sync is enabled in Sales Navigator Admin Settings, the correct opportunity stage is selected to trigger auto-import, and a Lead Source value is set for records created from Sales Navigator.
• Field mapping: Verify that First Name, Last Name, and Company are populated automatically from LinkedIn profiles, and that Email and Phone are pre-populated if already entered in Salesforce or Sales Navigator.
• User permissions: Ensure that all Sales Navigator users have OAuth enabled, API access at the Salesforce org level, and read and write access to standard Lead and Contact fields.
• Custom validation rules: Review Salesforce validation rules on the Lead object to confirm that no rules require custom fields unsupported by Sales Navigator, or adjust rules to allow Lead creation without those fields.
• Ownership rules: Verify that Salesforce Lead assignment rules (round-robin, territory-based, or user-based) are correctly configured and that leads imported from Sales Navigator are assigned to the expected users.
• Activity logging: Confirm that InMail messages and notes sent from Sales Navigator appear as activity records in Salesforce under the correct Lead or Contact.
• User authentication: Check that each user has signed into the correct Salesforce instance from within Sales Navigator by navigating to Settings and reviewing the CRM settings section.

Limits and guardrails to know

LinkedIn imposes monthly limits on Lead and Contact creation and updates to stay within Salesforce's API call limits. According to LinkedIn's FAQ, the Lead and Contact Creation features are limited to 1,000 contacts per user per month, and the Lead and Contact Updates features are limited to 1,000 contacts per user per month. If a user hits the limit, they will receive an error message.

LinkedIn notes that Salesforce's standard license allows a daily limit of 1,000 API calls per person, and the Sales Navigator limits are set well below that threshold. Page-level permissions in Salesforce are not enforced through Lead Creation because all interaction occurs via REST API.

If you disconnect CRM Sync, LinkedIn states that previously imported CRM data will be deleted within 30 days if you select the option to clean up all previously imported CRM data during the disconnect process. Manually saved accounts and leads are not affected by the disconnect.