n8n + HubSpot
n8n HubSpot Integration: CRM Workflows With AI Steps and Human Approval
For sales-led and B2B teams that want HubSpot updated, routed and summarized automatically, with a person approving anything that reaches a customer.
What the n8n HubSpot integration covers
n8n connects to HubSpot through two built-in nodes. The HubSpot node reads and writes CRM data: contacts (create or update, get, search, delete, add to or remove from lists), companies (including search by domain), deals, engagements, forms (get fields, submit data) and tickets. The HubSpot Trigger starts a workflow when a company, contact, deal or ticket is created, deleted or has a property change, and also covers conversation events. Anything the node doesn't cover goes through n8n's HTTP Request node using the same HubSpot credential, as of October 2026.
The HubSpot node can also act as a tool for an n8n AI Agent, so a model such as Claude can look up or update a record as one step in a larger workflow. That is where guardrails matter most. How we approach n8n generally is on our n8n consulting page.
What you can automate with n8n and HubSpot
These are the n8n HubSpot workflows Operator Intelligence scopes most often for sales-led teams.
Inbound lead routing and scoring
A new contact or form fill triggers enrichment, Claude scores fit against your ideal customer profile, and n8n sets the owner and alerts the rep in Slack. Low-confidence scores go to a person.
Learn moreDeal hygiene alerts
Deals with no next step, a stale close date or a missing amount get flagged to the owner each morning, with a suggested update.
Ticket triage
New tickets are classified, prioritized and routed, and Claude drafts a first reply for a person to approve.
Meeting and email logging
Call notes and email threads become engagement records on the right contact and deal, without duplicates.
Weekly pipeline digest
A Monday summary of pipeline movement, slipped deals and new opportunities, posted to Slack or email.
Cross-system sync
Orders, invoices or support data from other systems written to HubSpot properties, with retries and duplicate checks.
Setup options: n8n, Claude's HubSpot connector or the HubSpot MCP server
Operator Intelligence often uses more than one: reps work through the connector, and repeatable work runs in n8n. Details as of October 2026.
| Option | What it is | Best for |
|---|---|---|
| n8n HubSpot workflow | Triggered or scheduled workflows on the HubSpot node, with AI steps where judgment is needed | Repeatable CRM work that should run without anyone asking |
| HubSpot connector in Claude | Made by HubSpot and in Claude's directory since November 2025; search and update contacts, companies, deals, tickets and campaigns from chat | Reps and managers asking ad hoc questions or making one-off updates |
| Remote HubSpot MCP server | Generally available since April 13, 2026; reads CRM, marketing and activity data and creates or updates core CRM objects, using OAuth 2.1 with PKCE and each user's own record permissions | Custom agents and other MCP clients |
| n8n with MCP | n8n's MCP Client Tool calls MCP servers from a workflow, and its MCP Server Trigger offers approved workflows to Claude as tools | Letting Claude trigger a reviewed, logged workflow instead of writing to the CRM directly |
n8n HubSpot credentials and scopes
n8n's HubSpot credential options, from n8n's documentation as of October 2026. The credential decides what a workflow can touch, so we choose it before building.
| Credential | Used for | Notes |
|---|---|---|
| Service key (recommended by n8n) | HubSpot node | In public beta at HubSpot; creating one needs super admin or Developer tools access. HubSpot recommends service keys over legacy private apps |
| OAuth2 | HubSpot node | n8n Cloud can use Connect my account; self-hosted n8n needs its own HubSpot public app |
| Developer API key | HubSpot Trigger | Needs a HubSpot developer account plus a public app's client ID, client secret and app ID |
| API key | Not for new builds | HubSpot deprecated regular API keys |
Permissions, rate limits and security
Most n8n HubSpot failures are operational, not technical. The controls Operator Intelligence builds in:
- Least-privilege scopes. n8n recommends read and write scopes for contacts, companies and deals plus tickets, forms and lists for the HubSpot node, and only read scopes for the Trigger. We remove anything a workflow doesn't use.
- One trigger per app. n8n warns that activating a second HubSpot Trigger stops the first, because HubSpot allows one webhook at a time, so several workflows route from one trigger.
- Rate limits. HubSpot allows service keys and privately distributed apps 100 requests per 10 seconds on Free and Starter and 190 on Professional and Enterprise, with a daily limit shared across every app in the account. Backfills run in batches.
- No duplicates or loops. Deduplication keys on email or domain, and guards so an update doesn't re-trigger its own workflow.
- Human approval on risky tools. n8n can pause an AI Agent before a chosen tool runs and ask a reviewer in Slack, Gmail, Microsoft Teams or another channel; a denial cancels the action.
- Credentials and hosting. Credentials stay in n8n's credential store under your company's accounts, on n8n Cloud or self-hosted n8n.
n8n and HubSpot are trademarks of their respective owners. Operator Intelligence is an independent consultancy.
OI example: the patterns behind a typical n8n HubSpot build
Operator Intelligence hasn't published an n8n HubSpot case study, so this is a typical build drawn from two shipped projects. For Mail New England, a direct mail company, we built an n8n workflow with Google Sheets and Gmail in three weeks that validates client files, emails clients about errors and routes corrected files to the print team, removing about 20 hours a week of manual review. For Wizard Leads, a Wizard-affiliated company, we built a Claude Sonnet app that monitors 15+ channels and scores leads; lead opportunities rose 35% in six months.
A typical n8n HubSpot build combines those patterns: form fills and new contacts trigger n8n, Claude scores and summarizes each lead, n8n writes the score and owner back to HubSpot, and anything below the confidence threshold waits for a person. Read the Mail New England case and the Wizard Leads case, or see AI for B2B sales.
How we build an n8n HubSpot integration
Map the CRM process
Which records change, who owns them and where the hours go today.
Choose credentials and hosting
Service key or OAuth, n8n Cloud or self-hosted, and the narrowest scopes that work.
Build against test records
Development runs on test contacts and deals, so production data isn't touched while logic changes.
Add AI steps and approvals
Claude scores, classifies or drafts; approvals sit in front of anything that sends or overwrites.
Test on real history
Run last month's leads or tickets through the workflow and compare with what your team did.
Launch and hand over
Error alerts to a named owner, a runbook and training on how to pause the workflow.
Frequently asked questions
Is n8n better than Zapier for HubSpot?
It depends on volume, logic and who maintains it. n8n suits high volumes, branching logic, AI agent steps and self-hosting; Zapier can be simpler for a non-technical owner with a few automations. Our n8n vs Zapier vs Make comparison covers the trade-offs.
Do we need a HubSpot developer account?
Only for the HubSpot Trigger node, which uses a developer API key with a public app's IDs. The HubSpot node itself runs on a service key or OAuth2.
Can AI update HubSpot records without review?
It can, but we limit it. Low-risk enrichment fields can write directly with logging; anything that changes owners or stages, sends a message or overwrites data goes through n8n's human approval step first.
Should we use n8n Cloud or self-host?
n8n Cloud suits teams that want low maintenance. Self-hosting keeps CRM data on your infrastructure but makes updates, backups and security your job, or ours on a support retainer.
What does an n8n HubSpot integration cost?
Cost depends on the number of workflows, systems and exceptions, whether AI steps are involved and how you host n8n. Each workflow is scoped and quoted as a project. Request a scoped proposal.
How long does it take?
A single well-defined workflow can ship in a few weeks; Mail New England's n8n build took three. Quick-win pilots usually ship in four to six weeks.
Put your HubSpot busywork on n8n
Bring us the CRM task your team repeats most. We'll map it, recommend n8n, the HubSpot connector or both, and estimate what it should save. Or browse other AI integrations.
Book a scoping callSources
- n8n docs, HubSpot node (2026): n8n HubSpot node operations: Contact (create/update, delete, get, get all, get recently created/updated, search), Contact List (add, remove), Company (incl. search by domain), Deal, Engagement, Form (get fields, submit), Ticket; usable as an AI tool; HTTP Request node with predefined HubSpot credential for other operations
- n8n docs, HubSpot Trigger node (2026): HubSpot Trigger events for company, contact, conversation, deal and ticket (created, deleted, property changed, etc.); activating a second trigger stops the previous one because HubSpot allows one webhook at a time
- n8n docs, HubSpot credentials (2026): HubSpot credentials in n8n: service key (recommended, public beta), OAuth2 (Cloud Connect my account; self-hosted needs a public app), Developer API key for the Trigger (developer account, public app client ID, secret and app ID), API key deprecated; private apps are legacy; recommended scopes listed
- n8n docs, Human-in-the-loop for AI tool calls (2026): n8n human-in-the-loop for AI tool calls: review via n8n Chat, Slack, Discord, Telegram, Microsoft Teams, Gmail, WhatsApp Business Cloud, Google Chat or Outlook; denied actions are canceled
- n8n docs, MCP Client Tool (2026): MCP Client Tool lets n8n agents use tools exposed by an external MCP server, with tool selection All, Selected or All Except
- n8n docs, MCP Server Trigger (2026): MCP Server Trigger lets n8n act as an MCP server, making n8n tools and workflows available to MCP clients
- Anthropic, Claude connector directory (2026): HubSpot connector for Claude: made by HubSpot, Anthropic verified, added November 2025; search and update contacts, companies, deals, tickets, campaigns and more
- HubSpot developer changelog (2026): Remote HubSpot MCP server generally available April 13, 2026; read access to CRM, marketing and activity objects; create/update contacts, companies, deals, tickets, line items, products and activities; OAuth 2.1 with PKCE required; users only access records they already have permission to view or edit
- HubSpot developer docs, API usage guidelines (2026): Private apps and service keys: 100 requests per 10 seconds on Free and Starter, 190 on Professional and Enterprise; daily limits 250,000 / 625,000 / 1,000,000 shared across all apps in the account; public OAuth apps 110 per 10 seconds
Related
n8n consulting
n8n builds that hold up in production.
n8n vs Zapier vs Make
Which automation platform fits your team.
AI for B2B sales
Agents and training for sales-led companies.
Mail New England case study
A three-week n8n build that removed ~20 hrs/week.
Custom MCP server development
Connecting Claude to your systems safely.
AI for marketing agencies
n8n builds across several client CRMs.