Zapier is the easiest option with the most integrations, ideal for simple workflows and non-technical teams, but it charges for every step that runs. Make offers a more powerful visual editor at a generally lower cost per operation. n8n charges per full execution on its cloud or can be self-hosted on your own server, which makes it the most cost-effective for long workflows, high volume or sensitive data, in exchange for requiring more technical know-how.
- Zapier bills by task: every successful action in a workflow counts.
- Make bills by operation (now called credits): every module that runs adds up.
- n8n Cloud bills per full execution, no matter how many steps the workflow has.
- Self-hosted n8n has no license fee for internal use; you pay for the server and maintenance.
- With sensitive data, keeping the workflow on your own server simplifies compliance.
- To get started fast, Zapier; for complex workflows and volume, n8n.
What these tools do
Zapier, Make and n8n are automation platforms: they listen for an event in one app (a form came in, an order was paid, a message arrived) and run actions in others (create the contact in the CRM, send a WhatsApp message, save a row in Google Sheets, issue an invoice). All without a person copying and pasting.
All three share the same concepts: a trigger that starts the workflow, a series of steps or nodes, and conditions that decide which path to take. The difference comes down to four things: how they bill, how complex the workflow can get, where your data lives and who can maintain it.
In our automation service we mainly use self-hosted n8n, but we recommend Zapier or Make when the client needs to manage their workflows without technical help. There's no universal answer.
The difference that matters most: how each one bills
This is the part almost nobody checks before choosing, and the one that surprises people most later.
- Zapier bills by task. Every action that runs successfully counts as a task. The trigger doesn't count and some built-in utilities don't either, but a six-action workflow uses six tasks every time it runs.
- Make bills by operation, which it started calling credits in 2025. Each module that runs usually uses one, including the one that checks for new data. Some modules, such as AI modules, can use more.
- n8n Cloud bills by execution. An execution is one complete run of the workflow, whether it has three steps or thirty.
- Self-hosted n8n (community edition) charges no license fee for your company's internal use. You pay for the server and the time of whoever maintains it.
Here's an example in usage numbers, not dollars. A workflow that receives a lead from Meta, normalizes the phone number, checks whether it exists in the CRM, creates it, sends a WhatsApp message, saves a row in Sheets and notifies the salesperson has six actions. With 1,500 leads a month:
| Platform | Billing unit | Approximate monthly usage |
|---|---|---|
| Zapier | Tasks | About 9,000 tasks |
| Make | Operations or credits | About 10,500 operations (six actions plus the trigger) |
| n8n Cloud | Executions | 1,500 executions |
| Self-hosted n8n | None | Just the server |
The longer the workflow and the higher the volume, the further apart the costs drift. To estimate how many hours of manual work a workflow saves you, use the automation calculator.
Side-by-side comparison
| Criterion | Zapier | Make | n8n |
|---|---|---|---|
| Ease of getting started | The easiest | Medium | Medium to technical |
| Integration catalog | The largest, thousands of apps | Large | Smaller, offset by the HTTP node and community nodes |
| Complex workflows (loops, branches, errors) | Possible, but gets expensive | Very good, visual editor | Very good, with JavaScript or Python code when needed |
| AI agents and AI steps | Yes | Yes | Yes, with agent and memory nodes |
| Where your data lives | Vendor's cloud | Vendor's cloud | Their cloud or your own server |
| Billing model | Per task | Per operation or credit | Per execution, or free when self-hosted |
| Maintenance | None | None | None on the cloud; updates and backups if self-hosted |
When to choose Zapier
- Your team isn't technical and wants to create and tweak its own workflows.
- The workflows are short: two or three steps.
- Volume is low to medium.
- You need to connect a niche app that only Zapier has an integration for.
Zapier is excellent for a small business to start automating in an afternoon: post to a channel when a form comes in, save email attachments to Drive, create a contact in the CRM. The pain point comes when workflows grow and every extra step multiplies usage. It's also worth checking how often your plan polls for triggers: on basic plans it can take several minutes to detect a new event, which matters if you want to respond to a lead instantly.
When to choose Make
- You want workflows with branches, filters, iterators and error handling, but without coding.
- You like seeing the workflow as a diagram.
- Your volume is medium and the workflows have several steps.
Make is a good middle ground. Its visual editor makes it very clear what happens in each module and lets you transform data in considerable detail. Look carefully at how often scheduled triggers run, because a scenario that checks for new data every minute uses operations even when it finds nothing.
When to choose n8n, and why self-host it
n8n has a fair-code license: you can use it and self-host it for free for your company's internal processes; what you can't do is resell it as a service. It makes sense when:
- The workflows are long or the volume is high, because you pay per execution or pay no license at all.
- You handle sensitive data: patient records, financial data, employee information. With n8n on your own server, the data doesn't pass through a third party's cloud, which makes it simpler to comply with Mexico's personal data law (or HIPAA-style rules if you operate in the US).
- You need custom logic: the Code node and the HTTP node let you connect any API, even if there's no official integration.
- You want AI agents that query your knowledge base, classify messages or draft replies.
The hidden cost of self-hosting is operations: updates, backups, monitoring and server security. We run it in Docker on a VPS with encrypted backups; if you don't have someone to handle that, n8n Cloud or Make are the more sensible choice. We explain the difference between shared hosting and a VPS in the guide to shared hosting vs. VPS.
A real case with n8n
At Grupo Cimarra Desarrollos, a real estate developer, leads came in from Meta Ads, two real estate portals and the website, each to a different email inbox. We set up n8n on a dedicated server that normalizes each lead, checks for duplicates, assigns it by shift, sends a WhatsApp message with the brochure in under a minute and logs it in the CRM. It then runs appointment reminders and a 21-day follow-up sequence.
That workflow has dozens of steps. On a platform that bills per step, the monthly volume would have made it expensive; on self-hosted n8n, the cost is the server. The technical details are in the guide to lead follow-up with n8n and WhatsApp.
For a lower-volume business in La Laguna, such as an auto repair shop that just wants to send a WhatsApp message when a vehicle is ready, Zapier or Make solve the same problem in an afternoon.
Common automation mistakes, on any platform
The tool matters less than how the workflows are built. These mistakes show up just the same in Zapier, Make or n8n:
- Not handling errors. If the WhatsApp or CRM API hiccups for a moment, the workflow stops and the lead is lost without anyone noticing. Every important workflow should retry and alert a person when something fails.
- Duplicating contacts. If you don't check whether the phone number or email already exists, the CRM fills up with copies and salespeople call the same customer twice.
- Storing passwords and keys in plain text inside the steps. Always use the platform's credential manager and give each integration only the permissions it needs.
- Workflows nobody documents. Six months later nobody remembers why a step exists. Give each node a clear name and add a note with the workflow's purpose.
- Automated messages that sound like a robot. In Mexico, customers immediately notice a generic WhatsApp message. Use their name, the product they looked at and a human tone; for open-ended conversations, rely on a shared inbox like MonkeyChat.
Before switching on any workflow, test it with real data in a test environment and check the full result, not just that it "ran without errors."
How to decide in five minutes
- List the workflows you want to automate and count the steps in each one.
- Estimate monthly volume: how many leads, orders or messages.
- Look at the data that flows through them. If it's sensitive, lean toward n8n on your own server.
- Ask who will maintain it. Without a technical person, Zapier or Make.
- Test with one real workflow on the free tier of whichever you choose before migrating everything.
And before automating, get the process in order: automating a mess just makes it faster. If you don't know where to start, the digital transformation assessment tells you which processes have the most potential, and the guide to CRMs for small businesses explains where your leads should end up.
