n8n is the main Make alternative when credits are the problem, since it bills one execution per workflow run from EUR 20 a month for 2,500. Zapier is easier for non-technical teammates but counts each action step.
If you're leaving Make because credits run out on scenarios that loop over rows, n8n is the usual answer: it bills one execution per workflow run, however many steps or items it touches. If you're leaving because scenarios got too fiddly for the people who maintain them, Zapier is easier to hand to a non-technical teammate, at a higher price per step. Tray.ai is the step up for integration-heavy teams, and Cargo fits when the scenarios are all GTM enrichment and routing.
Why people move off Make
Credits scale with the data. Make moved its billing to credits, and most module actions cost one. Reading, searching, creating, updating, transforming, aggregating and iterating all count; routers and error handlers don't. Make's own pricing FAQ says one run can use "two credits to thousands of credits". A scenario that pulls 300 CRM records and enriches each one uses credits for every pass through every module after the iterator. That's fine at low volume and painful once a list job runs daily.
Some AI features use more than one credit, which makes the bill harder to forecast when you add an AI step to an existing scenario.
Extra credits expire. Packs bought on a monthly plan expire after a month; on annual Pro and Teams they last until the year ends.
Complex scenarios are hard to hand over. Make's flowchart editor is its strength, until a scenario has 40 modules, three routers and a data store, and the person who built it leaves. Teams often look for something with code steps and version control at that point, or something simpler.
The Free plan includes 1,000 credits a month. We couldn't read the paid plan prices from Make's pricing page in November 2026, so compare tiers on Make's pricing page at your own monthly credit count.
Which alternative fixes which problem
| Your problem with Make | Look at | How it bills |
|---|---|---|
| Credits burn on loops and long scenarios | n8n | Per workflow run, EUR 20/mo annual for 2,500 (Nov 2026) |
| Teammates can't maintain the scenarios | Zapier | Per successful action step, from $19.99/mo annual |
| Need governance, many integrations, an API layer | Tray.ai | Tasks plus compute units, quoted, from $50/mo for Helix Builder |
| Scenarios are all enrichment, scoring and routing | Cargo | Credits, from $165/mo for 1,500 |
n8n

n8n is the closest thing to Make for people who like building, and it fixes the billing problem directly. An execution is "a single run of your entire workflow", so an iterator over 300 rows is still one execution. Cloud Starter was EUR 20 a month on annual billing for 2,500 executions and Pro EUR 50 for 10,000 (November 2026). The Community edition is free to self-host, and the paid Business license (EUR 667 a month, annual) runs on your own servers with SSO and queue mode.
The editor is a node canvas like Make's, with JavaScript and Python code nodes where Make would need a chain of modules. The catch is the learning curve and, if you self-host, the hosting: upgrades, backups and noticing when a job has stopped. n8n vs Make compares them module by module, and n8n cloud vs self-hosted covers the hosting decision. Dated plans are in our n8n pricing record.
Zapier
ZapierCount the successful tasks in the full automation.
Zapier is where teams go when Make is too much tool for the people using it. A Zap is a straight line of steps with optional Paths, it connects to more apps than Make does, and a sales ops person can build one without training. Professional was $19.99 a month on annual billing or $29.99 monthly for 750 tasks in November 2026, and Team $69 or $103.50 for 2,000.
It'll usually cost more for the same work. Zapier counts a task for each successful action step, while triggers and built-ins like Formatter, Filter and Paths are free. Overage on monthly plans bills at 2.5 times the base task rate. Moving a looping Make scenario to Zapier can multiply the count, so price your busiest scenario before you switch. Make vs Zapier has the side-by-side, and Zapier alternatives covers the other direction.
Tray.ai
- Application and API integration
- Workflow automation
- Agent building
Which features and usage are included in your exact plan?
Check product scope ↗Tray.ai is for teams whose Make account has turned into the company's integration layer. It meters Tasks: each trigger, connector step and pass through a loop counts one, and retries are free. Helix compute units cover hosted compute, storage and requests. Workspaces, log retention and security features scale by plan (Pro, Team, Enterprise), and apart from a $50 a month starting price for the Helix Builder edition, plans are quoted. Its 30-day trial includes 1 million tasks and needs no card, enough to rebuild a few real scenarios and read the meter. The trade is a sales process and an annual commitment. Workato vs Tray.ai covers the enterprise end, and Workato is the other name on that shortlist.
Cargo
CargoPublished capabilities- Repository-owned TypeScript workflows
- Production execution
- Retries
Which runtime limits, retries and provider costs are included?
Check product scope ↗A lot of Make accounts in sales teams are really enrichment pipelines: watch for a new lead, call two or three data providers, score it, write it to the CRM, notify a rep. Cargo is built for exactly that. Credits pay for enrichment provider actions, AI tokens, row storage and orchestration, at 100 workflow steps per credit, and plans start at $165 a month for 1,500 credits (monthly figure, November 2026). It isn't a general automation tool. Keep Make or a small Zapier plan for the finance and ops scenarios, and move only the GTM ones.
Moving off Make
- Export the blueprints. Make can export each scenario as a JSON blueprint. No other tool imports it, but it's the most complete record of what the scenario does, including filters and field mappings.
- Data stores. Anything kept in Make data stores has to be exported and reloaded into the new tool, a database or a sheet.
- Webhooks. Every custom webhook URL changes. List the systems that call them before you rebuild.
- Incomplete executions. Clear or resolve the queue first, or you'll lose runs that were waiting for a retry.
- Scheduling. Check how often each scenario runs, because the new tool's plan has to cover that frequency at your volume.
The wider field is in our workflow automation tools guide.
Questions buyers ask
What is the best alternative to Make?
n8n for most technical teams, because it bills per workflow run and doesn't charge for each item a loop processes. Zapier if the people maintaining automations aren't technical.
Is n8n cheaper than Make?
For scenarios that loop over many items or have many steps, yes, since n8n counts one execution per run. For short, infrequent scenarios the difference is small, and Make's 1,000 free credits a month may cover them.
Make vs Zapier: which is easier?
Zapier. Its linear Zaps are simpler to build and hand over. Make handles branching and loops better and costs less per action.
Is there a free alternative to Make?
Self-hosted n8n Community edition has no license fee; you pay for the server and the upkeep.
Can I import Make scenarios into n8n?
Not directly. Export each scenario's blueprint as a record of its logic and rebuild it in n8n, starting with the scenario that uses the most credits.