n8n vs Make for Ecommerce: What Each One Bills You For

Most comparisons of n8n and Make open with a feature table, and the table ends in a tie. For an online store the decision usually turns on something the table barely mentions: what each tool counts as one unit of work, and who ends up looking after the automation once it matters to revenue.

Here is the short version. Make is the better pick when a marketing or operations person will build and own the automations. n8n is the better pick when the flows are long, touch orders or stock, and someone technical is available to keep them running. The rest of this piece explains why, with the arithmetic.

What each tool charges for

The two platforms meter different things, and everything else follows from that.

Make counts credits, and a credit is spent every time a step in your scenario does something. Its own pricing page says that each module action, such as adding a Google Sheet row or fetching Gmail account data, counts as one credit. Reading, searching, creating, updating, transforming and looping data all cost credits. Routing is free, and so are the error-handling steps.

n8n counts executions. Its documentation, quoted on the n8n pricing page, defines an execution as a single run of the entire workflow, however many steps it has and however much data it handles. A workflow with three steps and a workflow with thirty are the same price per run.

As of 5 October 2026, Make lists a Core plan at $12 a month with 10,000 credits. n8n lists Starter at 20 euros a month, billed annually, with 2,500 executions, and Pro at 50 euros a month with 10,000. Prices move, so check both pages before you budget.

A worked example: one order, eight steps

Take a plain order flow. A new order arrives, the customer is looked up in your CRM, stock is checked, the order is written to the ERP, a shipping label is requested, the tracking number is saved back, a confirmation email goes out, and a row is added to a finance sheet. Call it eight steps. This is a made-up flow for the arithmetic, not a client figure.

On Make that order costs about eight credits. The 10,000 credits in Core cover roughly 1,250 orders a month. A store doing 2,500 orders a month would need around 20,000 credits for this one flow, and that is before the abandoned-cart flow, the returns flow, and the nightly stock sync.

On n8n the same order is one execution. The 2,500 executions in Starter cover 2,500 orders, and adding a ninth or tenth step costs nothing extra.

Notice what the example does not say. At low volume the difference is a few euros a month and nobody should choose a platform over it. The gap only becomes a budget line when flows are long, volumes are high, or both. And n8n's model has its own sharp edge: a flow that loops over a large list inside one run is cheap on the meter, but it can still be heavy on the server that runs it.

Where Make is the better call

If the person who will own the automation is not technical, Make is the safer choice. Its builder is visual, its connectors for common apps are polished, and a marketing manager can read a scenario and see what it does. Make is also cloud-only, which means there is no server to patch and no one to blame when it goes down at the weekend. For lead routing, Slack alerts, simple email sequences and spreadsheet syncing, it is a good default, and the credit bill stays small because the flows are short.

I would also pick Make for a store with a few hundred orders a month and no developer on call. The meter does not matter at that size. Fewer things to look after does.

Where n8n wins, and what self-hosting really costs

n8n pulls ahead when the flow has real logic in it: retries, branching on stock levels, splitting a multi-item order, reconciling two systems that disagree. According to n8n's own comparison with Make, code steps in JavaScript or Python are available on every plan, whereas Make restricts custom functions to its Enterprise plan. That is a vendor's claim about a competitor, so verify it before you rely on it, but it matches what we see in practice: the awkward last stretch of an integration is almost always custom logic.

We use n8n ourselves. Our own publishing and reporting automations run on it, and for a Berlin art and science school we built an enrollment pipeline on n8n that turns every booking into a linked parent, child and course record across six platforms, with no manual re-entry. That job needed splitting multi-item orders and mapping product codes to course codes. It is the kind of work where per-step pricing would have punished the design. The same logic applies to learning platforms: rent the commodity core and build only what is yours.

Then there is self-hosting, which gets sold as "free" and should not be. The Community Edition costs nothing to install, but n8n describes its licence as fair-code, so read the terms before you build a product on top of it. More to the point, a self-hosted instance is infrastructure. Someone has to run the server, apply updates, take backups and notice when it stops. If your team has nobody for that, the managed cloud plans exist for a reason, and the price gap with Make narrows.

The question that actually decides it

Subscription cost is the smaller number. The larger one is what a broken automation costs you. When the flow that writes orders into your ERP fails quietly, you find out when stock counts drift and a customer buys something you do not have. We wrote about the four places Magento ERP integrations break, and almost every one of them is an automation problem, not a platform problem.

So ask three questions before you compare prices. Who will notice when a run fails? Who will fix it, and how fast? And is this flow close enough to money, stock or customer data that failure has a price?

If the honest answers are "nobody technical" and "yes, very close to money", the cheapest platform is not the cheap option. Put the system integration work in proper hands, or pick a tool that matches the skills you actually have.

How to choose

Choose Make if a non-developer owns the flows, they are short, and volume is modest. Choose n8n if the flows are long or touch orders and stock, volume is growing, and you have someone who can look after it, or a partner who will. If you cannot answer the ownership questions, settle that before you settle the tool.

If you are weighing this for your own store and not sure which side of the line you are on, this is the sort of decision we help with at Encomage. We usually start by mapping which flows touch revenue and who would be on the hook when one fails, and only then pick a platform.

Let's discuss your project

By submitting this form, you agree to the processing of your personal data in line with our Privacy Policy.

Frequently Asked Questions

Explore more on this topic

A magnifying glass over a storefront wireframe with a ranked list of five numbered fixes below it

What a Good Ecommerce Website Audit Actually Delivers

Most ecommerce website audits are sold as a score and end in a PDF nobody acts on. A good one ends in a ranked fix list. The five areas it has to cover, what to ask for at the end, and three quick checks that expose a template report.

Line-art valve on a pipeline letting four bright streams through into one vessel while faint trickles drain away

Ecommerce Marketing Automation: Which Flows Pay Off

A small number of automated flows earn most of the money in ecommerce email, and they only work when the order and customer data behind them is right. Which four flows to build first, where automation quietly loses money, and when to build your own workflows instead of buying a platform.

Cutaway of a store building where an intruder slips through a crack in the engine-room foundation beneath the shopfront

Is Your Magento Store Exposed to PHP2Shell? How to Check

PHP2Shell is a pair of critical flaws in PHP itself, confirmed against the latest Magento release. Four questions to your host or agency tell you whether your store is exposed, why a Magento patch won't fix it, and what to do if your store runs on PHP 8.1 or older.

Line-art illustration of a simple ready-made module beside a layered custom structure with one glowing magenta component, representing LMS build versus buy

How to Build an LMS Without Building Most of It

Most of an LMS is a solved problem you can rent. A buyer's view of when custom code is worth it, which standards keep you portable, and how to scope the part that is actually yours.

A shelf of five shipping crates, the oldest two tagged as expired and the newest two clean, with a person reading one of the tags

Magento Isn't End of Life. Your Version Might Be.

Magento the platform is alive and supported to 2029. Individual releases are not: 2.4.4 and 2.4.5 are out of support and 2.4.6 lost standard support on 11 August 2026. What the dates mean for an owner, why Open Source and Adobe Commerce are treated differently, and what to do about it.

Line-art balance scale with a stack of coins on one pan and a heavy block on the other, tilting toward the coins

Is Shopify Plus Worth $2,300 a Month? The Break-Even Math

Shopify Plus costs roughly $2,000 a month more than Advanced. The gateway-fee saving alone only covers that near $500,000 in monthly sales, so below that the case rests on four specific constraints. The break-even math, and who should skip Plus.

Inspired by what you’ve read?

Let’s build something powerful together - with AI and strategy.

By submitting this form, you agree to the processing of your personal data in line with our Privacy Policy.

messages
mechanizm
folder
gray background