n8n and Zapier get compared on the same three axes every time: n8n is cheaper, n8n can be self-hosted, Zapier is easier. All three are true. None of them tells you what your Notion to HubSpot workflow will actually cost on each, because they skip the one thing that decides the bill, which is what each platform counts.
n8n counts runs. Zapier counts steps. For a two-step automation that difference barely registers. For the kind of workflow a Notion to HubSpot job usually turns into, with a search, a lookup, a formatter and a write, it decides everything.
| Products | n8n | Zapier | NoteLinker |
|---|---|---|---|
| Billed By | Executions (1 per workflow run) | Tasks (1 per successful action) | Flat per account |
| Five-Step Run Costs | 1 execution | 5 tasks | No meter |
| Empty Trigger Checks | Free | Free | Nothing to schedule |
| HubSpot Access | Every plan; trigger needs a developer app | Premium app, paid plans only | Included |
| Self-Hosting | Free Community Edition | Not available | Nothing to host |
| When You Run Out | Keeps running, overage may apply | Pay-per-task overage | No limit to hit |
| Entry Price | €20/mo annual (2,500 executions) | $19.99/mo annual (750 tasks) | $19/mo (flat) |
| Best For | Long workflows with a technical owner | Simple flows built by non-engineers | Sales notes in the CRM |
In this article
1.
2.
3.
4.
5.
6.
7.
8.
The Core Difference: n8n Counts Runs, Zapier Counts Steps
Both products run the same shape of automation. A trigger watches an app, and a chain of steps searches, transforms and writes. Zapier calls the chain a Zap. n8n calls it a workflow and each step a node.
The unit is where they part. n8n's pricing page defines an execution as "a single run of your entire workflow. It doesn't matter how many steps are in the workflow or how much data it processes." Zapier's help centre defines a task as "any successful action that runs in Zapier", and counts one per action per run.
So the same workflow is priced on two different axes. On n8n, cost follows how often the workflow fires. On Zapier, cost follows how often it fires multiplied by how many actions it has.
Both are generous in the same place. Zapier never bills trigger steps, filters, paths or formatter steps. n8n's docs say "polls that return no results don't count as an execution", and manual test runs, error workflow runs and sub-workflow calls are free too. That shared rule is what separates both of them from Make, which bills every check whether it finds anything or not.
n8n vs Zapier Pricing, Side by Side
Prices below are from the vendors' own pricing pages as of September 2026. n8n prices in euros; Zapier in US dollars.
n8n Cloud. Starter is €20 a month billed annually for 2,500 executions, unlimited active workflows and 5 concurrent executions. Pro is €50 a month billed annually for 10,000 executions, with admin roles, workflow history and more concurrency. Business is €667 a month billed annually for 40,000 executions with SSO, Git version control and queue mode, and the pricing page now marks it self-hosted only, with a waitlist for a hosted version. Enterprise is custom. There is no free cloud plan; the free option is self-hosting the Community Edition.
Zapier. Free is $0 for 100 tasks a month, 15-minute polling, two-step Zaps and no premium apps. Professional starts at $19.99 a month billed annually, or $29.99 monthly, for 750 tasks with two-minute polling, then $39 for 1,500, $49 for 2,000, $89 for 5,000 and $129 for 10,000, billed annually. Team starts at $69 a month billed annually for 2,000 tasks, 25 users and one-minute polling, up to $249 for 20,000. Enterprise is custom.
The entry prices look identical, and they buy very different amounts. 2,500 executions and 750 tasks are not the same quantity, and the gap between them grows with every step in the workflow.
The Arithmetic for a Real Notion to HubSpot Flow
Take the common version of the job. When a Notion row changes, find the matching HubSpot contact by email, tidy a couple of fields, and update the contact. That is a trigger, a search, a formatter and an update. Assume 600 row changes a month, which is a small sales team.
- 1
On Zapier
The trigger and the formatter are free. The search and the update are a task each, so 600 changes cost 1,200 tasks. That is past the 750 on the $19.99 tier and lands on the 1,500-task tier at $39 a month billed annually.
- 2
On n8n
Each change fires the workflow once. 600 changes are 600 executions, which fits comfortably inside the 2,500 on Starter at €20 a month billed annually. The search, the formatter and the update cost nothing extra.
- 3
Now make the workflow realistic
Real flows grow. Create the contact if the search finds nothing, associate it with the open deal, and log a note. That is five actions per run. Zapier now needs 3,000 tasks a month, which is the $89 tier. n8n still needs 600 executions and stays on Starter.
On Zapier, every step you add to a workflow is a line on the invoice. On n8n it is free, right up until the volume itself pushes you off a plan.
Where n8n hits a cliff
n8n's advantage is in step count. Its weakness is volume. Above 10,000 executions a month, n8n Cloud publishes nothing between Pro at €50 and Enterprise. Business is the next published tier and costs 13 times as much, and it is self-hosted only. n8n says workflows keep running past the quota but "overage charges may apply if you do not upgrade", and it publishes an overage rate only for Business, €4,000 per 300,000 executions.
Zapier's curve is smoother. Professional and Team have published tiers up to 20,000 tasks, and Zapier lists task tiers well beyond that. A workflow that fires 15,000 times a month with a single action is simple to price on Zapier and a sales conversation on n8n Cloud.
Notion and HubSpot Support on Each
Both cover both apps. The setup cost sits in different places.
Zapier treats HubSpot as a premium app, so there is no free Notion to HubSpot Zap and you start on Professional. In return, connecting HubSpot is an ordinary sign-in. Zapier's Notion app works in terms of data sources, with triggers for a new data source item, updated properties in a data source item and updated content in a data source item, and actions to create, update, and find or create items, and to add blocks or content to a page.
n8n includes both nodes on every plan, Community Edition included. The Notion node is deep on page bodies: it can get a page or a block list as Markdown and update a page from Markdown, as well as create, get and update database pages. Its Notion Trigger fires on a page added to or updated in a database. The HubSpot node covers contacts, contact lists, companies, deals, engagements, forms and tickets, and accepts a private app token or OAuth.
The HubSpot Trigger is where n8n asks more of you. It needs a HubSpot developer account and an app to supply the developer credentials. And n8n's own docs carry this warning: "If you activate a second trigger, the previous trigger stops working... HubSpot only allows one webhook at a time." In practice that means one HubSpot-triggered n8n workflow per portal, so the natural design of one workflow per object has to become one workflow that routes everything.
Building Experience: A List of Steps vs a Node Canvas
Zapier builds downward. A Zap is a vertical list with Paths for branching and Formatter for clean-up, and a non-technical teammate can usually build, read and fix one without help. That is the real product Zapier sells, and the price per task is partly a price for not needing an engineer.
n8n builds across a canvas. Nodes pass items to each other, expressions can reach into any earlier step, a Code node takes JavaScript or Python, and sub-workflows let you factor out shared logic. It is far more capable for anything that branches, loops or reshapes data, and it expects you to think about items and JSON. Most teams that choose it have someone who enjoys that.
n8n is the better buy when
- Workflows have many steps per run
- Someone technical will build and own them
- You want code, expressions and sub-workflows
- Data residency means self-hosting
- You need to read or write Notion page bodies as Markdown
Zapier is the better buy when
- Non-technical teammates build the automations
- Workflows are a trigger plus one or two actions
- Volume will pass 10,000 runs a month
- You want HubSpot connected with a normal sign-in
- You would rather pay overage than run a server
When You Run Out
Unusually for this category, neither platform simply stops.
n8n keeps running. Its pricing page says "your workflows will continue running without interruption, but overage charges may apply if you do not upgrade to the next usage tier." What those charges are below Business is not published.
Zapier keeps running and bills more. On Professional and Team, going over the limit switches you to pay-per-task billing at 1.25 times your per-task rate on annual plans and 2.5 times on monthly plans. Without pay-per-task, Zapier holds new Zap runs until the billing cycle resets.
Neither one checks afterwards that Notion and HubSpot still agree. If a run fails halfway, both leave the repair to you. That gap is what a dedicated sync engine sells instead, covered in Whalesync vs n8n and Whalesync vs Zapier.
What Neither Tool Does: The Note Itself
Both tools move fields, and for most Notion to HubSpot jobs fields are enough. One very common job does not fit.
A rep writes up a discovery call in Notion: a heading, a bulleted list of requirements, a bolded objection their manager needs to see. n8n can read that page as Markdown and Zapier can read its content, and both can write it into a HubSpot note. What lands is flattened, because a HubSpot engagement body does not use Notion's block format, and it is a copy. Edit the Notion page tomorrow and HubSpot still shows yesterday, unless you build a second workflow that watches the page and rewrites the note, which is one more execution or a few more tasks on every edit.
If the job is the note, skip the workflow
NoteLinker connects Notion and HubSpot in two minutes with no field mapping and shows your formatted Notion notes on the contact and deal records your team already opens.
NoteLinker was built for that half of the problem. It renders Notion rows directly on HubSpot contact and deal records with the formatting intact, matches on the email or deal name you already have, and costs a flat $19 a month with no executions, tasks or servers. It is not an automation platform, which is why plenty of teams run it next to n8n or Zapier.
Zapier vs n8n: Which One Should You Choose?
One execution per run however many steps, a far deeper Notion node, code and sub-workflows, and a free self-hosted edition. Budget from €20 a month billed annually on Cloud, and plan around the jump after 10,000 executions.
The easiest builder here, HubSpot connected with a normal sign-in, smooth pricing at high volume, and triggers and formatter steps that are never billed. Budget from $19.99 a month billed annually, since HubSpot needs a paid plan.
Two-minute OAuth setup, no field mapping, formatting preserved on the contact and deal record. Flat $19 a month. Pair it with either tool above if you also automate fields.
The short version: n8n if the workflow is long and you have someone to own it, Zapier if it is short and the people building it are not engineers, and neither if what is stuck in Notion is the writing rather than the fields.
For more on each tool, see NoteLinker vs n8n, NoteLinker vs Zapier and the best Zapier alternatives for Notion and HubSpot. For the third automation platform on most shortlists, Make vs Zapier covers the credit meter that charges for every check, and the best Make.com alternative runs through the field from Make's side.
Get your Notion notes onto HubSpot records today
No executions, no tasks, no server to run. Connect Notion and HubSpot with NoteLinker and see your first synced note in two minutes.
Get HubSpot and Notion tips delivered straight to your inbox
We'll email you 1-3 times per week, and never share your information.