n8n vs Zapier vs Make: what actually matters once you're past ten workflows

Under ten workflows, any of the three tools works fine, and the pricing-and-integrations comparison posts you've read are accurate enough. Past ten workflows, the question stops being "which has more integrations" and becomes "can I debug this at 11pm without opening a support ticket."

Zapier's linear model is the easiest to reason about and the hardest to scale: branching logic gets awkward fast, and version history is thin. Make's visual canvas handles branching well but the scenario view becomes unreadable past a certain complexity, especially for anyone who didn't build it.

n8n wins on one thing that rarely makes the comparison charts: self-hosting means your workflow logic and data never leave infrastructure you control, and you can inspect every execution's raw JSON when something goes wrong, which, eventually, it will.

My honest rule: Zapier for a solo operator's first ten workflows, n8n the moment more than one person needs to maintain them, Make when the client already has a team fluent in its visual style. The tool matters less than whether someone can read the workflow a year from now.