n8n is an open-source workflow automation tool, comparable to Zapier or Make, with one key difference: you can host it on your own server with no per-usage fees. If you’ve been connecting apps with Zapier and noticed the monthly bill creeping up, this post explains what n8n is, the problem it solves, and when it starts to make sense for an online store.
What is n8n exactly?
n8n is a workflow automation tool, conceptually equivalent to Zapier or Make. Its key difference: it’s open source and can be self-hosted on your own server with no licence cost. An official cloud version exists and competes on price with the usual SaaS tools, but most of n8n’s growth over the last three years has come from self-hosted installs.
Visually it’s a canvas: you drag nodes (each one a trigger or an action), connect them with arrows and build the flow. Each node receives data, transforms it and passes it on. The philosophy is closer to Make than to Zapier: branching, loops, explicit error handling.
Where does n8n come from?
The project started in 2019 in Germany as an open-source alternative to Zapier. For years it was a niche tool used by technical teams. In 2023-2024 it matured into a full product, with its own cloud, enterprise tier and an active community publishing integrations faster than the core team.
By 2026 it’s the reference open-source automation tool. Its growth comes down to three factors: price, control over your data, and the speed at which the community adds new integrations.
The Zapier “tasks” trap
Zapier charges per task: every step a Zap executes counts as a task. A simple Zap (trigger + action) uses one task per run. A multi-step Zap with three steps uses three. Zapier’s plans scale with monthly task volume.
The problem shows up as your store grows. A store with 1,000 orders a month firing a five-step automation per order burns 5,000 tasks/month from that one automation. Ten similar automations and you’re at 50,000 tasks. The matching plan jumps from €30 to €100-150 a month within weeks.
The trap isn’t that Zapier is expensive: it’s that its price scales with your business activity, while the marginal value of each automation doesn’t scale the same way. Stores that have grown for two years find themselves paying four figures a year for automations that would cost tens elsewhere.
Open-source model with optional cloud
n8n ships with a community licence (free for internal use) and a commercial cloud version from €20-50/month. The difference with Zapier is that the community version isn’t a crippled tier: it includes every integration and all core features. What the community licence limits is enterprise use: multi-tenant execution or reselling it as a service.
For a single online store, the self-hosted community version is functionally equivalent to cloud with no task ceiling. Your monthly cost is the VPS it runs on plus the time to maintain it.
Quick comparison with Zapier and Make
- Pricing model. Zapier per task. Make per operation (more granular). n8n cloud per workflow execution (a 30-node workflow = one execution). n8n self-hosted free.
- Native integrations. Zapier 5,000+. Make 1,000+. n8n 400+ official plus an active community. The gap matters less than it looks: many of Zapier’s integrations are barely used.
- Self-hosting. Only n8n. It’s the key differentiator for sensitive data or high volume.
- Learning curve. Zapier easiest. Make intermediate. n8n requires grasping its item model but gives more control.
- Extensibility. n8n lets you write custom nodes in inline JavaScript; the other two only allow what the vendor has already built.
Who uses n8n today?
The typical 2026 adoption profile: product and operations teams at mid-volume online stores (500-5,000 orders/month), agencies running several stores that consolidate automations on shared infrastructure, and companies that need to automate but can’t send data to an external vendor’s cloud for compliance reasons.
Small individual stores still use Zapier for simplicity. Large enterprise stores sometimes jump straight to enterprise tools like Microsoft Power Automate or Workato. n8n lives in the growing middle.
Cases where Zapier still wins
Three profiles where Zapier is the right answer and migrating to n8n doesn’t pay off:
- Small store with no technical team. If your total monthly volume is under 5,000 tasks, Zapier is free or nearly so, and its simplicity is hard to beat.
- You need a niche app only Zapier integrates with. It happens with very specific SaaS tools. Before switching, check that the apps you use have an n8n integration or that the generic HTTP node is enough.
- Time-to-market matters more than three-year cost. If you need the automation running this afternoon and can’t spend hours learning, Zapier wins even while being more expensive.
When does n8n start to make sense?
Three signs you’re ready to evaluate n8n:
- Your monthly Zapier or Make bill is over €100 and still growing.
- Your team has at least one person comfortable with Docker, nginx or running scripts in a console.
- You want automations the linear Zapier model can’t do (complex loops, heavy data manipulation, custom integrations with your own APIs).
If two of the three are true, evaluating n8n is reasonable. If all three are true, migrating probably pays off.
What about WooCommerce or PrestaShop specifically?
WooCommerce has a robust native REST API and well-documented webhooks: all three tools —n8n, Zapier and Make— talk to it without friction, with triggers for order created, updated, completed, or payment confirmed. PrestaShop is more uneven: native integration in Zapier and Make relies on third-party modules or the PrestaShop webservice API, which works but is old; n8n has an active community publishing unofficial PrestaShop nodes, and the rest is covered with the generic HTTP node against its REST API.
At Zeyvro we solve it this way: for stores under 200 orders a month with no technical team, we recommend Zapier or Make; for mid-volume stores with a minimal team, n8n cloud for its per-execution pricing; for high-volume stores with someone comfortable in a console, self-hosted n8n gives the best return per euro.
Next step
If your store runs on WooCommerce or PrestaShop, the trickiest part of any n8n automation is the first link: getting data out of the store and into n8n reliably and securely. We cover it in the guide to connecting your store to an ERP.
To avoid building that first link by hand, the Zeyvro n8n Connector module for PrestaShop 8 sends your store events (orders, customers, stock, carts) to n8n with signed webhooks, ready to use. If you get stuck on the initial setup, email us at hola@zeyvro.com with your current configuration and the specific problem.
Frequently asked questions
What is n8n in one sentence?
An open-source tool to automate workflows between applications, which you can host on your own server without paying per execution volume.
Is n8n free?
The self-hosted (community) version is free and open source; you only pay for the VPS it runs on. There’s also a paid cloud version from €20-50/month.
Is n8n better than Zapier?
It depends on volume. With few automations, Zapier is simpler and nearly free. Above ~€100/month of billing or when you need complex logic, self-hosted n8n usually pays off.
Do I need to know how to code to use n8n?
Not for basic flows: you build them by dragging nodes. It helps to have someone comfortable with Docker for self-hosting, and it allows inline JavaScript for advanced cases.
Does n8n work with WooCommerce and PrestaShop?
Yes. WooCommerce has native API and webhooks; PrestaShop needs a bit more configuration. A connector module handles the store side and leaves the data ready for n8n.