Make vs n8n (2026): Which Should Solo Builders Actually Use?
| Tool | Best for | Starting price | Free trial |
|---|---|---|---|
| Make (formerly Integromat) | non-technical automation, connecting CMS/publishing to AI APIs | $9/mo | Free tier, no credit card required, 1,000 ops/mo (confirmed firsthand Aug 2026) |
| n8n | research agent pipelines, publishing automation | $24/mo (cloud, after trial) | Cloud: 14-day trial, no credit card required (confirmed firsthand Aug 2026). Self-hosted Community Edition is free forever, no execution/workflow limits. |
We didn’t compare these two from spec sheets. We built the identical automation in both — watch this site’s own RSS feed, send an email when a new item appears — and documented what actually happened in each. Full writeups are in our Make review and n8n review; this is the head-to-head.
Getting to a working automation
Make required manually dragging out a trigger module, an action module, and wiring them together — intuitive, but every field (recipient, subject, body) is filled in by hand.
n8n’s AI assistant built the entire two-node workflow from one plain-English sentence. It asked one clarifying question (which email service), then constructed the trigger, the action, and the connection between them itself. For a solo builder without an automation background, this is a real difference in time-to-working- automation, not a marginal one.
What broke, and how visible the failure was
Both tools hit a real problem during setup — this is the part spec-sheet comparisons never capture.
- Make: granting only a minimal “send” OAuth scope for Gmail caused the scenario to report “completed”
with zero visible errors, while the email silently never sent. Finding the actual cause required right-
clicking the Gmail module and running it in isolation, which returned
[403] Request had insufficient authentication scopes— an error the main execution log never surfaced. - n8n: we granted broader Gmail scope upfront (a lesson carried over from the Make test), and hit no equivalent failure. More notably, before we even asked, n8n’s assistant ran a simulated verification and explicitly said so — “no real email went out during testing” — rather than presenting a simulated pass as a real one.
On this specific dimension, n8n’s tooling was more transparent about the difference between “looks done” and “actually done.”
The free-tier trap — present in both, worse in n8n
Both free tiers cap out around 1,000 operations/month, and both left the trigger on an aggressive default polling interval that we had to manually correct:
| Default interval | Free-tier exhausted in | |
|---|---|---|
| Make | Every 15 minutes | ~10 days |
| n8n | Every 1 minute | ~17 hours |
n8n’s AI-assistant-generated default was six times more aggressive than what we needed. Adjusting it in n8n was trivial — a plain-English request, applied instantly without re-verifying the already-tested workflow. Adjusting it in Make means finding the schedule setting in the trigger module manually. Neither is hard, but n8n’s default makes the correction more urgent.
Which should you use?
- Pick n8n if you want to describe an automation in plain English and have it built for you, and you’re disciplined about checking the trigger interval immediately after — or you want the option to self-host the Community Edition for free indefinitely once you outgrow the trial.
- Pick Make if you’d rather see and control every module yourself from the start, and you’re comfortable digging into isolated module tests when something silently doesn’t run.
For our own pipeline, both are staying in the stack for now — n8n for building new automations quickly from a plain description, Make for scenarios where we want to see the full wiring while we’re still learning what we actually need.