---
name: hubspot-lemlist-integration
description: Connect HubSpot and lemlist: what syncs, which editions carry it, the setup order, and the failures to expect. Covers contacts, companies, activities. Use when the user wants to set up, audit or troubleshoot HubSpot and lemlist together, or asks why data is not moving between them.
---

# HubSpot and lemlist

> Generated from https://www.reversecontact.com/integrations-hub/hubspot-integrations/hubspot-lemlist-integration
> Every tier requirement, sync direction and limit below was read from the vendors' own documentation on 2026-10-11.
> Vendors change these without notice. Re-check anything load-bearing before you rely on it.

**What you have to buy first:** A paid lemlist plan (there is no free tier), plus admin access on both sides

**What moves:** contacts, companies, activities, both ways.
**How it is built:** native, marketplace app. **Effort:** hours.

## The short version

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.

## When a call outcome maps and when it silently does not

Rows: The call status in lemlist. Columns: Your portal's call outcomes. 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.

| 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 |

- **maps correctly.** Only the top-left corner works without intervention. A rep marking No answer produces No answer in HubSpot, and the mapping can still be overridden status by status if you want different wording.
- **falls back to Connected.** A custom lemlist status has no default mapping. Recreated HubSpot outcomes carry different ids, so the default mapping points at something that no longer exists. Either way the call lands as Connected and nothing reports an error.

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.

## What actually syncs

Direction is written from HubSpot's point of view: out means out of HubSpot, in means into it.

| What | Direction | What that means in practice |
|---|---|---|
| Contacts and companies | Two-way sync | 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. |

## Which field lands where

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. |

### Which HubSpot object each kind of activity is allowed to become

| 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 |

**What does not cross:**

- Opens and clicks as engagement. They are notes, so a HubSpot report built on email engagement does not count them, and lemlist says plainly that this is HubSpot's restriction rather than theirs.
- A recording, transcript or summary on a call that came through Aircall or Ringover. Those four extras are for calls placed with lemlist calling only.
- An AI summary that does not already exist. lemlist pushes the summary if the call has one and syncing never triggers one to be generated.

## Connect it, in this order

**Who has to do it:** One person with admin on both sides. The integration is configured once at team level rather than per user, which is the nicest thing about it.
**How long:** An hour, and the order of it decides whether you do it twice.

### 1. Create the HubSpot properties before you open lemlist

*Where:* 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.

### 2. Decide whether lemlist may create records, and on what trigger

*Where:* 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.

### 3. Set the mandatory properties that gate creation

*Where:* 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.

### 4. Set default values for anything lemlist creates

*Where:* 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.

### 5. Map the fields, with a direction on each

*Where:* 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.

### 6. Map users, and set the fallback owner per direction

*Where:* 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.

### 7. Decide on call recordings before the first call

*Where:* 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.

### 8. Map every call status by hand if you invented any

*Where:* 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](layer:engage) as long as the order holds.

## How to check it worked

- Send one email to a test contact and look for it in the Email object. Then open one and look for the open in Notes. If you expected both in the same place, the reporting conversation has to happen now rather than after launch.
- Place one call and open the HubSpot note. Click the recording link in a private browser window with no lemlist session. If it plays, that is what anybody with the link can do, permanently.
- Mark a call with every status your team uses and read the HubSpot outcome on each. Any that says Connected when it should not is an unmapped status rather than a bad call.
- Open Logs for the last day and read the failures. It takes a date range and a refresh, and it is the only place the integration tells you it did not do something.

## When it goes wrong

Each row is a symptom somebody reports, the documented reason, and the fix. Work down it before escalating to either vendor, because most of these are configuration.

| Symptom | Why it happens | What to do |
|---|---|---|
| Every call shows as Connected whatever the rep marked | The 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. |
| Opens and clicks are nowhere in the Email object | HubSpot 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. |
| A field mapped last week is still empty on older contacts | Field 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. |
| A contact is not being created in HubSpot at all | Mandatory 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. |
| Activity is landing with the wrong owner | User 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. |
| A call has no transcript or summary on the HubSpot record | Neither 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. |
| Somebody edited a call note in HubSpot and it reverted | lemlist 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. |
| A manual unsubscribe never reached HubSpot | lemlist 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. |

## What breaks, from the vendors' own docs

- **Most activity is a note, by HubSpot's rule.** Only sent and replied emails become Email objects. Opens, clicks, bounces, failures, campaign state changes and most LinkedIn actions become Notes, because HubSpot does not allow third-party applications to write to its open and click objects. Notes are visible on the timeline and are not countable in the reports built on email engagement, which is the thing to check before promising anybody a dashboard.
- **Field mapping is not retroactive.** Fields mapped after you import leads or launch a campaign do not backfill, and custom properties have to exist in HubSpot before lemlist can map to them at all. The order is create the properties, map the fields, then import. Doing it the other way round means re-importing, which is the single most common support thread on this pair.
- **Manual unsubscribes do not reach the CRM.** lemlist only pushes an unsubscribe when the lead unsubscribes themselves from the campaign. Somebody moved into the Unsubscribe section by hand is not pushed to HubSpot. In a team that manages opt-outs manually, that is a compliance gap rather than an inconvenience, and it needs a process on the HubSpot side.
- **Custom call statuses fall back to Connected.** lemlist's built-in call statuses map to HubSpot's standard outcomes, so No answer stays No answer. A status your team invented has no default mapping and lands as Connected until somebody maps it by hand in the activities settings. The same happens if your portal's call outcomes were deleted and recreated, because the default mapping targets HubSpot's factory outcomes by id. Every call therefore looks successful until you notice.
- **The call recording link is public and permanent.** lemlist states it outright: anyone who opens the recording link from the HubSpot record can listen to the call with no lemlist account, and the link never expires and cannot be revoked. Calls recording is one of four toggles that are on by default. This is the one setting on the page to decide before go-live rather than after, because a link already written into a note cannot be withdrawn.
- **The call note is rebuilt rather than merged.** The activity is created when the call ends with whatever exists at that moment, rewritten when the transcript arrives and rewritten again when the AI summary is generated, always in the same order: the rep's note, the summary, the recording link, then the transcript. An edit made by hand in HubSpot is replaced on the next refresh, and the note caps at 65,000 characters with anything longer cut from the end, so a long transcript is what disappears.

## The APIs, if you are building around it instead

### HubSpot

- **Base:** `https://api.hubapi.com`
- **Auth:** `Authorization: Bearer <private-app-token>` for a private app, or OAuth for a marketplace app. Full CRM API access is on every tier including Free.

| Call | Request | What it does |
|---|---|---|
| `PATCH /crm/v3/objects/contacts/{contactId}` | `{ "properties": { "rc_title": "VP Sales" } }` | Update a contact. Send only the properties you own. |
| `POST /crm/v3/objects/contacts/search` | `{ "filterGroups": [...], "properties": [...] }` | Find records by property. Use this to pull the slice that is missing a field. |
| `POST /crm/v3/objects/contacts/batch/update` | `{ "inputs": [ { "id": "...", "properties": {...} } ] }` | Batch of up to 100. Prefer this over per-record PATCH at volume: it is one request against the rate limit. |

**Rules that will cost you time if you skip them:**

- **Rate limits.** A private app gets 190 requests per 10 seconds on Professional and Enterprise, 100 on Free and Starter. Daily caps are 250,000 / 625,000 / 1,000,000 calls **per account, shared across every app**. A public OAuth marketplace app is capped at 110 per 10 seconds per installing account.
- **Calling an external API from a workflow needs Data Hub Professional or Enterprise.** Both the webhook action and the custom code action live in that hub, not in Sales Hub. Check this before designing an in-HubSpot build.
- **Custom code actions get 20 seconds and 128 MB.** Combined length of all workflow secrets is capped at 1,000 characters. Secrets are read with `process.env.NAME`.
- **Workflows:** up to 50 simple on Starter, up to 300 fully customisable on Professional.
- **Never write to a property a human maintains.** Use prefixed properties (`rc_*`) and promote with a separate workflow only where the human field is empty.

**HubSpot custom code action (Node 20):**

```javascript
// Input field: email   Output fields: rc_status, rc_title, rc_company, rc_headcount
// Secret: RC_API_KEY
const axios = require('axios');

exports.main = async (event, callback) => {
  const email = event.inputFields['email'];
  const res = await axios.post(
    'https://api.reversecontact.com/v2/enrich/persons',
    { email },
    { headers: { Authorization: `Bearer ${process.env.RC_API_KEY}` } }
  );

  const person = res.data?.data?.person;
  const company = res.data?.data?.company;

  // null means "not found", not "try harder". Write nothing and flag it.
  if (!person) return callback({ outputFields: { rc_status: 'no_match' } });

  callback({ outputFields: {
    rc_status:    'matched',
    rc_title:     person.currentPosition?.title || '',
    rc_company:   company?.name || '',
    rc_headcount: company?.employeeCount || 0
  }});
};
```

Docs: https://developers.hubspot.com/docs/api/overview

## Filling the record this integration moves

The integration above moves a record between two systems. Neither of them creates what is in it, so a sync that works perfectly still carries whatever gaps the record arrived with. Reverse Contact resolves an email, a domain or a profile URL into a verified people and company record through one API, and returns null with a confidence score rather than a guess.

### Reverse Contact

- **Base:** `https://api.reversecontact.com/v2`
- **Auth:** `Authorization: Bearer rc_your_api_key`. Keys are created in Workspace > API Keys.

| Call | Request | What it does |
|---|---|---|
| `POST /v2/enrich/persons` | `{ "email": "j.okafor@northwind.io" }` | Resolve a person from an email, a name plus company, or a profile URL. Cached resolution, returns in the response. |
| `POST /v2/enrich/companies` | `{ "domain": "northwind.io" }` | Resolve a company from a domain or a name. |
| `POST /v2/fetch/persons` | `{ "linkedInUrl": "..." }` | Standard profile lookup from the database. |
| `POST /v2/fetch/persons/live` | `{ "linkedInUrl": "..." }` | Live on-demand resolution. ASYNCHRONOUS: returns a webhookId to poll, not a record. |
| `POST /v2/search/people` | `{ "filters": { "currentCompanyDomain": "northwind.io" } }` | Filtered people search. 1 credit a profile delivered, and /v2/search/people/count is free. It replaced /v2/search/persons, which returns 410 Gone since 13 October 2026. |
| `POST /v2/search/organizations` | `{ "filters": { "companyDomain": "northwind.io" } }` | Filtered company search. A domain can also go straight to a company through POST /v2/enrich/companies, or through the enrich_company MCP tool since November 2026. |
| `POST /v2/contact/email` | `{ "linkedInUrl": "..." }` | Find an email. ASYNCHRONOUS: returns a taskId to poll. 3 credits for a professional address, 5 for a personal one, 8 for both, refunded when neither is found. |
| `GET /v2/webhooks/:webhookId` | - | Poll an async job until status is "succeeded". Polling is free and does not count against the rate limit. |

Response shape:

```json
{
  "success": true,
  "data": {
    "person": {
      "fullName": "Jane Okafor",
      "headline": "VP Sales at Northwind",
      "location": "London, United Kingdom",
      "linkedInUrl": "https://linkedin.com/in/...",
      "currentPosition": { "title": "VP Sales", "companyName": "Northwind", "startDate": "2023-04" },
      "emails": [], "experience": [], "education": [], "skills": []
    },
    "company": { "name": "Northwind", "domain": "northwind.io",
                 "industry": "Software Development", "employeeCount": 220 }
  },
  "error": null,
  "metadata": { "requestId": "req_...", "executionTimeMs": 480, "updatedAt": "2026-09-01T..." },
  "quotas": { "creditsConsumed": 1, "workspace": { "credits": { "total": 10000, "used": 4521, "left": 5479 } } }
}
```

**Rules that will cost you time if you skip them:**

- A miss returns **null**, not a best guess. Every response carries a confidence score, and you can raise the precision threshold on the request. Branch on it: do not treat a low-confidence answer as a match.
- Use the cached endpoints anywhere that must answer inside one HTTP request. The `/live` endpoints return a task and need polling.
- `quotas.workspace.credits.left` is on every response. Log it, or you will find out about the balance from a 402.
- Credit costs per call are published and a dollar rate per lookup is not: 2 credits for a reverse lookup from an email, 1 for a cached profile lookup, 2 for a live refresh, 3 for a business email and 20 for a direct phone number, with the last two charged only when one is found. Checks and the search count endpoint are free. Credit packs expire after 3 months. Do not hard-code a dollar cost assumption.

**MCP server:** `https://api.reversecontact.com/mcp`

- Auth: OAuth 2.1 where the client supports it, otherwise `Authorization: Bearer rc_your_api_key`.
- Tools: `enrich_person`, `enrich_person_live`, `enrich_company`, `enrich_company_live`, `search_persons`, `search_companies`, `check_usage`, `check_task`
- Streamable HTTP, JSON-RPC 2.0. The `_live` tools return a task id that `check_task` polls.

Docs: https://docs.reversecontact.com/getting-started

## Sources

- lemlist help centre: configure the HubSpot integration: https://help.lemlist.com/en/articles/10308771-how-to-configure-the-hubspot-integration-in-lemlist
- lemlist help centre: map lemlist activities to HubSpot: https://help.lemlist.com/en/articles/8735296-map-lemlist-activities-to-hubspot
- lemlist: pricing: https://www.lemlist.com/pricing
- 14 practitioner threads read on 2026-10-11, summarised on the page: https://www.reversecontact.com/integrations-hub/hubspot-integrations/hubspot-lemlist-integration#reddit
- This pair, with the reasoning behind each step: https://www.reversecontact.com/integrations-hub/hubspot-integrations/hubspot-lemlist-integration

---

*Published by Reverse Contact, which appears in this directory as a data provider.
No other vendor pays for placement. Where a vendor publishes no public figure, this file says so
rather than estimating. Reverse Contact costs are stated in credits, which it publishes; no dollar
rate per lookup appears here, because none is published and dividing a pack price is not their number.*
