The cheapest way out of the Data Hub trap, and the trigger needs a public app.
An n8n instance and a HubSpot service key. The trigger needs a registered public app.
Contacts, Companies, Deals, Custom objects, two-way sync.
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.
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 | Both ways | Create or update, delete, get, get all, get recently created or updated, and search. |
| Companies and deals | Both ways | Full create, update, delete, search and recently-modified reads on both. |
| Custom objects | Both ways | Through the HTTP Request node on the same credential, which is how anything the node does not list gets done. |
| Engagements and tickets | Both ways | Engagements create, delete and read; tickets create, update, delete and read. |
| Form submissions | Both ways | 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. |
Five of those six rows move in both directions. The one that does not is Record changes out to n8n, and those are the rows that decide how you design around this rather than the ones in the brochure.
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. |
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 |
|---|---|
| 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 |
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, five action rows and three documented exclusions, each one's note, and the five 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 useful way to read those two tables together is as a division of labour: the trigger tells you that something changed and the node tells you what it now is. Neither carries the other's information, which is why almost every workflow on this pair starts with a trigger and immediately calls a get, and why it costs two calls against the allowance below rather than one.
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. Pick one on each side and the grid marks the answer.
Pick one on each side.
| 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 |
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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-n8n/SKILL.md https://www.reversecontact.com/integrations-hub/skills/hubspot-n8n.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.
WhyHubSpot 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.
WhyA 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.
WhyHubSpot 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.
WhyHubSpot'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.
WhyA 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.
WhyRate 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.
WhyHubSpot 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.
WhyThe 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.
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 2025 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.
Yes I am testing a workflow for a client on my self hosted N8N (on GCP) that gets triggered when a new contact is added to Hubspot CRM. Hubspot integration is not straight forward and it took a lot of trials to get it to work.
r/n8n·February 2025·2 points
Answering somebody stuck on exactly the trigger path, with free HubSpot and self-hosted n8n. The thread is useful because nobody in it finds a single misconfiguration: the answers are a valid certificate, a developer account, and trial and error, which matches a credential path with four values in it.
I COULD NOT get it to work with telegram and it ended up being that I needed an https url on my self hosted n8n instance. [...] I had everythjng setup correctly (so I thought) tread every single guide I could find and nothing fixed it until I tried the tunnel.
r/n8n·February 2025·2 points
Written about a different service and it transfers exactly, because the requirement is HubSpot reaching your instance rather than anything HubSpot-specific. The typos are in the original. A Cloudflare tunnel is the fix named, and it is cheaper than the two days of guide-reading it followed.
HubSpot's webhook only sends text fields, not file uploads - that's why your JSON is missing the image. If you need the file, you'll have to call HubSpot's API from n8n (via HTTP Request) to pull the file URL or upload it, and that does require a private app token.
r/n8n·September 2025·2 points
The most specific answer in the set, and it names the consequence rather than just the cause: a workflow that was going to be webhook-only now needs a token, which means the credential work you were trying to avoid.
With the hubspot MCP server in beta, the scopes are quite limited, and the n8n hubspot node also seems quite limited. My next step was to create a code tool for every single endpoint that I want to leverage, but this seems excessive.
r/n8n·May 2025·2 points
Seven resources and no custom objects is the documented scope of the node, and the HTTP Request node on the same credential is n8n's own answer. Building a code tool per endpoint is the more laborious version of the same idea, which is worth knowing before you start.
If you're serious about HubSpot automations, I'd narrow your focus to Workflows and Custom Code Actions first. Workflows are the backbone of almost everything in HubSpot automation, and custom code is what lets you go beyond the out-of-the-box limits
r/hubspot·January 2026·6 points
The highest-scoring comment in the set, and correct for anybody who owns Data Hub Professional. For anybody who does not, custom code actions are not available at all, which is the fact the comment does not mention and the whole reason this page exists.
Two kinds of thread, and they disagree productively. In r/n8n people are debugging a specific thing, and it is nearly always the webhook rather than the node: self-hosted instances that look right and receive nothing, payloads missing the file somebody uploaded, scopes that match the documentation and still fail. In r/hubspot the same question gets a different answer, which is to learn HubSpot workflows and custom code actions instead and stop bolting on tools. Both are right, and which one applies to you is decided by whether you own Data Hub.
Four of those five describe behaviour the vendors document, and the fifth is an argument rather than an observation. The disagreement between the two subreddits is the useful part: it is a licensing question dressed as a tooling preference, and the same split runs through every pair in the orchestration layer.
The reason this pair matters more than its search volume suggests is the Data Hub gate. HubSpot sells workflows in Sales Hub and sells the webhook and custom code actions that let a workflow call an external API in Data Hub, which is a separate purchase. A team on Sales Hub Professional therefore has automation and still cannot reach an outside service from it. That is the most expensive surprise in this directory, it is documented on the Reverse Contact guide in full, and n8n is the cheapest documented way around it.
What you are buying instead is a host and a maintainer. Self-hosted n8n costs the instance and nothing per execution, which inverts the economics of a per-task tool once you are running real volume, and it gives you version control over the logic rather than a diagram in somebody's account. Against that, HubSpot has to be able to reach your n8n for webhooks to fire, so this is a server with a public endpoint rather than something on a laptop, and the person who built it has to still work here in a year.
The pattern worth copying is the one in the CRM data layer: let HubSpot own the record, let n8n own the decisions that HubSpot cannot make, and keep every enriched value in its own property so a workflow decides what gets promoted into the fields reps trust. That discipline is what separates the builds that survive a year from the ones that quietly start disagreeing with the CRM in month three.
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, n8n 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.
No. Full CRM API access is on every HubSpot tier including the free one, so an n8n workflow can read and write your records whatever you pay HubSpot. That is the reverse of calling an outside API from inside a HubSpot workflow, which needs Data Hub Professional, and it is exactly why n8n is the usual answer for teams that do not own that hub.
Three ways, and which one depends on the node. n8n recommends a service key, entered in the App Token field, for the HubSpot node, and creating one needs super admin or developer tools access. The HubSpot Trigger node is different: it is documented with the developer API key method, which means registering a public app with a client ID, client secret, app ID and developer API key. The old API key method is deprecated by HubSpot and should be migrated.
Yes, through the HubSpot Trigger node, which uses HubSpot's webhooks API. The cost is that webhooks belong to a public app, so you register one in a HubSpot developer account even if the workflow is only ever for you. That is an afternoon the first time and nothing afterwards, and it is the part most people do not expect when they picture a trigger node.
When nobody will own it. A self-hosted instance is a server with credentials on it, and the workflow that nobody maintained is the most common failure in this layer. If the logic is three steps and the volume is low, a per-task tool is less to look after. The crossover is volume and conditionality: n8n wins once you are running thousands of executions or branching on things a connector cannot see.
The node carries seven resources, contacts, contact lists, companies, deals, engagements, forms and tickets, and no custom objects. The engagement resource has no update operation, so changing one means deleting and recreating it. On the trigger side, HubSpot allows one webhook per app, so activating a second trigger stops the first one working. For everything outside that list, n8n's own documentation points at the HTTP Request node on the same credential, which reaches any HubSpot endpoint and costs nothing extra to authenticate.
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.