LeadIQ + Salesforce Integration Guide: Full Setup 2026

Your reps prospect on LinkedIn, your pipeline lives in Salesforce, and right now the bridge between the two is copy-paste. Contacts arrive with missing fields, duplicates pile up, and nobody fully trusts the CRM anymore. A proper LeadIQ Salesforce integration fixes exactly this, one-click capture from LinkedIn straight into clean Salesforce records, but only if you configure it deliberately. Done carelessly, the same integration becomes a machine for mass-producing duplicates and overwriting good data.

LeadIQ is a prospecting platform built around capturing contact data while reps browse LinkedIn, enriching it with verified emails and phone numbers, and pushing it into your CRM. Salesforce is where that data has to land correctly, because every workflow downstream, routing, sequencing, reporting, depends on record quality.

We integrate prospecting tools with CRMs as part of the outbound systems we build, so this guide walks through the full setup in the order we would actually do it, including the safeguards most teams skip.

Before You Start: What You Need

Three prerequisites, confirm them first.

A LeadIQ plan that includes CRM integration, the Salesforce connection is available on paid tiers. Salesforce Professional edition or higher with API access enabled, Enterprise and Unlimited have it by default. And a Salesforce user account with permission to create and edit Leads and Contacts, plus access to the objects you will sync.

Strongly recommended: a Salesforce sandbox. Every step below works in production, but testing field mapping against live data is how clean CRMs get damaged.

Step 1: Connect LeadIQ to Salesforce

In LeadIQ, open Settings, then Integrations, and select Salesforce. You will be redirected to a Salesforce OAuth login screen, authenticate and approve the requested permissions, and the connection is established.

The decision that matters here: which Salesforce user authorizes the connection. Use a dedicated integration user if your Salesforce edition allows it, rather than a rep's or admin's personal account. Every record LeadIQ creates will be stamped with this user, which keeps audit trails clean, and the integration will not break when an individual employee leaves and their account is deactivated.

Once connected, LeadIQ pulls in your Salesforce schema, objects, fields, and picklist values, which you will use in the next step.

Step 2: Configure Field Mapping

This is the highest-stakes step in the entire setup. In LeadIQ's integration settings, open the field mapping panel. You will map LeadIQ's data points, name, title, company, verified email, phone, LinkedIn URL, and so on, to specific Salesforce fields on the Lead and Contact objects.

Work through it field by field:

Two rules to apply throughout. First, create a custom field for the LinkedIn URL rather than stuffing it into Description, you will want it filterable later. Second, hardcode a Lead Source value so every LeadIQ-created record is identifiable, which makes reporting on the integration's actual contribution possible, and makes a mass rollback possible if anything ever goes wrong.

Set overwrite behavior to "fill empty fields only" anywhere your team manually curates data. Enrichment data is good, but a rep's hand-verified direct dial should never be silently replaced by a database guess.

Step 3: Set Dedupe Rules on Both Sides

Duplicates are the number one complaint with any capture tool, and prevention has to live in two places.

In LeadIQ: enable the duplicate check so the extension searches Salesforce before creating a record. When a rep captures someone who already exists, LeadIQ should surface the existing record and offer to enrich it instead of creating a sibling. Configure matching on email first, then name plus company as the fallback.

In Salesforce: confirm your native Duplicate Rules and Matching Rules are active for Leads and Contacts, and that they apply to records created via API, there is a checkbox for exactly this, and integrations bypass duplicate rules in many default configurations. Set the rule to block or alert on a match against email, and to match Leads against existing Contacts, not just other Leads, since the most painful duplicate is a "new lead" who is already an active customer contact.

Step 4: Set Up the Capture Workflow From LinkedIn

Now the part reps actually touch. Each rep installs the LeadIQ browser extension and logs in. When they view a LinkedIn or Sales Navigator profile, the extension panel shows the person's enriched data, verified email, phone, title, company, alongside a capture button.

Decide as a team where captures land. The standard flow pushes new people into Salesforce as Leads, while prospects at companies with existing Accounts can be captured as Contacts under that Account. Pick one convention and document it, mixed conventions are how the same person ends up as both a Lead and a Contact.

LeadIQ also supports capturing into lists or directly into a connected sequencer. If you run sequences, set the flow so the Salesforce record is created first and the sequence enrollment references it, keeping the CRM as the source of truth.

Step 5: Configure Enrichment Sync

Beyond capture, LeadIQ can refresh data on records over time, updated titles after job changes, newly verified emails, additional phone numbers. In the integration settings, choose which fields enrichment is allowed to update and on what cadence.

Be conservative. Let enrichment update clearly factual, fast-decaying fields like title and phone. Keep it away from fields that drive automation, lead status, owner, score, and away from anything reps maintain manually. Every enrichment write should respect the same "fill empty only" defaults from Step 2 unless you have a specific reason to allow overwrites.

Step 6: Set Admin Permissions and Team Roles

In LeadIQ's admin console, separate admin rights from user rights. Admins control field mapping, dedupe configuration, and integration settings, reps capture and enrich. Lock mapping changes to one or two named owners, the single most damaging event in this integration's life is a well-meaning rep "fixing" a field mapping on a Tuesday afternoon.

On the Salesforce side, review what the integration user can touch. It needs create and edit on Leads and Contacts and read on Accounts. It does not need delete rights, modify-all permissions, or access to Opportunities. Scope it to the minimum, an integration credential with broad rights is both a data risk and a security finding waiting to happen.

Step 7: Test Before Rolling Out

Run a structured test pass, ideally in sandbox, before the team gets access. Capture a brand-new person and verify every mapped field lands correctly, including Lead Source. Capture someone who already exists as a Lead, then someone who exists as a Contact, and confirm dedupe catches both. Capture a person at an existing Account and confirm the association. Trigger an enrichment update on a record with manually entered data and confirm nothing hand-curated gets overwritten.

That is 10-20 deliberate scenarios and roughly an hour of work. Only after all of them pass cleanly do you connect production and onboard reps, starting with one or two power users for the first week before the full team.

Common Mistakes That Damage Your CRM

Duplicate floods. Skipping Step 3, or enabling LeadIQ dedupe while Salesforce API enforcement stays off. The result is parallel records, split activity history, and reps working the same prospect twice.

Overwrite-everything field mapping. Leaving overwrite rules at their most permissive lets database enrichment replace hand-verified data. The damage is invisible until a rep calls a number that used to be right.

Capturing into the wrong object. No Lead-versus-Contact convention means the same human exists twice in different objects, and Salesforce reporting can never reconcile them automatically.

No Lead Source stamp. Without it, you cannot measure what the integration contributes, and you cannot surgically undo a bad sync.

Treating verified emails as permanently verified. LeadIQ's verification reflects a moment in time. Before any captured list goes into a sending campaign, re-verify it, the hard bounce target for healthy outbound is under 2%, and months-old captures will not hit that without a fresh pass.

Where a Managed Outbound System Fits

A clean LeadIQ Salesforce integration solves data capture. It does not solve what happens next: building target account lists worth capturing from, sending infrastructure that keeps emails out of spam, copy that earns replies, and someone answering positive replies the same day. Plenty of teams nail the integration and still stall there, with a beautifully enriched CRM and an empty calendar.

That full chain is what we run. LeadHaste is a system orchestrator, we wire 20+ tools, capture and enrichment included, into one outbound machine connected to your CRM, then manage it end to end. Typical campaigns we run see reply rates of 1-5%, with 15-50% of those replies positive, and we report on meetings, not activity. You own the entire system we build, and our guarantee pauses billing if targets are missed. You can read about how we work or browse our case studies to see the model in practice.

Ready to turn captured contacts into booked meetings?

LeadIQ plus Salesforce gets clean data into your CRM. We run everything from there to the calendar, list strategy, infrastructure, copy, and reply handling, with billing that pauses if we miss targets.

Book your free pilot →