Partner spotlight: Lemlist
Lemlist is a multichannel sales outreach platform founded in 2018 in Paris. See how it connects to OutboundSync to sync activity into your CRM.
Jason Ma
Lemlist → Salesforce
Bring every Lemlist touch into Salesforce. OutboundSync logs email and social steps on the Lead or Contact, and keeps Lemlist Unsubscribe in step with your Salesforce reports.
Lemlist connects to Salesforce through OutboundSync. Email sends, opens, clicks, replies, bounces, and unsubscribes, plus connection requests, social messages, and social replies, are logged on the matching Lead or Contact as Tasks, or as EmailMessage records for email. Salesforce reports can also feed Lemlist's Unsubscribe list, so suppression follows your CRM.
| Status | Live |
|---|---|
| Channels | Email and social |
| Direction | Activity Lemlist → Salesforce; block lists Salesforce → Lemlist |
| Salesforce records | Leads, or Contacts and Accounts |
| Block lists | Yes, from Salesforce reports |
| Lemlist plan | Needs webhook access |
| Setup | Self-serve: create an External Client App, then connect it in OutboundSync |
Salesforce reports can only credit the activity they can see, and email-only logging misses every social step. OutboundSync writes each Lemlist step as a Task on the Lead or Contact, with optional OutboundSync fields for the latest activity. Subject templates carry the event and campaign, so a report can split email from social without manual tagging.
Suppression works from the same source. Point OutboundSync at a Salesforce report, for example Contacts on open opportunities or accounts another team owns, and the people in it are pushed to Lemlist as Unsubscribe entries. Each list picks Email for addresses and domains, or Social for profile URLs.
Every event below arrives in near-real time and lands on the matched Salesforce record. Pick the ones you want per source.
| Event | Channel | Where it lands in Salesforce |
|---|---|---|
| Email sent | Task or EmailMessage on the Lead or Contact | |
| Email opened | Task on the Lead or Contact, plus optional OutboundSync fields | |
| Link clicked | Task on the Lead or Contact, plus optional OutboundSync fields | |
| Reply received | Task or EmailMessage on the Lead or Contact | |
| Email bounced | Task on the Lead or Contact, plus optional OutboundSync fields | |
| Lead unsubscribed | Task on the Lead or Contact, plus optional OutboundSync fields | |
| Lead category updated— Interested and Not Interested, from email and social | Task plus optional OutboundSync fields on the Lead or Contact | |
| Connection request sent | Social | Task on the Lead or Contact |
| Connection request accepted | Social | Task on the Lead or Contact |
| Social message sent— Includes voice notes | Social | Task on the Lead or Contact |
| Social reply received | Social | Task on the Lead or Contact |
| Profile viewed | Social | Task on the Lead or Contact |
Event names come from the Lemlist webhooks OutboundSync receives. See the Lemlist event reference.
Push a report of Contacts on open opportunities to Lemlist Unsubscribe.
Trigger a Salesforce Flow when a prospect answers a Lemlist social message.
Report which Lemlist channel produced the first reply on won opportunities.
The options teams weigh before they commit a production sync.
| Option | What it does | Trade-off |
|---|---|---|
| Zapier, Make, or n8nCompare integration platforms | Catch Lemlist webhooks and write each event to Salesforce with a workflow you build. | Every event type, retry, and field change is a workflow you maintain, billed per task or step. |
| Custom buildBuild vs buy | Write your own service against the Lemlist and Salesforce APIs. | You own matching, deduplication, API limits, and every upstream schema change. |
| OutboundSync | Pre-built email and social activity sync into Salesforce Leads and Contacts, with Salesforce reports pushed back as block lists. | Self-serve setup, searchable event logs, and support from the team that maintains the connector. |
A Salesforce admin creates an External Client App, then connects it in OutboundSync and picks Task or EmailMessage logging.
Add your Lemlist API key in OutboundSync, then paste the source's webhook URL into Lemlist.
Pick which Lemlist events to log, whether they write Tasks or EmailMessage records, and which OutboundSync fields to fill.
Point a Salesforce report of customers, open deals, or do-not-contact records at Lemlist so they never get cold outreach.
Trigger one Lemlist event and confirm it on a real Lead or Contact.
Turn on the source and start building Salesforce reports, dashboards, and Flows on real Lemlist data.
Needs webhook access
OutboundSync receives Lemlist activity through webhooks. Confirm your Lemlist plan includes webhook access, or ask us to check during setup.
OutboundSync works across Salesforce editions. The difference is API capacity: plan for roughly 6 API calls per sent email once replies and status events are counted.
| Edition | Fit | What to know |
|---|---|---|
| Professional | Limited support - API limits may restrict ongoing sync. |
|
| EnterpriseMost common | Recommended - Best balance of capability, API capacity, and cost. |
|
| Unlimited | Ideal - Best for scale and high activity volume. |
|
Millions of activities synced every month
EliseAI
Yotpo
Ona
HG Insights
Finout
HologramTutorials, case studies, and updates related to Lemlist.
Lemlist is a multichannel sales outreach platform founded in 2018 in Paris. See how it connects to OutboundSync to sync activity into your CRM.
Jason Ma
OutboundSync now supports beta one-way sync of Lemlist email and social activity into Attio, Close, HighLevel, HubSpot, Pipedrive, and Salesforce.
Harris Kenny
A quick walkthrough with your own stack. Setup takes minutes, with no long-term contract.
