What is an n8n HubSpot integration?
An n8n HubSpot integration connects your HubSpot portal to n8n, a source available workflow automation platform, through a private app token and webhook subscriptions. Once connected, n8n workflows react to CRM events within seconds and write results back through the HubSpot API, which unlocks automation HubSpot's native workflow builder cannot express.
The integration itself is the foundation everything else stands on, and it is where most attempts quietly go wrong: the wrong auth method, polling instead of webhooks, or a connection that works in a test and misbehaves with real traffic. This guide does one thing: gets you from nothing to a connection you have proven end to end.
Four Steps to a Verified Connection
In HubSpot: Settings, then Integrations, then Private Apps, then Create. Name it after what it does, not just "n8n", so the audit log stays readable. Grant only the scopes you need to start: crm.objects.contacts read and write covers most lead flow work. You can add deals, timeline, or forms scopes later without recreating the app. Copy the access token immediately and store it in a password manager; HubSpot shows it exactly once.
In n8n: Credentials, then Add credential, then HubSpot App Token, and paste the token. Every HubSpot node and every direct HTTP request to api.hubapi.com in your workflows authenticates through this one credential, so a token rotation later is a single field change instead of a hunt through every workflow.
Webhooks are what make the integration react in seconds instead of minutes. Add a Webhook node to an n8n workflow and copy its PRODUCTION URL, not the test URL; the test URL only listens while the editor is open, and pointing HubSpot at it is the classic silent failure. Then in your private app's Webhooks tab, set that URL as the target and subscribe to the events you care about, such as contact.creation. Save, and HubSpot now pushes events the moment they happen.
Prove the round trip before you build anything on top. Submit a real form on your site, watch the execution appear in n8n, and have the workflow write something harmless back, like a note on the contact. When you can see the note on the HubSpot timeline, the loop is closed: events flow in, writes flow back, and you know it works with real traffic, not just the editor's test button. The free starter workflow below does this entire step for you.
What HubSpot pushes to n8n on a new contact. Note changeSource: a CSV import fires this exact same event for every row, so anything you build on this trigger must check it before acting.
What You Need Before You Start
The Round Trip, as an Importable Template
Five nodes that verify your integration end to end: catch the webhook, drop imports, fetch the contact through the v3 API, and write a proof note back to its timeline. The guards from the traps below are already built in, which is exactly what makes it a better starting point than an empty canvas.
The exact canvas you import: three labeled stages from webhook to verified write back.
Get the Connection Starter, Free
The workflow above as an importable n8n template: import, connect one credential, subscribe the webhook, and see the proof note land on a contact. Runs on any n8n instance, including the free self hosted version. Tell us where to send it and the file is in your inbox in a minute.
Free template, delivered by email · import in one click
Three Traps That Survive the Tutorial
The connection takes half an hour. These are the failures that show up later, with real traffic, and every one of them cost us something in production before it earned a guard in our workflows.
The v1 conversion loop. The n8n HubSpot node's contact upsert runs on HubSpot's legacy v1 API, and that call registers as a form conversion. The conversion recalculates properties, which can re trigger the very webhook that started your workflow. Write contacts through the v3 batch endpoint with an HTTP node instead.
The import stampede. A CSV import fires contact.creation for every row. An unguarded workflow treats 500 imported rows as 500 new leads. Check changeSource before acting.
The test URL that stops listening. n8n's test webhook URL only works while the editor is open. Subscribe HubSpot to the production URL and activate the workflow, or events silently vanish.
The connection itself is genuinely self serve; this page is enough. What comes after is where teams stall: designing the workflows that run on top, lifecycle rules, deliverability, rate limits, and the CRM hygiene that decides whether automation helps or embarrasses you.
If you would rather have the whole system built, builds run $5,000 to $15,000 fixed price, live in 2 to 4 weeks, scoped after the free audit: a 10 to 15 minute video showing where your leads leak. Five per month.
Connected? Build Something Real on It
Both of these playbooks run on exactly the connection you just made, and each ships its full workflow free.
Speed to Lead: reply to form leads in minutes · AI Lead Qualification: score and route every lead
Before You Ask
Yes. n8n ships HubSpot nodes for contacts, companies, deals, and more, plus a HubSpot trigger. For reads they are fine. For contact writes we use the v3 API through the HTTP node instead, because the native upsert runs on the legacy v1 endpoint and registers a conversion, which can loop your own automation.
Zapier is faster to click together; n8n gives you real logic: branching, code, AI steps, human approval, and self hosting with no per task pricing. If your automation is one trigger and one action, either works. Anything with judgment in it favors n8n, and at volume the pricing difference is not close.
No. Private apps and webhook subscriptions work on free and Starter HubSpot plans, which is exactly what this guide uses. You bring an n8n instance, which is free self hosted. Paid HubSpot tiers add more objects and properties you can automate, but the connection is the same.