n8n vs Make: what one query automation scenario really costs

Form → CRM → notification → report: one scenario, not four

The scenario starts with a form on the site. The client enters data and clicks send. At that moment, the chain starts:

Each arrow is a separate step, and n8n and Make run it as an operation.

The first step saves the lead in the CRM. The second sends a notification to the salesman, for example via WhatsApp or Messenger. The third step, run once a day, collects leads into a report for the owner. In Make, each of these steps counts separately as an operation towards the limit. In n8n, the entire scenario execution counts, not individual steps in between. That's a different billing unit. It grows differently with the number of leads, so comparing the price lists alone doesn't tell you your cost.

Who presses the button: n8n, Make, and the people on both sides of the form

Behind every scenario is someone who runs it and someone who maintains it. You install n8n on your own server or run it in the provider's cloud. Both options require an administrator who handles updates and access. Make operates exclusively as a cloud service, so the administrator only manages accounts and permissions within the platform itself.

Connecting the form to the CRM is the first step in the chain, but not the last. The receptionist or salesman gets a notification about a new lead. The manager checks the report at the end of the day. The owner decides whether a given lead is worth calling the same day, based on CRM data, not memory. Each of these people uses a different fragment of the same chain. They, not n8n or Make, bear responsibility for what happens to the lead next.

The tool price is not the implementation price

The n8n price list and the Make price list are two different numbers. Neither tells you how much it costs to run the scenario in your company. The tool license is a fee you pay the provider. Configuration, tests, and the connection to your CRM are work on our side — and that is what decides whether the scenario runs at all. The cost depends on how many steps it has to close and on the state of the data it has to carry; the scope is settled after a conversation about exactly what it should do.

We quote integrations with email and messengers after a conversation about what exactly they have to do — every channel hands over its data differently, so every channel is a different piece of work. If the scenario should save data directly in the CRM and update the lead status, that adds CRM automation — another stretch of the same chain. They look separate only on paper; they make sense together, because an inquiry that reached the CRM and stopped there is just as lost as one that never arrived.

The n8n or Make subscription alone is a cost that changes with the provider. You check the current amount directly in the n8n or Make price list, at the provider itself. We price implementation and scenario maintenance, not the tool license.

What breaks when the operation limit runs out mid-month

A scenario that runs without errors for three weeks can stop mid-month. The operation limit in Make runs out, and subsequent runs queue up or get rejected. In n8n, the error looks different: the execution ends with an error code, and the scenario doesn't resume on its own.

The symptom is always the same. The form on the site works, but the lead doesn't reach the CRM. The receptionist doesn't see the new lead in the system. The salesman doesn't get a notification on WhatsApp. The client waits for a call that never comes because nobody knows about their submission. The administrator usually notices the failure only when the owner asks why last week's report is empty.

That's why the scenario needs a separate error handling branch that sends an alert when a step doesn't execute. Without it, the error is silent, and the loss is the lead that never reached the salesman's hands.

When it's not worth comparing n8n and Make

For one lead per day, neither of these tools is worth it. A simple form after which the receptionist calls manually anyway doesn't need a scenario in n8n or Make. An email notification is enough.

We don't promise that automation will lower your costs with low lead volumes. Maintaining the scenario, testing, and monitoring limits is work. With a few leads per month, that work simply doesn't pay off.

It's also not for everyone when the form data must stay in one system for legal reasons. If your company processes sensitive data and you don't yet have a processing basis compliant with RODO, an external scenario connecting several platforms is an additional risk. Better to solve it before automation, not during.

Who is responsible for the scenario after implementation

Implementation ends on launch day, but responsibility remains. Someone needs to monitor whether the scenario runs, whether the limit has run out, and whether notifications reach the salesman. In a small business, the owner takes on this role. In a larger company, it's the administrator or department manager who receives the report with the number of leads and exceptions.

You have control over the process when you see the numbers, not when you trust that the scenario just works. AI-based automations can qualify leads themselves, but the decision about a lead's priority is always made by a human, based on CRM data.

That's why a good scenario ends with a report, not just a notification. A report that shows this instead of guessing turns the question "does automation work" into an answer based on numbers, not the administrator's impression.

Frequently asked questions

Can the scenario be transferred from Make to n8n without rewriting it from scratch?

Not directly. Make and n8n have different module logic and different ways of saving connections, so the scenario must be recreated step by step in the new tool. The chain itself - form, CRM, notification, report - stays the same, only the way it's written changes.

Does n8n need to be self-hosted?

Not always. You can run n8n on your own server or use the cloud version from the provider, similar to Make. The choice affects who handles updates and availability. With your own server, your administrator does it; with the cloud, the provider does.

Does the quote for query automation include the tool itself, n8n or Make?

No. The price, worked out after a conversation, includes building and configuring the scenario, meaning connecting the form, CRM, and notifications. You settle the n8n or Make license, if paid, separately and directly with the tool provider.

What exactly counts towards the operation limit?

In Make, almost every scenario step is a separate operation, including internal ones like filtering or data formatting. In n8n, the entire execution usually counts, not individual steps within it. The exact rules change with the provider's price list, which is why you check them directly before choosing a plan.

Does form automation with customer data require additional RODO consents?

The scope of additional consents depends on what data the form collects and what you use it for next. The data administrator in your company determines it before the scenario runs. You can find general personal data processing rules on the UODO website.

Let's talk about what this chain looks like in your company and which variant - n8n or Make - makes sense with your number of leads.