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

# HubSpot and Smartlead

> Generated from https://www.reversecontact.com/integrations-hub/hubspot-integrations/hubspot-smartlead-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 Smartlead plan and a HubSpot account that can authorise OAuth. A campaign not yet live for the native sync, or SmartAgents access for the other route.

**What moves:** contacts, activities, one way, into HubSpot.
**How it is built:** native, built on the api. **Effort:** hours.

## The short version

The narrowest CRM integration on the HubSpot hub, and the one with the sharpest timing constraint. HubSpot is connected inside the campaign creation flow, after the leads are uploaded, and Smartlead documents that it cannot be added to a campaign that is already running. Every campaign needs it enabling again, with the list, the group and the field mapping chosen each time, and the actual on switch is a toggle that reads like a deduplication setting. Get those three things right and it does what you want; miss any of them and the campaign runs perfectly while the CRM learns nothing.

## What each of the two routes will actually do

Rows: What you need it to do. Columns: The route you take. Neither side gates this by edition: any Smartlead plan and any HubSpot account that can authorise OAuth. The choice that matters is which of the two integrations you use, and they are not equivalent.

| What you need it to do | The campaign-level sync | A SmartAgent |
|---|---|---|
| Push leads from a brand new campaign | Works | Works |
| Add syncing to a campaign already running | Not possible | Works |
| Update an existing HubSpot contact rather than duplicate it | Not possible | Works |
| React in real time to a reply | Not possible | Works |

- **Works.** The native sync is a toggle in the campaign creation flow where you also choose the HubSpot list and group. A SmartAgent is a workflow with a schedule or an event trigger, built from a template or a prompt, which Smartlead documents as doing search, create and update by email.
- **Not possible.** Smartlead states the campaign-level integration cannot be added midway through an active campaign and must be enabled for each new campaign separately. It has no documented upsert and no event trigger.

Counted off that grid, of eight pairings: five give you works, three give you not possible.

One column works in every row and the other works in one, which makes this the least balanced grid in the directory and the most useful thing on the page. The native sync is not wrong, it is just narrower than most people need, and the three rows it cannot do are the three everybody asks for.

## 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 |
|---|---|---|
| New leads | One way, in | Created in HubSpot when they do not already exist, into the list and group chosen during campaign setup, across the fields you mapped. |
| Field mapping | One way, in | Set per campaign in the import step. All the fields in the HubSpot column have to be mapped before the sync is confirmed. |
| Replies, bounces and unsubscribes | One way, in | Through webhooks rather than the campaign sync, posted to an endpoint you control and scoped by user, client or campaign. |
| An existing HubSpot contact | Events only | The documented behaviour covers creating leads that do not exist. How existing contacts are treated is not stated, so verify it on a test campaign. |
| Anything out of HubSpot | One way, out | Nothing on this path. Smartlead is fed from its own lead import, not from a HubSpot list. |

## Which field lands where

Four contact fields cross, and which route you took decides when they cross and what happens to a contact that already exists. The field list is the same either way; the behaviour around it is not.

| In HubSpot | In Smartlead | What to know about the match |
|---|---|---|
| Email address | The HubSpot contact email | The match key for the SmartAgents upsert, and the field a lead must have for the agent to do anything. A lead without one is the first thing to check in the run logs. |
| First name, last name | The HubSpot contact name | Synced only when present on the Smartlead lead record. |
| Company name | The HubSpot company field | The fourth and last field. Anything richer than these four has to reach HubSpot from somewhere else. |
| An empty Smartlead field | Leaves HubSpot alone | Smartlead states empty fields will not overwrite existing values, which is the safe default and worth knowing before anybody worries about a thin lead record. |
| A HubSpot list and group | Chosen at campaign creation | On the native route you select both, and they decide where a lead is pushed when it does not already exist in HubSpot. |
| Lead sync status | Updated back in Smartlead | A step in the Scheduled CRM Sync template, and what lets it process only unsynced leads on the next run rather than everything again. |
| A Slack summary | The configured channel | The last node in both templates. Optional in principle and required in practice, because the agent will not deploy until the app is in the channel. |
| Replies, opens, clicks, unsubscribes | Webhooks, not this integration | Smartlead publishes email_sent, email_reply, email_open, email_link_click, lead_unsubscribed and lead_category_updated as webhook events for a server to consume. |

### What the two routes can and cannot do

| The action | How it reads on the record |
|---|---|
| Add it to a campaign that is already running | Native: no. SmartAgents: yes |
| Work across every campaign at once | Native: no, it is per campaign every time. SmartAgents: yes, with account-level scope |
| Update an existing HubSpot contact rather than duplicating it | SmartAgents, through the documented upsert logic |
| Trigger in real time on a reply | SmartAgents, with an event-based trigger |
| Change the trigger afterwards | Not for an event-based agent. Smartlead says build a new one |
| Run without touching Slack | Native: yes. SmartAgents: only if you remove the Slack node from the workflow |

**What does not cross:**

- Anything beyond email, first name, last name and company name. That is the documented sync list for the SmartAgents route and nothing suggests the native one is wider.
- Retrospective enablement on the native route. Smartlead states it can only be integrated while creating the campaign and not midway through an active one.
- An edit to an event-based SmartAgents trigger. Smartlead states it cannot be changed after the agent is created, so the agent has to be rebuilt.

## Connect it, in this order

**Who has to do it:** Somebody in Smartlead, plus a HubSpot account with permission to authorise OAuth integrations. No HubSpot admin, and no developer anything.
**How long:** Ten minutes either way. The decision about which route to take is the part worth thinking about.

### 1. Decide which of the two routes you are taking

*Where:* Design, before either settings screen

There are two and they behave differently. The campaign-level sync is a toggle inside the campaign creation flow and cannot be added later. SmartAgents is an agent you build, triggered on a schedule or a campaign event, and it works against campaigns that already exist.

### 2. For the native route, connect HubSpot to Smartlead first

*Where:* Smartlead: the CRM connection

Smartlead is explicit that connecting a HubSpot CRM does not automatically sync with all campaigns in the account. The connection is the prerequisite and enables nothing on its own.

### 3. Enable it inside the campaign creation flow, every time

*Where:* Smartlead: creating a campaign

Toggle the HubSpot connection on while the campaign is being created, then select the HubSpot list and the HubSpot group that leads should be pushed to when they do not already exist. Smartlead states this cannot be integrated midway through an active campaign.

### 4. For the SmartAgents route, connect from Integrations

*Where:* Smartlead: SmartAgents, Integrations

Find HubSpot, click Connect, authorise on HubSpot's OAuth page and confirm the status shows Connected. Smartlead notes tool connections are one-time and need no reconnecting unless you disconnect manually.

### 5. Start from a template rather than a blank prompt

*Where:* Smartlead: SmartAgents, Home

Two exist. Scheduled CRM Sync pushes leads who replied, runs daily at 9am, processes only unsynced leads and reports to Slack. Inbox Reply Sync with Upsert syncs interested leads and prevents duplicates with upsert logic.

### 6. Choose the trigger carefully, because it is permanent

*Where:* SmartAgents: trigger configuration

Schedule-based takes a time, timezone, frequency and a skip-weekends toggle. Event-based takes a scope of account, client or campaign level and an event such as email reply or lead category update. Smartlead states event-based triggers cannot be edited after the agent is created.

### 7. Add the SmartAgents app to the Slack channel if the workflow uses one

*Where:* Slack

Both templates end in a Slack summary, and Smartlead states the agent cannot be deployed until the SmartAgents app is in the target channel. A Configuration Required notice that will not clear is usually this.

### 8. Test run before deploying, and read every step

*Where:* SmartAgents: the workflow canvas

Click Test Run and confirm the HubSpot Upsert Contact step returns what you expect on both the create and the update path. If it is wrong you give feedback in the prompt field and the simulation reruns.

The two routes answer different questions, and the page is worth reading as a choice rather than a sequence. The native sync is a setting you must remember at the right moment; SmartAgents is a workflow you build once and point at campaigns that already exist, which is what makes it the answer to the limitation that defines this pair.

## How to check it worked

- On the native route, try to enable HubSpot on a campaign that is already running. You cannot, and confirming it once is how a team learns to do it at creation time.
- On the SmartAgents route, run the test and watch both paths: a lead that exists in HubSpot and one that does not. Upsert is only proven when you have seen it update as well as create.
- Push a lead with an empty company name and check what HubSpot holds afterwards. Smartlead states empty fields in Smartlead will not overwrite existing values in HubSpot.
- Check the run logs after the first scheduled execution. It is the only place that distinguishes an agent that ran and found nothing from an agent that did not run.

## 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 |
|---|---|---|
| A campaign is running and HubSpot cannot be switched on | Smartlead states the campaign-level integration can only be set up while creating the campaign and not midway through an active one. | Either recreate the campaign, or build a SmartAgent instead, which works against campaigns that already exist. The second is almost always the better answer. |
| The CRM is connected and no campaign is syncing | Connecting HubSpot to the Smartlead account does not sync it with any campaign. It has to be enabled per campaign, every time. | Enable the toggle in each new campaign's creation flow, and select the HubSpot list and group while you are there. |
| HubSpot shows as disconnected after authorising | Smartlead lists this as its first troubleshooting case: the OAuth account may lack the necessary CRM permissions. | Re-authorise from SmartAgents, Integrations, with an account that has CRM permissions. Tool connections are one-time otherwise and do not need periodic reconnection. |
| The Configuration Required notice will not clear | Slack is the usual culprit. The SmartAgents app has to be present in the target channel before the agent can be deployed. | Add the app to the channel using the in-app link, then return to the workflow. Connecting Slack as an integration is not the same as adding it to the channel. |
| The agent ran and the contact is not in HubSpot | Three documented causes: check the run logs for that execution, confirm the lead has a valid email address, and confirm the HubSpot OAuth connection is still active. | Work through all three in that order. The email is the match key for the upsert, so a lead without one cannot produce a contact. |
| The agent runs but contacts are never updated | The Upsert Contact step is not receiving the right lead data, or the connection logic between the fetch step and the HubSpot step is wrong. | Open the connector between the two steps, choose Edit Connection Logic, and check what is being passed. Reset to Default is there if you changed it and want it back. |
| The trigger is wrong and cannot be changed | Smartlead states that event-based triggers cannot be edited after the agent is created. | Create a new agent. This is the one irreversible decision in the SmartAgents flow, so it is worth being deliberate about scope and event type before clicking Proceed. |
| Nothing about replies or opens is reaching anywhere | Those are webhook events rather than part of this integration: email_sent, email_reply, email_open, email_link_click, lead_unsubscribed and lead_category_updated. | Point them at a server. Smartlead retries failed deliveries, marks an event failed after three attempts, and exposes a Retrigger Webhooks endpoint for the failures. |

## What breaks, from the vendors' own docs

- **The window is the campaign creation flow.** HubSpot can only be connected while a campaign is being created, in the pop-up after the lead upload. Smartlead states it cannot be integrated into an active campaign. There is no retrofit, so the cost of forgetting is rebuilding the campaign, and the only way to check is the HubSpot integrated column in the import leads section.
- **Per campaign, every time.** The connection does not carry to new campaigns. Each one needs the toggle, the HubSpot list, the HubSpot group and the full field mapping again. That is a process problem rather than a technical one and it is the usual reason a team's CRM has data from three campaigns and not from the other nine.
- **The on switch is disguised as a dedupe option.** Data syncs only if the create-the-lead-if-they-do-not-exist toggle is on. Nothing about the label suggests it governs whether anything syncs at all, so it is routinely left off by somebody being careful about duplicates, and the campaign then runs with an integration that is connected and silent.
- **The scope of the sync is not well documented.** Smartlead's marketing describes leads, deals, updates and activities, while its SmartAgents guide lists four contact fields and its campaign article does not enumerate them. Do not plan reporting on the marketing description. Run a test campaign with two leads, look at what reaches HubSpot, and design from that.

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

### Smartlead

- **Base:** `https://server.smartlead.ai/api/v1`
- **Auth:** API key as a query parameter.

| Call | Request | What it does |
|---|---|---|
| `POST /campaigns/{id}/leads` | `{ "lead_list": [ { "email": "...", "custom_fields": {...} } ] }` | Push the survivors of your suppression rules into a campaign. |

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

- Webhooks fire on every send, reply, bounce and unsubscribe. Route replies to a human within minutes; send the rest to a report.
- Entry pricing comes off a plan slider. Confirm the tier against your own mailbox count rather than budgeting from the headline.

Docs: https://api.smartlead.ai/reference

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

- Smartlead help centre: how to sync leads with HubSpot: https://helpcenter.smartlead.ai/en/articles/225-how-to-sync-leads-with-hubspot
- Smartlead API: webhook integration guide: https://api.smartlead.ai/guides/webhook-integration
- Smartlead help centre: Smartlead and HubSpot integration guide: https://helpcenter.smartlead.ai/en/articles/445-smartlead-x-hubspot-integration-guide-smartagents
- 14 practitioner threads read on 2026-10-11, summarised on the page: https://www.reversecontact.com/integrations-hub/hubspot-integrations/hubspot-smartlead-integration#reddit
- This pair, with the reasoning behind each step: https://www.reversecontact.com/integrations-hub/hubspot-integrations/hubspot-smartlead-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.*
