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

# HubSpot and n8n

> Generated from https://www.reversecontact.com/integrations-hub/hubspot-integrations/hubspot-n8n-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:** An n8n instance and a HubSpot service key. The trigger needs a registered public app.

**What moves:** contacts, companies, deals, custom objects, both ways.
**How it is built:** zapier, make or n8n, built on the api. **Effort:** hours.

## The short version

HubSpot gives away the API and charges for calling out of it, which is the single fact that shapes this pair. Workflows that reach an external service need Data Hub Professional, and n8n sits on the other side of that wall: it reads and writes a free HubSpot CRM perfectly well, so the automation that HubSpot would gate behind a hub upgrade becomes an instance you already run. The surprise is on the trigger rather than the actions. Writing to HubSpot needs a service key; reacting to a HubSpot change needs the trigger node, and that means registering a public app in a developer account even for a workflow only you will use.

## What your HubSpot tier allows an n8n workflow

Rows: HubSpot product tier. Columns: What a privately distributed app gets. Nothing about the n8n side is gated: the node, the trigger and the HTTP Request node are all in the free, self-hosted build. What is metered is HubSpot's API, and the two numbers behave differently, which is the thing to understand before a backfill.

| HubSpot product tier | Per 10 seconds, per app | Per day, per account | Per day, with limit increases |
|---|---|---|---|
| Free or Starter | 100 calls | 250,000 calls | plus 1,000,000, twice at most |
| Professional | 190 calls | 625,000 calls | plus 1,000,000, twice at most |
| Enterprise | 190 calls | 1,000,000 calls | plus 1,000,000, twice at most |

- **100 calls.** The burst limit applies individually per app, so an n8n service key has its own 100 and does not share it with your native connectors. This is the one number on the grid that is yours alone.
- **250,000 calls.** The daily limit is shared across every app in the account. A row-by-row n8n backfill spends from the same pool as every marketplace integration you have installed, and the symptom of exhausting it is somebody else's connector returning 429.
- **plus 1,000,000, twice at most.** The API Limit Increase add-on raises the burst to 250 per app and adds 1,000,000 a day on top of the base subscription, and HubSpot allows a maximum of two of them. It is sold on every tier, which is why this column reads the same all the way down.

Counted off that grid, of nine pairings: one gives you 100 calls, two give you 190 calls, one gives you 250,000 calls, one gives you 625,000 calls, one gives you 1,000,000 calls, three give you plus 1,000,000, twice at most.

The two columns tell opposite stories and both matter. A single n8n workflow is almost never the thing that hits the burst limit, because that number is its own; a backfill is very often the thing that empties the daily one, because that number is everybody's. Batch the reads and cache what you can, which is HubSpot's own first piece of advice on the subject.

## 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 | Two-way sync | Create or update, delete, get, get all, get recently created or updated, and search. |
| Companies and deals | Two-way sync | Full create, update, delete, search and recently-modified reads on both. |
| Custom objects | Two-way sync | Through the HTTP Request node on the same credential, which is how anything the node does not list gets done. |
| Engagements and tickets | Two-way sync | Engagements create, delete and read; tickets create, update, delete and read. |
| Form submissions | Two-way sync | Read all fields from a form, and submit data to one. |
| Record changes out to n8n | One way, out | The HubSpot Trigger node on HubSpot's webhooks API, which requires a registered public app and the developer API key. |

## Which field lands where

There is no field mapping on this pair, because n8n is not a sync. What there is instead is a list of resources the node covers and a boundary where you fall through to raw HTTP, and knowing where that boundary sits is most of what makes a workflow here predictable.

| In HubSpot | In n8n | What to know about the match |
|---|---|---|
| Contact | Create or update, delete, get, get all, get recent, search | Create and update are one operation, so the node will not tell you which of the two it did. If that matters, search first and branch. |
| Contact list | Add contact to a list, remove a contact from a list | Static lists only in practice, because an active list's membership is computed from its filters rather than written. |
| Company | Create, delete, get, get all, get recent created, get recent modified, search by domain, update | Search is by domain specifically rather than a general property search, which is a narrower operation than the contact one of the same name. |
| Deal | Create, delete, get, get all, get recent created, get recent modified, search, update | The most complete resource on the node. Pipelines and stages are properties here rather than their own operations. |
| Engagement | Create, delete, get, get all | No update. An engagement that needs changing is deleted and recreated, which changes its ID and anything pointing at it. |
| Form | Get all fields from a form, submit data to a form | Submitting to a form is a useful way into HubSpot's own automation, because a form submission can start a HubSpot workflow that an API write does not. |
| Ticket | Create, delete, get, get all, update | The only Service Hub object on the node, and the reason some teams run this pair without a sales use case at all. |
| Custom objects and everything else | HTTP Request node, same credential | n8n's own answer when an operation is not supported. It costs the convenience of the node and nothing else, because the authentication is already in place. |

### What the HubSpot Trigger node will tell you about

| The action | How it reads on the record |
|---|---|
| Company | Created, deleted, property changed |
| Contact | Created, deleted, privacy deleted, property changed |
| Conversation | Created, deleted, new message, privacy deletion, property changed |
| Deal | Created, deleted, property changed |
| Ticket | Created, deleted, property changed |

**What does not cross:**

- A file uploaded through a HubSpot form. HubSpot's webhook sends text fields, so the file has to be fetched with a separate API call from n8n rather than read out of the payload.
- A second simultaneous trigger. HubSpot allows one webhook per app, and activating another one silently stops the first.
- Anything from a HubSpot workflow reaching out to n8n without Data Hub. The webhook action in a HubSpot workflow needs Data Hub Professional, which is the gate this whole pair exists to route around.

## Connect it, in this order

**Who has to do it:** A HubSpot super admin, or a user with Developer tools access, plus whoever owns the n8n instance.
**How long:** Twenty minutes for the node. An afternoon the first time you need the trigger.

### 1. Decide first whether you need the trigger at all

*Where:* Design, before any settings page

The HubSpot node needs one service key. The HubSpot Trigger node needs a registered public app with four separate values. If a HubSpot form or a schedule can start the workflow instead, you have just saved the longest step on this page.

### 2. Create a service key for the HubSpot node

*Where:* HubSpot: Development, Keys, Service Keys

Also reachable through Settings, Account Management, Integrations, Service Keys. Name it, pick the scopes, confirm with Update, then Create. Open the key's detail page, click Show, and paste the value into the App Token field in n8n rather than into a field called service key.

### 3. Register a public app if the trigger is in the design

*Where:* HubSpot developer account: Apps

Get the developer API key from Apps, then Create app. The Auth tab carries the App ID, Client ID and Client Secret, all three of which n8n asks for. Paste n8n's OAuth Redirect URL into the app as its Redirect URL before you click Create app.

### 4. Give the app the scopes the trigger needs

*Where:* HubSpot: the app's Auth tab, Scopes

n8n publishes a recommended starting set rather than a minimum, and the oauth scope is on it alongside the CRM object scopes. A scope added after the app is created needs the connection re-authorised, so overshoot slightly rather than iterating.

### 5. Make the n8n instance reachable over valid HTTPS

*Where:* Your host

HubSpot has to reach n8n for a webhook to fire, so a self-hosted instance needs a public endpoint and a certificate that validates. Practitioners on r/n8n report a Cloudflare tunnel as the fix when a self-hosted instance looked correctly configured and simply never received anything.

### 6. Activate one trigger, and only one

*Where:* n8n: the HubSpot Trigger node

HubSpot allows one webhook, so n8n registers one when the trigger is activated. Activating a second trigger stops the first one working. Fan out inside a single workflow instead of running two trigger nodes.

### 7. Use the HTTP Request node for anything the node does not list

*Where:* n8n: HTTP Request

The HubSpot node covers contacts, contact lists, companies, deals, engagements, forms and tickets. Custom objects, file uploads and newer endpoints are not on that list, and n8n's own documentation points at the HTTP Request node on the same credential for them.

### 8. Watch the account-wide daily limit, not your own workflow

*Where:* HubSpot: Development, Monitoring, API call usage

The burst limit is per app and the daily limit is shared across every app in the account. The page lists usage for apps you built and third-party apps you installed, which is the only place the competition between them is visible.

Two of those eight steps exist only because of the trigger, and skipping it is a legitimate design decision rather than a compromise. The rest is one key and a host somebody owns, which is why this is the usual route out of the Data Hub gate described on the [HubSpot and Reverse Contact guide](pair:hubspot+reverse-contact).

## How to check it worked

- Run the HubSpot node once against a single contact before building anything. A wrong scope fails here in a way that is readable, and fails inside a long workflow in a way that is not.
- Activate the trigger, change a record, and watch for the execution. Then deactivate it, activate a second trigger, and confirm the first one has stopped: that is the documented single-webhook behaviour and it is better to see it than to meet it.
- Check the API call usage page after a full run and compare it against your daily allowance. If an n8n backfill consumed most of it, the thing that breaks next is another integration rather than this one.
- If you built a public app, re-authorise the credential after adding any scope. A scope that is present in the app and absent from the connection fails with a permissions error that names the endpoint rather than the scope.

## 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 |
|---|---|---|
| The first trigger stopped firing when a second one was activated | HubSpot allows one webhook. n8n registers it on activation, and activating another trigger takes the registration with it. | Run one trigger node and branch inside the workflow. If two workflows genuinely need the same event, have the first one call the second. |
| Authentication credentials not found. This API supports OAuth 2.0 authentication | A developer API key was used against a test account. HubSpot documents that developer API keys do not work for test accounts. | Use OAuth or a private app token for anything pointed at a test account. This is also worth knowing before you build the whole workflow against a sandbox. |
| A self-hosted instance never receives the webhook | HubSpot has to reach n8n over a valid HTTPS endpoint. An instance behind a self-signed certificate or no public address looks correctly configured from inside n8n and receives nothing. | Put it behind a real certificate. Practitioners on r/n8n report a Cloudflare tunnel fixing exactly this after every guide had been followed. |
| A form submission arrived without the file somebody uploaded | HubSpot's webhook sends text fields. The file is not in the payload and never was. | Call HubSpot's API from n8n with the HTTP Request node to fetch the file URL. That call needs a token, so the webhook alone will not do it. |
| OUTPUT_VALUES_TOO_LARGE from a HubSpot custom code action | A string data output exceeded 65,000 characters. This is the HubSpot side of the pair rather than the n8n side, and it is the usual reason a working action starts failing on one record. | Truncate or split the output. Remember the harder ceilings on the same action: 20 seconds of runtime, 128 MB of memory, and a maximum of 50 properties passed in. |
| This action has been paused to stay within the configured rate limit | Rate limiting was turned on for a HubSpot custom code action. It is off by default, and when on it also delays every action after it in the workflow. | Read the workflow action log, which names the resume time. If the limit is not what you wanted, it is configured per action under Configure rate limit rather than globally. |
| A retry never happens after a 429 | HubSpot only retries a custom code action if the error is thrown. Catching it quietly means HubSpot treats the execution as a success. | Throw the error in the catch block in Node.js, or raise it in the except block in Python. Swallowing it is the behaviour that turns a transient limit into missing data. |
| The node does not have the operation the workflow needs | The HubSpot node covers seven resources and no custom objects. That is the documented scope of it rather than a gap to work around. | Use the HTTP Request node on the same credential, which is n8n's own recommendation. Everything HubSpot exposes is reachable that way, and the authentication is already configured. |

## What breaks, from the vendors' own docs

- **The trigger is a different credential from the node.** n8n documents the service key, entered as App Token, as the recommended method for the HubSpot node, and the developer API key for the HubSpot Trigger. The trigger method needs a public app with a client ID, client secret, app ID and developer API key, registered in a HubSpot developer account. Teams who expected to paste one token and start listening lose an afternoon here.
- **Service keys are in public beta.** n8n notes that service keys are in public beta and may change, that private apps created in the UI are now legacy, and that HubSpot has deprecated the plain API key with a migration guide. Three auth methods in flight at once is a reason to write down which one each workflow uses, because the one that breaks will be the one nobody documented.
- **The daily API cap is shared across every app.** HubSpot allows 190 requests per 10 seconds per app and a daily cap shared across the whole account: 625,000 on Professional and 1,000,000 on Enterprise. An n8n workflow that loops row by row competes with your native connectors for the same allowance, and the symptom of exhausting it is somebody else's integration returning 429.
- **Somebody has to own the instance.** This is not a documented limit and it is the one that actually ends these projects. A self-hosted instance carries credentials, upgrades and uptime. n8n must also be reachable by HubSpot for webhook triggers to fire at all, which rules out a laptop and means a real host. Decide who owns it before you build on it.

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

### n8n

- **Base:** `Self-hosted or n8n Cloud`
- **Auth:** Credentials are stored in n8n, not in the workflow JSON, so the workflow stays safe to export and review.

| Call | Request | What it does |
|---|---|---|
| `NODE HTTP Request` | `Authentication: Generic > Header Auth. Name: Authorization. Value: Bearer rc_your_api_key` | There is no dedicated Reverse Contact node and you do not need one. Five minutes to configure, and no node update can break it. |
| `NODE HubSpot Trigger` | - | Authenticates with a **developer API key from a HubSpot developer account**, not a private app token, because that is how HubSpot exposes the webhooks API. Free to create, and nobody expects it. |
| `NODE Wait + IF` | - | The polling loop for Reverse Contact's /live endpoints: Wait 5s, GET the webhook id, IF status != succeeded loop back. |

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

- HubSpot allows **one webhook URL per app**. Route several object types through one subscription and branch inside n8n with a Switch node.
- Self-hosting is usually the reason this route was chosen: records never leave infrastructure you control. Do not quietly move it to a third-party cloud.
- n8n must be reachable by HubSpot for webhook triggers to fire.

Docs: https://docs.n8n.io/integrations/builtin/core-nodes/n8n-nodes-base.httprequest

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

- n8n docs: HubSpot node: https://docs.n8n.io/integrations/builtin/app-nodes/n8n-nodes-base.hubspot
- n8n docs: HubSpot credentials: https://docs.n8n.io/integrations/builtin/credentials/hubspot
- n8n docs: HubSpot Trigger node: https://docs.n8n.io/integrations/builtin/trigger-nodes/n8n-nodes-base.hubspottrigger
- HubSpot developers: API usage guidelines and limits: https://developers.hubspot.com/docs/developer-tooling/platform/usage-guidelines
- HubSpot developers: custom code workflow actions: https://developers.hubspot.com/docs/api-reference/legacy/automation/workflow-actions/custom-code-actions
- 14 practitioner threads read on 2026-10-11, summarised on the page: https://www.reversecontact.com/integrations-hub/hubspot-integrations/hubspot-n8n-integration#reddit
- This pair, with the reasoning behind each step: https://www.reversecontact.com/integrations-hub/hubspot-integrations/hubspot-n8n-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.*
