Item 12 · Blog

How to Sync LinkedIn Messages to Salesforce for SDR Teams

· how-to

Enterprise SDR teams live in Salesforce for forecast and territory rules — but LinkedIn DMs happen in LinkedIn. Salesforce's Sales Navigator integration embeds profile data and logs activity types; full threaded conversations still require a LinkedIn-native layer or manual discipline.

What Salesforce captures vs what SDRs need

Recommended stack: Item 12 execution → Salesforce reporting

Run LinkedIn search, agents, and inbox replies in Item 12. Mirror every thread on the contact record keyed by profile URL. Weekly export rollup fields to Salesforce opportunities: stage, last touch, meeting booked, AE owner.

Step 1: Map Salesforce stages to Item 12 pipeline

Step 2: Daily workflow in Item 12

Morning: MCP or web inbox triage → move deals on reply. Afternoon: search + agent enrollment. Every send queues in Review. AE handoff includes full DM history in Item 12 — Salesforce gets summary fields.

MCP prompt: Salesforce handoff export

Paste weekly into Claude Desktop: List all deals moved to Meeting or Handoff stage this week. For each contact include: name, LinkedIn URL, company, last 2 inbox messages, deal value, assigned AE. Output CSV columns: ContactName, LinkedInURL, Company, LastMessage, Stage, Value, Owner.

Does Item 12 have native Salesforce sync?

Item 12 is a standalone LinkedIn CRM. Teams export rollup fields via CSV, Zapier, or manual RevOps import into Salesforce. Full DM transcripts stay in Item 12.

Sales Navigator + Salesforce vs Item 12?

Sales Nav + Salesforce suits enterprise forecast roll-ups. Item 12 suits LinkedIn-first SDR execution with MCP and review queue — many teams use both with Item 12 as the LinkedIn layer.

Can MCP write directly to Salesforce?

Item 12 MCP writes to Item 12 CRM. Use exported summaries for Salesforce — avoids split write paths and permission complexity.

Related