How to choose between n8n and Make
Choose between n8n and Make by writing where the automation runs, which system starts it, and who receives an exception. n8n’s docs describe a workflow as nodes connected on a canvas, and Make’s current homepage describes a platform for building automations and AI agents visually. Neither page ranks the two.
On this page
Name where it runs and who catches a failure
Write four facts for each automation: which infrastructure runs it, which system starts it, which field receives the write-back, and who receives a failure. Leave any of the four blank and you cannot yet tell which product page to read.
How a flow meets systems you already run is covered under Workflow agents. A screen robot, and an agent that pauses and writes back, are a separate question, covered in What is the difference between RPA and workflow agents. This note covers how n8n and Make connect applications.
What n8n’s docs call a workflow
The current n8n docs home describes n8n as a fair-code licensed workflow automation tool that combines AI features with business process automation. The page shows no publish date. The workflow page says a workflow is a collection of nodes connected together to automate a process, that execution starts when a trigger condition occurs, and that it then runs in sequence. That page shows no publish date.
The current code page calls n8n a low-code tool: many steps need no code, and code is added when you need it. Expressions use JavaScript. The Code node adds JavaScript or Python. The current hosting page says you can self-host on your own infrastructure, on-premises, or in a private cloud, including with Docker Compose or a one-line setup. Without a licence key, n8n runs as the free Community edition. A Business or Enterprise licence key enables those editions. The same page says npm installation is deprecated from n8n 3.0. The page shows no publish date. This note does not quote a price for any edition. The current n8n homepage also says you can deploy on your infrastructure or on n8n’s, that the source code is on GitHub, and that human approvals sit with rules to contain AI steps. That page shows no publish date. This note does not repeat the page’s star counts, ratings, or customer stories.
What Make’s current pages call a scenario
The current Make homepage describes Make as an AI automation platform: you build automated workflows and AI agents visually, connect them to the apps and data you already use, and see them running in one place. The same page says you can build by prompting, by drag-and-drop, or fine-tune with JavaScript or Python when needed. The page shows no publish date.
The same page says there is a free plan, that no credit card is required, and that the free plan has no time limit. The FAQ says the free plan includes enough credits and active scenarios to build and run automations, and the page text does not state those quantities. The page also states GDPR, SOC 2 Type II, and SOC 3, plus encryption in transit and at rest, SSO, and access controls. It also states app counts and a team count that do not match each other on the page, so this note does not quote them. Customer quotations and claims about reducing manual work are omitted as well. The Make help centre calls the automation you build a scenario. That page shows no publish date.
Where the two pages overlap
Both current pages describe a visual canvas and adding JavaScript or Python inside the flow. The overlap means both docs have those two layers. It is not a ranking.
The difference goes back to the four facts you already wrote. n8n’s hosting page documents installation on infrastructure you operate. Make’s current homepage describes visual automation on its platform and lists the compliance and access-control sentences on that page. This note did not find a separate Make page for self-hosting, so self-hosting is not written here as a difference that has already been checked. If self-hosting is an adoption condition, read n8n’s hosting page, then check the same condition in Make’s current docs, and only then put either product on the short list.
Choose from the workflow you already run
When the automation must run on infrastructure you operate, and the failure record must stay in that infrastructure’s execution history, start from n8n’s hosting page and workflow page. Write the trigger, the write-back field, and the owner of a failure beside the flow. The licence key selects the edition the docs name. The price is outside this note.
When the team will connect apps in Make’s visual scenarios, and the security review will read the compliance and access-control sentences already on the homepage, start from Make’s homepage and help centre. The scenario still names the trigger, the write-back field, and who opens the run when it fails. This note does not call either product the better one.
When to leave n8n off
Leave the flow off n8n when nobody reviews failed runs on a fixed cycle, or when you cannot name the system and the field that receive the write-back. A longer chain of nodes still leaves the failure in a queue with no owner.
When the step is only a click on a screen, and the system has no field you can write, go back to the note on workflow agents and RPA and separate the screen from the write-back. This note does not state hours saved or a return.
When to leave Make off
When a usage limit is an adoption condition, and the current page does not state the free plan’s credit count or scenario count, leave the decision off the four words “there is a free plan”. Check the quantity and the date on that page or on the plan page that follows, then write them into the record. This note does not fill in a number the page left out.
When the triggering system, the write-back field, and the owner of a failure are still unwritten, a finished scenario is not yet an automation you can accept. Write those three, then see which of the n8n or Make pages matches them. How that scope meets systems you already run is covered under Workflow agents.