Skip to content

Lemlist

When to use this guide: Read this before configuring Lemlist with OutboundSync to confirm what the integration covers today.

OutboundSync supports Lemlist as an engagement-platform source for email and LinkedIn campaign activity. Lemlist events are received by OutboundSync and written into HubSpot or Salesforce as activity on the matching contact or lead record.

What this integration does

Section titled “What this integration does”

Lemlist is an omnichannel sales engagement platform for email and LinkedIn outreach. OutboundSync maps Lemlist activity into CRM timelines so reps and RevOps can see campaign activity without relying on exports or manual logging.

Lemlist can also be used in partner-routed workflows through Master Inbox. When Lemlist is connected that way, use the Masterinbox docs and onboarding path for the current setup steps.

What syncs into your CRM

Section titled “What syncs into your CRM”
  • Email sends, opens, clicks, replies, bounces, and unsubscribes
  • Reply/category updates when provided by Lemlist
  • LinkedIn connection requests, messages, replies, and category updates
  • Campaign, lead, account, and timestamp metadata when available

Where it syncs

Section titled “Where it syncs”
  • HubSpot — direct integration or partner-routed setup, depending on account configuration
  • Salesforce — direct integration or partner-routed setup, depending on account configuration
  • Close — direct integration during the current Close beta
  • Attio — supported via Master Inbox during the current Attio beta
  • HighLevel — supported during the current HighLevel beta
  • Pipedrive — supported during the current Pipedrive beta

Category-based filters

Section titled “Category-based filters”

Optionally hold Lemlist email and LinkedIn activity until a lead is marked with an allowlisted category, then release the held history into your CRM. For the shared hold-and-release lifecycle, see How category-based filters work.

Lemlist exposes exactly two categories for this filter: Interested and Not Interested. Unlike Smartlead or EmailBison, filtered sync does not require a Lemlist API key — OutboundSync populates those two options statically in the webhook builder.

Enable in OutboundSync

Section titled “Enable in OutboundSync”
  1. Open the Lemlist webhook in OutboundSync and edit its settings.
  2. Under Approved events for data sync, choose the filtered option (FILTERED data syncs to your CRM).
  3. Under Category-based filter, select Interested and/or Not Interested.

When a lead hits an allowlisted category, OutboundSync releases held activity for that webhook, campaign, and lead. If the lead later leaves every allowlisted category, new activity is held again until they match the filter.

Events that unlock sync

Section titled “Events that unlock sync”

These Lemlist interest events map to Lead Category Updated in OutboundSync:

  • Email Interested
  • Email Not Interested
  • LinkedIn Interested
  • LinkedIn Not Interested

Include these interest events when the Lemlist webhook is configured — both Interested and Not Interested — so category state stays accurate even if you only allowlist Interested (the OutboundSync team can do this during guided setup). Test with a category event first — see Sending test webhook payloads.

This section applies to direct Lemlist webhooks. If Lemlist activity reaches OutboundSync through Master Inbox, confirm filtered-sync behavior during onboarding.

Block lists

Section titled “Block lists”

OutboundSync can push a HubSpot list or Salesforce report into Lemlist Settings → Unsubscribe as channel-level unsubscribe variables. That is the same product as block lists for Smartlead, Instantly, and EmailBison, plus a social channel for LinkedIn profile URLs.

Create the Lemlist API key first under Connected Accounts. Block lists require that key. Category-based filtered sync still does not.

When you create the block list, choose Email or Social:

  • Email — emails as-is (jane@acme.com) and domains with an @ prefix (@acme.com). Contacts can still be reached on LinkedIn.
  • Social — LinkedIn profile URLs from the CRM list. Lemlist has no HeyReach-style leads / exclusion list; only the profile URL is pushed. Contacts can still be emailed.

Lemlist also has a global “do not contact” that blocks every channel. OutboundSync does not write that. Global DNC needs a Lemlist contactId we do not resolve. Phone numbers are also out of scope.

Sync is CRM → Lemlist and additive. New CRM memberships are unsubscribed; people who leave the CRM list stay on Unsubscribe until you remove them in Lemlist. See Block lists vs exclusion lists and the block list maintenance guide.

Scope and current limitations

Section titled “Scope and current limitations”
  • Activity is one-way. Campaign events flow Lemlist → CRM. Block lists are the exception: CRM lists push into Lemlist Unsubscribe; OutboundSync does not un-block when someone leaves the CRM list.
  • Channel-level Unsubscribe, not global DNC. Email and LinkedIn are blocked independently. Phone activity is out of scope.
  • Guided setup. Setup is currently handled with the OutboundSync team during onboarding.
  • Partner-routed setups differ. If your Lemlist activity reaches OutboundSync through Master Inbox, event availability and setup steps are confirmed during onboarding.

Get help and next steps

Section titled “Get help and next steps”