lemlist integrations

lemlist integrations, and what arrives as a note

Three integrations, and the cheapest one is the most native. The HubSpot pair costs nothing extra on either side and syncs both ways, while the other two are builds where the interesting question is which enrichment runs first.

lemlist.com 3 integrations
layerEngagement
entry$0/mo
authHTTP Basic, not Bearer. Empty us...
automationSequences, conditions and webhoo...
verified2026-09-18
checked Guides written 3 of 3
3integrations checked
2built natively
1sync both ways
0need a plan upgrade
The short version

What decides a lemlist integration

Email and LinkedIn steps in one sequence.

lemlist runs email and LinkedIn touches in the same sequence, which is why its CRM integration has to carry more activity types than a pure sender does. That is also where the surprise is: HubSpot treats only sent and replied emails as Email objects, so opens, clicks, bounces and most LinkedIn actions arrive as notes instead. The data is all there, and it is not where a reporting dashboard expects to find it.

The second thing to know is the authentication, because it costs people an afternoon. lemlist uses HTTP Basic rather than Bearer, the username is empty and the key is the password, so the string to base64 encode starts with a colon. The Reverse Contact build spends its first section on exactly that, and the published rate limit of 20 requests per 2 seconds is rarely what stops you.

The third is that lemlist sells enrichment itself, including a bulk endpoint. Running a second provider alongside it is a decision about order rather than a toggle, because rows both can fill get paid for twice. The Clay pair has the same shape from the other end: Clay fills the row and pushes it into a campaign, and nothing comes back.

lemlist sits in the engagement layer, with 5 other tools in this directory. Counted across the whole directory it reaches 3 of the other 22 tools, and the integration matrix shows that row against every other.

All 3

Every lemlist integration, with what it moves

Start with how the integration is built, because a native app and a webhook you maintain are the same feature with completely different owners.

The data layer

Whichever of these you connect, the integration moves the record. We fill it.

Start for free
Showing 3 of 3
↔

lemlist and HubSpot

Two-way sync
BuiltNativeMarketplace app
WatchNo upgrade needed

Opens and clicks arrive as notes, because HubSpot will not let a third party write them.

  • Moves: Contacts, Companies, Activities
  • Needs: A paid lemlist plan (there is no free tier), plus admin access on both sides
Included on both sides · hours Read the guide
→

lemlist and Clay

One way, out
BuiltNativeBuilt on the API

Three actions, an API key, and a campaign that has to exist first.

  • Moves: Contacts, Lists
  • Needs: Clay Launch or above, a lemlist API key, and a campaign that already exists
Metered by usage · minutes Read the guide
Buyer's guide

How to pick, and what to check first

4 things that decide whether a lemlist integration will work for you, in the order they usually bite.

01

Most activity is a note, by HubSpot rule

Only sent and replied emails become HubSpot Email objects. Opens, clicks, bounces, failures, campaign state changes and most LinkedIn actions become notes, because HubSpot reserves the Email object for those two. Anything counting emails from the timeline will undercount, and anything reading notes will find the rest. Decide which object your reporting reads before you build the dashboard on it.

02

Basic auth, with a colon in front of the key

lemlist uses HTTP Basic rather than Bearer. The username is empty and the password is the API key, so the string to encode is a leading colon followed by the key. Almost every failed first attempt against this API is a missing colon, and the error does not say so. The published limit is 20 requests per 2 seconds on all routes, metered per key, and the reset header comes back as a human-readable date rather than a timestamp.

03

Field mapping does not backfill

Fields mapped after you import leads or launch a campaign do not fill in retrospectively, and custom properties have to exist in HubSpot before lemlist can map to them. The practical consequence is that mapping is a setup step rather than something to tune later. Manual unsubscribes have the same shape: lemlist pushes an unsubscribe only when the lead does it themselves, so somebody moved by hand never reaches the CRM.

04

Two enrichment sources need an order, not a toggle

lemlist ships its own enrichment, so adding a second provider means deciding which runs first rather than switching one on. Rows that both can fill are paid for twice if nothing decides between them. A missing variable renders its fallback text rather than stopping the send, which is the behaviour you want and also the reason an unenriched row is easy to miss. Check the fallbacks before a send rather than after it.

Written up

The lemlist integrations with a full guide

Each one covers what syncs in which direction, the tier it needs, the limits that bite, when not to use it, and the questions people ask before they start.

Other tools

Integrations for the rest of the stack

Connecting lemlist is half the job

An integration moves a record from one system to another. It does not make the record worth moving. Reverse Contact is the layer underneath: one API that resolves an email, a domain or a profile URL into a verified people and company record, with a confidence score instead of a guess.

Free trial, no card required, and 500 credits to start.

FAQ

lemlist integrations, asked and answered

The questions that come up before anyone opens a setup guide.

Does lemlist have a native HubSpot integration?

Yes, and it is one of the five integrations in this directory that costs nothing extra on either side. It is configured once at team level, contacts and companies sync with a direction you choose per field, and campaign activity lands on the HubSpot timeline. The catch is which object that activity becomes: only sent and replied emails are Email objects and the rest are notes.

How do I authenticate with the lemlist API?

HTTP Basic, not Bearer. The username is empty and the API key is the password, so the string you base64 encode begins with a colon. The rate limit is 20 requests per 2 seconds on all routes, metered per API key, and the X-RateLimit-Reset header comes back as a human-readable date rather than a Unix timestamp, which breaks code that assumes an integer.

Can Clay push leads into a lemlist campaign?

Yes, from Clay Launch or above, with three actions: add, update and look up. Each one takes a campaign that already exists, because Clay cannot create a campaign, so the sequence design and the sending mailboxes stay lemlist decisions. Nothing returns to Clay, so the table cannot suppress on engagement and cannot report on what the list produced.

Should I use lemlist enrichment or a separate provider?

That is an order-of-operations question rather than an either-or. lemlist ships its own enrichment including a bulk endpoint, so running a second provider without deciding which goes first means paying twice on every row both could fill. Pick one to run first, let the second fill only what is still empty, and check the fallback text, because a missing variable renders the fallback rather than stopping the send.

Checked by

Reverse Contact

We sell B2B people and company data, and we publish this directory. Every tier requirement, sync direction and limit behind the 3 integrations on this page was read from a vendor's own knowledge base, developer documentation or pricing page on the date below. Nothing on it is restated from a press release or a third-party listing.

Where a vendor publishes no public figure, this page says so rather than estimating, which is why no page here prints a cost per enriched record. Reverse Contact appears in this directory as a data provider and publishes it. No other vendor pays for placement, and every link out of a listing or a citation carries nofollow, including the ones that point at Reverse Contact. The only followed links on this page are the two calls to action and the reviewer.

Tier requirements, sync behaviour and documented limits change without notice. Confirm against your own contract before you budget. What has changed since · How we checked, and what we will not claim

Researched and written by

Eugene Suslov

Researched and wrote every page in this directory, and checked every tier requirement, sync direction and documented limit against the vendor's own knowledge base, developer documentation or pricing page.

Verified
2026-09-18
Sources
6 vendor documents
Paid placement
None

Tier requirements, sync behaviour and limits read from each vendor's own documentation in September, October and November 2026. Vendors change these without notice.

Reverse Contact appears in this directory as a data provider and publishes it. Every other tool is here on merit and nobody pays for placement.

Ask an assistant