TL;DR
- HubSpot workflows: best when the trigger and the work live inside HubSpot. They need a Professional or Enterprise hub (HubSpot KB). Custom code and webhook actions need Data Hub Professional or Enterprise (HubSpot KB — webhooks).
- Make: best for visual, multi-app scenarios run by an ops team, without hosting anything.
- n8n: best when you want to self-host, keep data on your own infrastructure, or write more code inside flows. The self-hosted Community edition runs without a license key (n8n Docs).
- Many good setups combine them. HubSpot decides when something happens; Make or n8n does the cross-app heavy lifting.
The question behind the question
"Which tool should we use?" is really three questions:
- Where does the trigger happen? In HubSpot (a deal stage change), or somewhere else (a Shopify order, a form on another site, a new file)?
- Who will maintain it? A HubSpot admin, an ops person who likes visual builders, or a developer?
- Where must the data live? Some companies need automation running on their own servers for compliance or cost reasons.
Answer those and the choice usually makes itself.
HubSpot workflows
What they are. HubSpot's built-in automation. Enrol records based on criteria, then run actions: set properties, create tasks, send emails, branch, delay.
Plan requirements.
- Workflows are available with Professional or Enterprise subscriptions of Marketing, Sales, Service, Data, Smart CRM or Revenue Hub (HubSpot KB).
- Custom code actions require Data Hub Professional or Enterprise (HubSpot Developers).
- The send a webhook action also requires Data Hub Professional or Enterprise (HubSpot KB).
Strengths.
- No extra vendor or login.
- Native access to every property, list and association.
- Webhook calls made from workflows don't count toward your API limits (HubSpot KB).
Limits to plan around. Custom code actions must finish within 20 seconds and use at most 128 MB of memory (HubSpot Developers). That's fine for API calls and data shaping. It's tight for slow external services.
Make
What it is. A hosted, visual scenario builder with a large app library, including a HubSpot CRM app.
HubSpot specifics (Make Apps Documentation — HubSpot CRM):
- You need a HubSpot user account to use the app.
- HubSpot CRM webhooks and a few other features need a HubSpot developer account.
- A Super Admin of your HubSpot account must pre-approve the Make app before anyone can create a connection.
Strengths.
- Fast to build.
- Easy for non-developers to read.
- Built-in error handlers (Make Help Center — error handling).
- Webhooks for event-driven flows (Make Help Center — webhooks).
Watch out for. Operations count the activities your scenarios perform, and credits are what you pay for them (Make Help Center — credits & operations). High-volume syncs need a quick cost estimate before you commit.
Where I've used Make
Most of my Make work has been HubSpot-centred:
- reservations and listings synced into HubSpot through webhooks;
- Rentvine vendors and work orders created and updated as HubSpot custom objects;
- Shopify + payments real-time sync for an e-commerce brand.
In all three, the trigger lived outside HubSpot, which is exactly where Make shines.
n8n
What it is. A workflow automation tool you can use in n8n Cloud or self-host with Docker, npm or a cloud provider. Without a license key, self-hosted n8n runs as the free Community edition; Business or Enterprise license keys unlock those editions (n8n Docs — hosting).
HubSpot specifics.
- The HubSpot node covers contacts, contact lists, companies, deals, engagements, forms and tickets (n8n Docs — HubSpot node).
- For anything the node doesn't support, use the HTTP Request node with the same credential.
- n8n recommends authenticating with a HubSpot service key, the newer per-account key HubSpot offers for direct REST API access (n8n Docs — HubSpot credentials; HubSpot Developers — service keys).
- The HubSpot Trigger node uses a developer API key. If you activate a second trigger, the previous one stops working, because HubSpot allows one webhook at a time for it (n8n Docs — HubSpot Trigger).
Strengths.
- Self-hosting.
- Code-friendly.
- Good AI and LLM support.
- Error workflows: a separate workflow, starting with an Error Trigger, that runs when an execution fails (n8n Docs — error handling).
Where I've used n8n
I use n8n on HubSpot projects with Revenue Institute (a HubSpot Solutions Partner). I also built an AI contract processing flow combining n8n, HubSpot, OpenAI (o1-mini) and JavaScript.
Side-by-side
| HubSpot workflows | Make | n8n | |
|---|---|---|---|
| Hosting | Inside HubSpot | Hosted by Make | n8n Cloud or self-hosted |
| HubSpot plan needed | Pro/Enterprise hub; Data Hub Pro+ for code and webhooks | Any HubSpot account (Super Admin pre-approval) | Any HubSpot account with a service key or OAuth |
| Best trigger | HubSpot record changes | External apps, webhooks | External apps, webhooks, schedules |
| Code | Node.js (Python beta) in custom code actions | Visual modules first | Code nodes, HTTP Request |
| Error handling | Action logs, automatic retries for rate-limit errors in custom code | Error handlers | Error workflows |
| Who maintains | HubSpot admin | Ops team | Developer / technical ops |
A practical decision path
- Trigger and outcome both in HubSpot? Use a HubSpot workflow.
- Need one or two API calls inside that workflow and you have Data Hub Pro? Use a custom code action.
- Trigger outside HubSpot, or 3+ apps involved? Use Make or n8n.
- Data must stay on your servers, or volumes would make per-operation pricing painful? Lean towards self-hosted n8n.
- The team maintaining it doesn't write code? Lean towards Make or native workflows.
Combining them well
A pattern I use a lot:
- A HubSpot workflow decides when something should happen (for example, a deal reaches Closed won).
- If you have Data Hub Pro+, a webhook action hands off to Make or n8n. Otherwise, Make or n8n watches for the change.
- The external flow does the cross-app work (create a project in ClickUp, a customer in an ERP, a payment link in Stripe).
- Results come back to HubSpot as properties, notes or associated records.
For a ClickUp handoff I built, a deal stage change checked whether a ClickUp space existed. If it didn't, it created the space; then it created the task. That's exactly this split between "when" and "do".
Common mistakes
- Two tools writing the same property. Pick one owner per field.
- No unique IDs. Every sync should store the other system's ID in HubSpot so retries update instead of duplicating.
- Silent failures. Turn on Make error handlers or n8n error workflows, and send alerts somewhere a human reads.
- Ignoring HubSpot rate limits. These apply whichever tool calls the API (HubSpot usage guidelines).
Sources
- HubSpot KB — Create workflows: https://knowledge.hubspot.com/workflows/create-workflows
- HubSpot KB — Use webhooks with HubSpot workflows: https://knowledge.hubspot.com/workflows/how-do-i-use-webhooks-with-hubspot-workflows
- HubSpot Developers — Custom code actions: https://developers.hubspot.com/docs/api-reference/latest/automation/workflow-actions/custom-code-actions
- HubSpot Developers — Service keys: https://developers.hubspot.com/docs/apps/developer-platform/build-apps/authentication/account-service-keys
- HubSpot Developers — Usage guidelines: https://developers.hubspot.com/docs/developer-tooling/platform/usage-guidelines
- Make Apps Documentation — HubSpot CRM: https://apps.make.com/hubspotcrm
- Make Help Center — Webhooks: https://help.make.com/webhooks
- Make Help Center — Error handling: https://help.make.com/error-handling
- Make Help Center — Credits & operations: https://help.make.com/credits-and-operations
- n8n Docs — Host n8n: https://docs.n8n.io/hosting/
- 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: https://docs.n8n.io/integrations/builtin/trigger-nodes/n8n-nodes-base.hubspottrigger/
- n8n Docs — Error handling: https://docs.n8n.io/flow-logic/error-handling/
FAQ
Do I need Data Hub to call an external API from a HubSpot workflow? Yes. Both the webhook action and custom code actions require Data Hub Professional or Enterprise.
Can n8n run on my own server? Yes. Self-hosted n8n runs as the free Community edition without a license key, or as Business/Enterprise with one (n8n Docs).
Why did my n8n HubSpot Trigger stop working? Usually because a second HubSpot Trigger was activated. n8n's docs explain that the newer trigger replaces the earlier webhook.
Is Make or n8n better for HubSpot? Neither wins everywhere. Make suits visual, hosted scenarios; n8n suits self-hosting and code-heavy flows.