Updated . Built from n8n's and Make's official docs and help center. Screens may differ slightly in your account. How we check this lesson
You know what you want to automate, and now everyone has an opinion on n8n or Make. Both connect your apps without code and both can add an AI step, so feature lists don't settle it. In this free beginner module you play Theo, operations manager at Bluefin Creative, a made-up 15-person marketing agency, with one real workflow: every new client brief goes into a project sheet, AI writes a one-line summary and the account lead gets an email. You answer four questions (who builds it, where it runs, how many steps and runs, how you test), see how n8n and Make each count and test that workflow according to their own docs, and pick one. 8 steps, about seven minutes, no account needed. There are no prices here on purpose: they change, so check each pricing page with your own numbers.
At a glance
| Question | Answer |
|---|---|
| What you build | Stop reading feature lists. Answer four questions about your team (who builds it, where it runs, how many steps and runs, how you test), see how n8n and Make each count the same workflow from their own docs, and pick one with a reason you can explain. |
| Tools | Automation basics |
| Time | About 7 minutes, 8 steps in 4 parts |
| Level | Beginner, no coding needed |
| Cost | Free |
| Ways to learn it | Practice it step by step |
The 4 parts, in short
- The job: Start from the job, not the tool.
- Four questions: Who builds and fixes it?, Where must it run?, How many runs a day?.
- How each counts: See how each tool counts it, Check how you test in each.
- Pick one: Open the rule of thumb, Save the pick, then do it for your own workflow.
Part of: Intro to AI Automation (step 6 of 6)
Part of: Make Jump Start (step 2 of 8)
Part of: n8n for Beginners: Your First Automations (step 2 of 12). Next up: n8n: What Is n8n? Build Your First Workflow
The business case: picking from a feature list costs a rebuild
Picture Theo, operations manager at Bluefin Creative, a made-up marketing agency. His first workflow has eight steps: a new brief arrives from the website form, the client is looked up in the project sheet, the brief is added as a row, AI writes a one-line summary, a rule checks the deadline, the account lead gets an email, the team chat gets the summary and the summary is saved back to the row. About 40 briefs arrive a day. These are example numbers; replace them with your own.
Teams that pick a tool from a comparison table often find out months later that the bill grows with every step they add, or that the only person who can fix it has left. Four questions about your own team and your own workflow settle it faster, and give you a reason you can explain to whoever signs off.
Who this is for, and what you need
Office managers, operations staff and small-business owners choosing a first automation tool after a beginner course such as Intro to AI Automation. Not sure what to automate yet? Do Pick the Right Job and Test It first. No account is needed; the practice is a decision worksheet. For prices and plan details side by side, the n8n vs Make comparison has them with the date they were checked.
The four questions, and what the docs say
- Who builds and fixes it? Both tools work without code and both run in the vendor's cloud with nothing to install (n8n Cloud and Make). n8n's docs say self-hosting needs setup (npm, Docker or a server), technical skill for installation and configuration, and your own maintenance.
- Where must it run? If data can live in a cloud service, both are fine. If it must stay on your own servers and someone can maintain one, self-hosted n8n is the option of the two.
- How many steps and runs? n8n's pricing FAQ says an execution is a single run of your entire workflow, and the number of steps or the amount of data doesn't change it. Make's help says an operation is a single module run, each item a module processes is its own run, and operations consume credits. So one eight-step run is 1 execution in n8n and about 8 operations in Make.
- How do you test it? n8n has Execute workflow (whole workflow), Execute step (one node) and Publish to make it run on its own. Make has Run once for a test run and a schedule (At regular intervals, Daily, Weekly and others) to switch it on; On demand only runs when started.
The rule of thumb
Pick n8n Cloud when workflows are long and run often, when AI agents and multi-step AI work are next on your list, or when you may need to self-host later for data reasons. Pick Make when your scenarios are short and run a few times a day, your team likes a visual drag-and-drop builder, and the jobs are simple app-to-app moves. For Bluefin (eight steps, 40 runs a day, office staff, cloud is fine) that points to n8n Cloud. A team with three-step scenarios that run five times a day would be well served by Make, and the counting difference would hardly matter.
Disclosure: Stepthrough has an affiliate relationship with n8n, so it may earn a commission if you sign up through an n8n link elsewhere on Stepthrough, at no cost to you. There is no affiliate link on this page, and the rule of thumb above is the same one the free n8n and Make courses use.
What this saves you
- A week of trials in two tools, and a rebuild when the first one turns out to be the wrong fit.
- A surprise bill: you know how each tool counts your own workflow before you buy.
- What it does not do: it does not compare prices, which change. Put your own steps and runs a day into each pricing page.
How this lesson was built
The practice is a plain decision worksheet, not n8n's or Make's screens. How each tool counts and tests a workflow comes from n8n's documentation (Choose your n8n; Manual, partial, and production executions), n8n's pricing FAQ and Make's help center (Operations; Schedule a scenario), read on 13 November 2026. Bluefin Creative and its numbers are made up.
Links
- n8n docs: Choose your n8n: n8n Cloud versus self-hosted, and what self-hosting asks of you (setup, technical skill, maintenance).
- n8n pricing FAQ: what an execution is: one run of your entire workflow, however many steps it has. Check current prices here.
- n8n docs: Manual, partial, and production executions: Execute workflow, Execute step and Publish.
- Make help: Operations: an operation is a single module run, and the credits those operations consume.
- Make help: Schedule a scenario: Run once, On demand and the schedule options.
Try it yourself, free
Reading the steps is a start. Doing them is how it sticks. The interactive module walks you through every click in a practice copy of Automation basics, checks each step, and never touches your real accounts.
Start “n8n vs Make: Pick the Right Automation Tool for Your Team in 10 Minutes”Step by step: n8n vs Make: Pick the Right Automation Tool for Your Team in 10 Minutes
All 8 steps of the interactive module, in order. In the module you watch each one, then do it yourself in a practice copy that checks your work.
1. The job
- Start from the job, not the tool. You are Theo, operations manager at Bluefin Creative, a made-up marketing agency. This is the one workflow you want first: eight steps, about 40 runs a day. Pick the tool for this job, not for a feature list. Click Answer the four questions.
You are Theo, operations manager at Bluefin Creative. This is the workflow you want first: eight steps, about forty runs a day. Pick the tool for this job, not for a feature list.
2. Four questions
- Who builds and fixes it?. Nobody at Bluefin is a developer, and there is no IT team. Click 1. Who builds and fixes it? Office staff, no IT help and read what the docs say.
Nobody at Bluefin is a developer, and there is no IT team.
- Where must it run?. Bluefin's client briefs can live in a cloud service, so there is no reason to run a server. Click 2. Where must it run? The cloud is fine.
Bluefin's client briefs can live in a cloud service, so there is no reason to run a server.
- How many runs a day?. Each new brief starts one run of the eight-step workflow. In 3. How many runs a day?, type 40.
Each new brief starts one run of the eight-step workflow.
3. How each counts
- See how each tool counts it. Click See how each tool counts it. This is the biggest difference for a long workflow: n8n's pricing FAQ says an execution is one run of the entire workflow, whatever the number of steps. Make's help says an operation is a single module run.
n8n counts one execution per run of the whole workflow. Make counts an operation for each module that runs.
- Check how you test in each. Both let you test before anything runs on its own. Click And how do I test it? n8n's docs name Execute workflow, Execute step and Publish; Make's name Run once and the schedule options.
Both let you test before anything runs on its own. n8n has Execute workflow and Publish. Make has Run once and a schedule.
4. Pick one
- Open the rule of thumb. Now decide. In the left menu, click Pick one.
Now decide.
- Save the pick, then do it for your own workflow. Long workflow, 40 runs a day, office staff, cloud is fine: n8n Cloud is picked for Bluefin. Click Save the decision. A team with short scenarios that loves a visual builder would pick Make, and that is a good answer too. Then write down your own steps and runs a day, check both pricing pages, and start the free course for your pick.
Long workflow, forty runs a day, office staff, cloud is fine. n8n Cloud is picked for Bluefin. Then do the same for your own workflow, and start the course for your pick.
Frequently asked questions
- Should I use n8n or Make?
- Pick by your team and your workflow, not by feature lists. If the people building it are office staff and the cloud is fine, both work. For long workflows that run often, n8n Cloud usually counts less, because it counts one execution per run however many steps it has. For short, simple scenarios and a team that likes a visual builder, Make is a good fit.
- How does n8n count usage compared with Make?
- n8n's pricing FAQ says an execution is a single run of your entire workflow, regardless of steps or data. Make's help says an operation is a single module run, and operations consume credits. An eight-step workflow run once is 1 execution in n8n and about 8 operations in Make.
- Do I need to self-host n8n?
- No. n8n Cloud is fully managed by n8n with nothing to install. n8n's docs say self-hosting needs setup with npm, Docker or a server, technical skill and your own maintenance, so it suits teams with infrastructure and technical resources.
- Which is easier to test, n8n or Make?
- Both let you test before anything runs on its own. In n8n you click Execute workflow (or Execute step for one node) and Publish when it works. In Make you click Run once and then set a schedule.
Terms in this lesson
Plain-English definitions, each with an example from a free lesson.