Why this matters
A new client fills in the contact form on your website. Someone copies the name, email and message into a spreadsheet, then emails the person who handles new clients. It takes five minutes, and on a busy day it does not happen at all.
n8n, Make and Zapier all fix this the same way, and they all rest on three ideas: a trigger starts the automation, actions do one job each, and data mapping carries the details from one step to the next. People who skip these ideas copy steps they do not understand, then cannot tell why a column comes out blank or why every row says the same thing.
This short module teaches the three ideas on plain diagrams, before you open any tool. After it, every n8n workflow, Make scenario and Zap you build will make sense.
What you’ll build
You read the recipe behind a new client inquiry automation for Harbor Lane Bookkeeping (made up): one trigger and two actions. Then you map five fields from the form data into an "Add a row" action, fix a box that has words typed into it, run a test and check the new row.
Last, a cheat sheet shows what n8n, Make and Zapier call each part, so the words in the next module are already familiar.
What you need
- NothingEvery screen is a plain diagram, not a real app. No account, nothing to install, nothing is sent.
- A repeat job of your own, if you likeThink of one task you copy from one app to another by hand. You will sketch its trigger and actions at the end.
Concepts
3 ideas you’ll use in the practice.
A trigger starts it, actions do the work
The trigger is the event that starts an automation: a form is sent, an email arrives, it is 8am on Monday. Nobody presses anything. Every step after it is an action: add a row, send an email, ask an AI model to write a reply.
Write any automation as one sentence first: "When a new inquiry comes in, add a row to the tracker and email Priya." The part after "when" is the trigger. Each part after "then" is an action.
Data mapping carries the details
The trigger hands over data as labels and values, like name: Maria Lopez. Field mapping means pointing a box in a later step at one of those labels, so every run fills in its own details.
The classic mistake is typing words into a box instead of mapping it. Typed words never change, so every row says the same thing. The other is picking the wrong label, which is why you read the sample data first.
Same idea, three names
In n8n the automation is a workflow made of nodes. In Make it is a scenario made of modules. In Zapier it is a Zap made of a trigger and action steps. Learn the ideas once and the second tool is much faster. To pick one, see n8n vs Make vs Zapier for AI automation.
Practice
Do every step yourself in a practice copy of the real tool. It checks your work, and “Do it for me” finishes any step you get stuck on.
Do it for real
Now repeat it in your own account. Tick each step as you go.
Quick check
3 questions to check you’ve got it.
1. What is the trigger in an automation?
- The event that starts it, like a new form entry
- The last step
- The person who approves it
Show the answer
The event that starts it, like a new form entry. The trigger is the "when" part. Every step after it is an action.
2. Every new row in the tracker has the same note, "Needs bookkeeping help". What went wrong?
- The trigger is broken
- Words were typed into the Notes box instead of mapping the message label
- The sheet is full
Show the answer
Words were typed into the Notes box instead of mapping the message label. Typed words stay the same on every run. A mapped box fills in each inquiry’s own message.
3. What does Make call a whole automation?
- A Zap
- A workflow
- A scenario
Show the answer
A scenario. Make calls it a scenario, n8n a workflow and Zapier a Zap. The ideas are the same.
Your First Make Scenario: Google Form to Google Sheets
You know the three ideas. Next, build them in Make: your first scenario, from a Google Form to a Google Sheet.
Start module 3 →