Learning Objective
By the end of this guide, you'll know how to access the team-level Salesforce integration in lemlist, configure general sync options, set up field mapping and user mapping, manage activity mapping, and use Logs/API Calls to monitor the integration.
Why This Matters
The Salesforce integration reduces manual CRM updates by syncing contacts and activities between lemlist and Salesforce at the team level, while helping you keep ownership consistent through user mapping.
Prerequisites
Before setting up:
Salesforce admin access to connect and authorize the integration
lemlist admin access to configure team-level settings
15–20 minutes to complete setup
Key Concepts
Team-level integration: Connect one Salesforce account for the entire team. Settings apply to all campaigns automatically.
Contact-based sync: lemlist sync is configured at the contact level (one person can exist in multiple campaigns).
Bi-directional sync: Depending on your mapping settings, updates can sync both ways. Sync typically takes a few minutes.
Exception: Opportunity creation triggers are configured per campaign, not team-wide.
Step 1: Open the Salesforce integration (Team Settings)
In lemlist, click your name/avatar in the bottom-left corner, then select Settings.
In the left sidebar, go to Integrations, then click Salesforce.
Step 2: Confirm connection status
On the Salesforce integration page, confirm you see the Connected status at the top of the page.
Step 3: Configure General settings
In the Salesforce integration, open the General tab.
Under General options, choose whether lemlist should create missing records in Salesforce and how lemlist contacts should be created in Salesforce (Lead or Contact).
Under Set default properties values of new added records, set any default values that should be applied to new CRM records created by lemlist (Contact/Lead/Account/Opportunity).
Step 4: Configure Field Mapping
Field mapping defines how lemlist fields map to Salesforce fields and the synchronization direction.
Open the Field Mapping tab, then map lemlist fields to Salesforce fields in the list (Contacts mapping shown below).
Choose sync direction (per field)
For each mapped field, use the direction icon to set how data syncs between lemlist and Salesforce (for example, syncing in both directions).
Add a custom lemlist field (optional)
In the Field Mapping view, click Add a custom field.
Enter the Field name, choose the Field type, then click Create field.
⚠️ Cannot map to: Formula, Auto Number, or Roll-Up Summary fields.
⚠️ Field mapping is NOT retroactive – only new/updated data syncs after mapping changes.
Step 5: Configure User Mapping
User mapping keeps record ownership and logged activities aligned by mapping lemlist users to Salesforce users.
Open the User Mapping tab, then map each lemlist user to the appropriate Salesforce user.
Fallback behavior: If a lemlist user isn’t mapped, the integration uses the default Salesforce user configured for the connection.
⚠️ You can map multiple lemlist users to one Salesforce user, but not one lemlist user to multiple Salesforce users.
Step 6: Configure Activity Mapping
Use activity mapping to decide which lemlist events should be stored as Salesforce activities.
Open the Activities tab, then enable/disable the activity types you want to sync and choose how each activity should be stored in Salesforce.
To change the Salesforce activity type for an item, click the activity type dropdown on the right side of that row.
Select the desired activity type from the list.
Step 7: Review Logs (for troubleshooting)
Use Logs to verify what synced (and what failed), filter by date range, and refresh the view.
Open the Logs tab, select a date range, then click Refresh.
Step 8: Monitor API Calls
Use the API Calls tab to monitor Salesforce API usage and adjust the limit if needed.
Open the API Calls tab to view the daily limit and daily usage.
Click Update limit if you need to change the configured limit.
Step 9: Configure Opportunity Creation (Per Campaign)
Opportunity creation triggers are set at the campaign level (not in Team Settings).
Go to Campaign Settings → CRM Integration, then select the triggers you want (for example: when lead replies or is marked interested).
💡 Only create opportunities for qualified actions to keep pipelines clean.
Step 10: Import Leads from Salesforce
Go to your campaign → Leads → Import Leads → CRM Import
Select Salesforce
Choose a view filter (Contact, Lead, or Report)
Click Import
What gets imported:
Contact view: Contact field mapping + custom contact fields
Lead view: Lead field mapping + custom lead fields
Report view: Depends on report type (must include
Lead IDorContact ID)
Enrichment: Enable LinkedIn enrichment, email finder, phone finder, or email verifier during import.
Step 11: Avoid Duplicates
lemlist checks for duplicates before creating records.
For Leads/Contacts: Checks Email, LinkedIn URL, First + Last name
For Accounts: Checks Domain, LinkedIn URL
If a match exists, lemlist associates data with the existing record instead of creating a duplicate.
Step 12: Handle Required Fields
If syncing as Leads, Salesforce requires a Company field.
lemlist auto-fills it using:
Contact's most recent company experience
Or experience marked as "primary"
How You'll Know It Worked
✓ Connected status appears in the Salesforce integration page
✓ Field and user mappings are configured under their respective tabs
✓ Activities appear in Salesforce according to your Activities settings
✓ Logs show successful sync operations (and failures when applicable)
✓ API Calls displays current usage
Troubleshooting
Connection fails → Use a Salesforce admin account and confirm API access is enabled.
Fields not syncing → Confirm the field mapping and sync direction, then wait a few minutes. Remember: mapping changes are not retroactive.
Can't map a field → Salesforce field type may be unsupported (formula, auto number, roll-up). Use a different field type.
Activities under the wrong user → Check User Mapping. Unmapped users fall back to the default Salesforce user.
Need proof of what happened → Check Logs and refresh with the correct date range.
Optimization Tips
Start simple: Map only essential fields first (name, email).
Test first: Run a small campaign to confirm the records and activities appear as expected.
Monitor logs regularly: Use the Logs tab to catch mapping or permission issues early.
Watch API usage: Use API Calls to avoid hitting Salesforce limits during large sync periods.