wiki/knowledge/salesforce/linkedin-integration.md · 344 words · 2026-04-05
LinkedIn Integration in Salesforce
Overview
Salesforce supports a free LinkedIn integration that surfaces a LinkedIn profile card directly on contact and lead records. Sales reps can view a matched profile and send messages without leaving Salesforce, reducing context-switching and keeping outreach activity centralized.
This integration was identified as a quick win for [1] during their lead-to-opportunity workflow buildout, where reps need to research and contact prospects efficiently.
How It Works
Once installed, a LinkedIn card appears on the contact or lead record. Salesforce attempts to match the record to a LinkedIn profile using:
- Company name
- Contact name
- Job title
If a match is found, the profile is displayed inline. Reps who are logged into LinkedIn can follow the contact or send a direct message from within the card.
Setup
- The integration is installed via the Salesforce AppExchange (free tier available)
- Each user must log into LinkedIn through the card on their first use — this is a per-user step, not a one-time admin setup
- No Sales Navigator license is required for basic profile viewing and messaging
Note: LinkedIn Sales Navigator offers a deeper paid integration with additional prospecting features. Confirm whether the free integration meets team needs before evaluating Sales Navigator.
Use Cases
- Lead research: Quickly verify a new lead's role, seniority, and company before first contact
- Outreach: Send a LinkedIn connection request or message directly from the lead/contact record
- Account-based prospecting: Identify the right decision-maker at a target firm without switching to a browser tab
Considerations
- Match accuracy depends on data quality in Salesforce (name, title, and company must be reasonably complete)
- The integration requires each rep to have a personal LinkedIn account
- Activity logged via LinkedIn (messages sent, connections made) is not automatically written back to Salesforce activity history — reps should log these manually or via a task