Opens and clicks arrive as notes, because HubSpot will not let a third party write them.
A paid lemlist plan (there is no free tier), plus admin access on both sides
Contacts, Companies, Activities, two-way sync.
A genuinely native two-way integration configured once at team level, which is a better deal than it sounds: contacts and companies sync with a direction you choose per field, and campaign activity lands on the HubSpot timeline without anybody wiring a webhook. The thing to understand before you judge it is that most of that activity arrives as notes. HubSpot does not let third-party applications write to its open and click objects, so only sent and replied emails become Email objects. That is a HubSpot restriction, it applies to every tool in this category, and it decides what your reporting can count.
Object by object, with the direction each one moves in. This is the table to read before the feature list, because a capability that only moves one way is a different product from the one you think you are buying.
| What | Direction | What that means in practice |
|---|---|---|
| Contacts and companies | Both ways | Direction set per field: two-way, HubSpot priority, lemlist priority, or off. Every contact needs an email, a LinkedIn URL or a company domain to match on. |
| Sent and replied emails | One way, in | As HubSpot Email objects, which is the only campaign activity that becomes one. |
| Opens, clicks, bounces and failures | One way, in | As Notes. HubSpot does not permit third-party applications to write to its dedicated open and click objects. |
| LinkedIn messages | One way, in | Sent and replied become LinkedIn Message objects. Profile visits, invites and opens become Notes. |
| Calls | One way, in | As Call engagements with direction, duration, outcome and the owner resolved through user mapping. The contact must exist in HubSpot first or the call waits. |
| Campaign state | One way, in | Paused, resumed, step skipped, meeting booked and interested or not interested, all as Notes. |
One of those six rows moves in both directions. The five that do not are Sent and replied emails, Opens, clicks, bounces and failures, LinkedIn messages, Calls and Campaign state, and those are the rows that decide how you design around this rather than the ones in the brochure.
Two different things are described as mapping on this pair, and only one of them is yours. Fields are mapped by you, per field, with a direction. Activities are mapped by HubSpot's API rules, which decide which object each kind of engagement is allowed to become.
| In HubSpot | In lemlist | What to know about the match |
|---|---|---|
| Contacts | lemlist leads, per-field direction | Two-way, HubSpot priority, lemlist priority or off, chosen field by field. Matching needs an email, a LinkedIn URL or a company domain on the lead. |
| Companies | lemlist company records | Same four directions. Default values can be set for companies lemlist creates, separately from contacts. |
| Deals | Created by lemlist, with defaults | Deal creation triggers are the one setting that is per campaign rather than team-level, and default property values for new deals are set in Advanced settings. |
| Custom properties | Mapped if they already exist | A lemlist custom field can be created and mapped to a HubSpot property. The HubSpot side has to exist first, and mapping is never retroactive. |
| Mandatory properties | A gate on record creation | Rules that decide which leads become HubSpot records at all. A lead failing them is simply not created, with no error on the lead. |
| Users | HubSpot owners, with a fallback | Mapped so activity keeps its owner, with auto-map available and a default owner configured per sync direction. |
| Call statuses | HubSpot call outcomes | Built-in statuses map to the factory outcomes. Custom ones, and portals whose outcomes were recreated, fall back to Connected until mapped by hand. |
| A manual unsubscribe | Nothing | lemlist pushes an unsubscribe only when the lead unsubscribed themselves from the campaign. Somebody moved into the Unsubscribe section by hand does not reach HubSpot. |
Worth knowing before you write a report against it, because the wording below is what you will be filtering and searching on rather than anything you choose.
| The action | How it reads on the record |
|---|---|
| Email sent, email replied | The Email object, and these are the only two that get it |
| Opens, clicks, bounces, failures | Notes. HubSpot does not let a third-party app write to its open and click objects |
| Campaign state: paused, resumed, step skipped, meeting booked, interested | Notes, all of them |
| LinkedIn messages sent and replied | The LinkedIn Messages object, which HubSpot does provide |
| LinkedIn visits, invites, invite accepted, message opens | Notes |
| A call placed with lemlist | A Call engagement, linked to the company too when the contact has one |
Three things are worth knowing before you plan around this mapping, because each one is a decision somebody has to own rather than a setting to find.
Every row above travels as a file: eight field mappings, six action rows and three documented exclusions, each one's note, and the three vendor documents behind them. The CSV opens in a spreadsheet, the JSON is the shape an agent wants, and the Markdown is the table to paste into a ticket.
The split in those two tables is the thing to take into a reporting conversation: you control which fields move and in which direction, and you control none of which object an activity becomes. Deciding where engagement reporting lives before launch is therefore a decision about which tool, not about which setting.
There is no edition grid on this pair: lemlist lists CRM integrations as included on every plan from Email upwards, and nothing on the HubSpot side is gated. The gate that matters is a mapping, and two independent conditions break it in a way that flatters every call your team makes. Pick one on each side and the grid marks the answer.
Pick one on each side.
| The call status in lemlist | HubSpot's factory outcomes | Outcomes deleted and recreated |
|---|---|---|
| A built-in lemlist status | maps correctly | falls back to Connected |
| A custom status your team created | falls back to Connected | falls back to Connected |
Counted off that grid, of four pairings: one gives you maps correctly, three give you falls back to Connected. One working combination out of four is the worst ratio on any grid in this directory, and the failure is the dangerous kind: a dashboard full of connected calls is believable. Map every status by hand unless you have checked that your portal still carries HubSpot's original outcomes.
Every step below is from the two vendors' own setup documentation, in the order they document it. Two of them cost you an afternoon if taken late, so the order is the useful part rather than the clicks.
HubSpot: Settings, Properties
lemlist can only map to a property that already exists, and field mapping is not retroactive. Every custom field you want filled has to be in HubSpot first, which makes this the step that has to come before the interesting ones.
lemlist: HubSpot integration, General settings
Contact and company creation is a setting with a trigger you choose, so you can let lemlist create a HubSpot record on a reply rather than on an import. A team that does not want cold leads in the CRM turns this off here rather than managing it campaign by campaign.
lemlist: Advanced settings
Mandatory property rules decide which leads are allowed to become HubSpot records. A contact that does not meet the conditions is not created, which is the documented reason records go missing and looks identical to a broken sync.
lemlist: Advanced settings, per object
Add a default value per object for Contact, Company or Deal, so a record created by lemlist always carries a lifecycle stage or a lead source. This is the lever that makes lemlist-created records distinguishable in a HubSpot report later.
lemlist: Field Mapping
Per field you choose two-way, HubSpot priority, lemlist priority or off, and you can create a lemlist custom field and map it to a HubSpot property. Changes propagate in two to ten minutes once mapped. Nothing already imported is backfilled.
lemlist: User Mapping
Match each lemlist user to a HubSpot user so activity keeps its owner, with auto-map as a shortcut. Define default ownership separately for each sync direction, because an unmapped CRM owner falls back rather than failing, and the fallback is what every unowned activity gets.
lemlist: Settings, CRM, Activities, Calls
Four toggles are on by default: Calls note, Calls recording, Calls transcript, Calls summary. The recording link lemlist writes into the HubSpot note is public, needs no lemlist account and cannot be revoked. Switch it off now or accept that permanently.
lemlist: the same Calls screen
Built-in statuses map to HubSpot's factory outcomes. A custom status, or a portal whose outcomes were deleted and recreated, falls back to Connected. Map each status explicitly rather than spot-checking, because the failure is silent and flattering.
Steps one and seven are the two that cannot be undone: a mapping added late does not backfill, and a recording link already written into a note cannot be withdrawn. Everything between them is a settings screen you can revisit, which makes this one of the gentler installs on the engagement layer as long as the order holds.
The same sequence, the sync table, the documented limits and the error list ship as one agent skill. Point Claude Code, Cursor or anything that reads a file at this pair as a skill and it has the whole pair without reading two sets of vendor docs first.
curl -o .claude/skills/hubspot-lemlist/SKILL.md https://www.reversecontact.com/integrations-hub/skills/hubspot-lemlist.md
Every limit below is documented by one of the two vendors. They are here because they change decisions, not because they are flaws.
Each of those is documented behaviour rather than a fault, so none of them is going to be fixed by a support ticket. The ones that produce a symptom you would misread are below.
Each one below is a symptom somebody reports, the documented reason behind it, and the fix. Most are configuration rather than faults, which is why they survive a support ticket.
WhyThe status has no mapping. Either it is a custom lemlist status, or your portal's call outcomes were deleted and recreated so the default mapping targets ids that no longer exist.
Map each status explicitly in Settings, CRM, Activities, Calls. Do it for all of them rather than the ones that look wrong, because a correct-looking outcome may be a coincidence.
WhyHubSpot does not allow third-party applications to write open and click data to its dedicated email objects. lemlist stores them as Notes because that is the only place available.
Look in Notes, and filter the Activity tab by type to find them. There is no configuration that moves them, and every tool in this category faces the same wall.
WhyField mapping is not retroactive. It applies from the moment it is set, not to records already imported.
Re-import the affected leads, and from now on create the HubSpot property, map the field, then import. That order is the single most common support thread on this pair.
WhyMandatory properties are enabled and the lead does not meet the required field conditions, so lemlist declines to create the record.
Check the mandatory property rules in Advanced settings against the lead. Also confirm the lead has an email, a LinkedIn URL or a company domain, since matching needs one of the three.
WhyUser mapping is missing or incorrect, so the fallback owner is being used. The fallback is configured per sync direction and applies to everything unmapped.
Map the lemlist user to the HubSpot user in User Mapping, then check the Define default ownership section for each direction rather than just one.
WhyNeither exists when the call ends: they arrive on a later refresh. The call may have no summary at all, or it came from Aircall or Ringover rather than lemlist calling.
Reopen the record later, confirm the call in lemlist actually has both, and check Calls transcript and Calls summary are on. Syncing never generates a summary that does not already exist.
Whylemlist rebuilds the note on every refresh rather than merging it, so a manual edit is replaced.
Write call notes in lemlist on the call record. Also note the 65,000 character cap: longer content is cut from the end, which means the transcript goes first with no warning.
Whylemlist only pushes the unsubscribe when the lead unsubscribed themselves from the campaign. A lead added to the Unsubscribe section by hand is not pushed.
Handle manual opt-outs on the HubSpot side as well, as a process rather than a setting. In a team that manages opt-outs by hand this is a compliance gap rather than a nuisance.
If none of those is it, the next thing to check is the thing most pairs fail on: whether the plan you are on carries the feature at all, which the grid above answers. The same symptom on another pair is often the same cause, so the directory indexes all of them by the message rather than by the integration.
The right-hand column is the one worth being honest about, because every item in it is a reason to spend the budget somewhere else in the stack rather than a reason to configure harder.
Searched for this pair by name, in the words a person would use. 14 threads from 2023 to 2026 were read in full on 11 October 2026, and the 5 below are the ones that carry a point. Each is one person's experience rather than a measurement, and the vendors' own documentation is what the rest of this page rests on.
The integration is not at its best. Most fields are not customizable.
r/CRM·October 2024·1 points
Answering somebody who wanted a HubSpot lead status set from lemlist campaign activity and found that the only automatic outcome was a deal card. Two years on, the documented feature set includes a direction per field, lemlist custom fields mapped to HubSpot properties, and default property values on records lemlist creates. Worth knowing when you read an older thread about this pair.
I really appreciate your thoughtful response. I'm happy to share that Lemlist supports the ability to remove contacts from campaigns when a contact is removed from an active list in Hubspot.
r/hubspot·October 2024·2 points
In a thread where the original poster had checked four other cold email tools and found their two-way sync was one-way for removals. Read the enthusiasm as a vendor-adjacent reply, and read the capability as the thing that distinguishes a real two-way integration from a contact import.
Hubspot/Salesforce sequencer could be convenient, but you will probably run into deliverability issues as they don't do a lot in this area. When I used Hubspot for this in my previous job, I got many problems due to the fact that you can't set-up limits. My sales team was then sending more than 500 emails per day which was too much and blacklisted our domains.
r/sales·January 2025·1 points
Answering somebody asking whether to drop lemlist now that they have HubSpot, which is the real question behind this pair. One team's experience rather than a measurement, and it names a specific mechanism: no sending cap, so the cap became the domain reputation.
We had 13K+ contacts from Lemlist, Propensity, Zoom, LinkedIn CRM Sync, and a few internal tools all showing up the same way in every report. Impossible to measure ROI per channel.
r/hubspot·April 2026·5 points
The highest-scoring thread in the set, and a problem this pair contributes to rather than creates. The fix described is a workflow reading Record Source Detail 1, the field HubSpot populates with the integration name, into a custom property. Setting a default property value on records lemlist creates is the version of that fix you can configure inside this integration.
HubSpot wants you to use sequences for sales outreach. They monitor the usage of the marketing email usage and performance to avoid dragging down the performance from the shared email sending ips.
r/hubspot·July 2023·4 points
The oldest quote here and the one that explains the note behaviour better than any documentation does. HubSpot reserves its email engagement objects and its sending reputation for its own tools, and an integration that writes opens as notes is that policy showing up as an API rule.
The threads are two years older than the integration they describe, which is the useful thing about them. In 2024 people complained that the fields were not customisable, and the documentation now describes per-field direction, custom fields, mandatory properties and default values, so that complaint has been answered. What has not changed is the reason people run lemlist against HubSpot rather than using HubSpot sequences, and that comes up repeatedly: deliverability controls HubSpot does not offer. One thread is about a reporting problem this integration contributes to rather than causes.
Only the second and third quotes describe the integration in use, and the first is now out of date in a way worth saying out loud rather than quietly leaving out. The reporting thread is the one to read before promising a dashboard, because it is a HubSpot behaviour that no setting in lemlist changes.
The note behaviour is the whole story on this pair and it is worth being precise about whose limitation it is. HubSpot reserves its email engagement objects for its own tools and does not let third-party applications write opens and clicks to them, so lemlist stores them as notes because that is the only place available. Any sequencing tool integrating with HubSpot faces the same wall, so this is not a reason to pick a competitor; it is a reason to decide early where your engagement reporting lives. For most teams the honest answer is lemlist, with HubSpot holding the record and the timeline.
What lemlist does unusually well here is the configuration model. The integration is set up once at team level and applies to every campaign and user, with an exception for deal creation triggers, which are per campaign, and the option to disable the push to CRM on a specific campaign. Field mapping carries a direction per field, so you can hold a property as HubSpot-owned, lemlist-owned or genuinely shared without that being an all-or-nothing choice. That is more control than several far more expensive connectors in this directory offer.
The failure modes are all front-loaded, which is good news if you read them first. Properties have to exist before mapping, mapping has to happen before importing, every contact needs an email, a LinkedIn URL or a company domain to match on, and importing from HubSpot only pulls fields visible as columns in the list view you import from. Spend the first hour on that checklist rather than on campaign copy. Teams that do have very little to say about this integration afterwards, which is the highest compliment a pair on the engagement layer gets.
Reverse Contact resolves an email, a domain or a profile URL into a verified people and company record, through one API with a consistent schema. It sits under HubSpot, lemlist and everything else in this directory, and it returns null with a confidence score rather than a guess.
Free trial, no card required, and 500 credits to start.
Any of them. lemlist lists CRM integrations including HubSpot on every plan from Email upwards, so there is no upgrade to buy for the connector itself. What there is not is a free plan: lemlist offers a 14 day trial rather than a free tier, so the real cost is a lemlist subscription you were going to buy anyway. On the HubSpot side nothing is gated.
As notes, not as email engagement. lemlist documents the reason plainly: HubSpot does not allow third-party applications to write open and click data to its dedicated email objects. Sent and replied emails do become Email objects, and opens, clicks, bounces and failures become Notes. So a HubSpot report counting opens from its own email tool will not count lemlist opens, and that is a HubSpot restriction rather than a lemlist shortcut.
Two likely reasons, both documented. Custom properties have to already exist in HubSpot, because lemlist can only map to a field that is there. And field mapping is not retroactive, so anything you map after importing leads or launching a campaign does not backfill. Map first, then import, in that order.
Partly, and more than most tools manage. Messages sent and replied become HubSpot LinkedIn Message objects, because HubSpot has a dedicated one. Profile visits, invites sent, invites accepted, message opens and failed actions all become Notes. Calls placed through lemlist log as proper Call engagements with direction, duration, outcome and owner, provided the contact already exists in HubSpot.
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.