The example is Harbor Lane Bookkeeping, a made-up firm. Its office manager, Priya, copies every website inquiry into a spreadsheet by hand. On a busy day it does not happen at all.
How do you describe an automation before you build it?
Write it as one sentence first. The lesson's recipe reads: "When a new inquiry is sent from the website contact form, add a row to the client tracker spreadsheet, then email Priya: New inquiry from {name}."
- The part after When is the trigger.
- Each part after Then is an action.
- Anything in curly brackets, like
{name}, is a spot that gets filled in from the trigger's data on every run.
If you can't write the sentence, you are not ready to open the tool yet.
What does the trigger hand to the actions?
A small set of labels and values. In the lesson, one sample inquiry from the form looks like this (all made-up data):
| Label | Value |
|---|---|
| name | Maria Lopez |
| maria@lopezdesignstudio.example | |
| service | Monthly bookkeeping |
| message | We are a 6-person design studio and our books are 3 months behind. Can you help? |
| submitted_at | 2026-10-20 09:14 |
Every tool shows you a sample like this after you test the trigger. That sample is what you map from.
What is data mapping, in plain words?
Field mapping means pointing a box in a later step at one label from an earlier step. In the lesson, the Add a row action has five boxes, and each one points at a label:
- Client name uses name
- Email uses email
- Service uses service
- Notes uses message
- Date received uses submitted_at
A mapped box changes with every run. Maria's inquiry fills in Maria's details, and the next inquiry fills in its own.
Try it free, step by step
Automation Basics: Triggers, Actions and Data Mapping. Learn the three ideas behind every n8n workflow, Make scenario and Zap: a trigger starts it, actions do the jobs, and data mapping carries the details. Fix the classic typed-in mistake. You do every step yourself in a practice copy of Automation basics, it checks your work as you go, and “Do it for me” finishes any step you get stuck on. Free, and nothing touches your real accounts.
Start the free lessonFrequently asked questions
- What is a trigger in automation?
The event that starts the automation: a form is sent, an email arrives, or it is 8am on Monday. Nobody presses a button. In the lesson, the trigger is a new inquiry from the website contact form.
- What is an action in automation?
Every step after the trigger. Each action does one job, such as add a row, send an email or ask an AI model to write a reply. The lesson's recipe has two actions: add a row to the client tracker, then email Priya.
- Can one trigger run several actions?
Yes. The lesson's automation has one trigger and two actions, and you can add more after them. Each action can use data from the trigger.
- Why does every row in my sheet say the same thing?
Words were typed into a box instead of mapping it. In the lesson, the Notes box starts with "Needs bookkeeping help" typed in. Typed words never change, so every row would get that same note. The fix is to map the box to the message label. The mistakes guide covers this and the other usual problems.
- Why is a column blank after a test run?
Usually the box points at the wrong label, or at nothing. The lesson's advice: if a box comes out blank, go back and check which label you picked.
- Do the labels have to match my column names?
No, and they often won't. In the lesson, the Date received column is filled from a label called submitted_at, not "date". That is why you read the sample data before you map anything.
- Should I test before I turn the automation on?
Yes. Every tool lets you run the automation once with the sample data. In the lesson you click Run test with the sample, then check the new row like a customer would see it: every column has the right value, and the notes show Maria's real message.
- What do n8n, Make and Zapier call these parts?
The ideas are the same. The words differ:
Tool The whole automation The steps How you map data n8n A workflow Nodes on a canvas Drag a field from the input panel into a box, or write an expression like {{ $json.name }}Make A scenario Modules joined in a line Click a box and pick an item from the earlier module in the mapping panel Zapier A Zap A trigger, then action steps Click a field and insert data from an earlier step - What does a trigger look like in each tool?
In n8n it is a trigger node, such as a Form, Webhook or Schedule trigger. In Make it is the first module, such as Watch new responses or a Custom webhook. In Zapier it is the first step: a new form entry, a new email or a schedule. For more on n8n's trigger types, see n8n triggers explained.
- Do I need an account to take the lesson?
No. Every screen in the lesson is a plain diagram, not a real app. There is nothing to install and nothing is sent.
- Which tool should I learn first?
The lesson doesn't pick one for you, because the three ideas carry over. After it, the AI Automation courses build the same idea for real: a client inquiry form that logs itself in n8n, a Google Form to a Google Sheet in Make, or a Zap that never misses a new inquiry. The n8n vs Make vs Zapier comparison helps you choose.
- What should I do right after the lesson?
Sketch one repeat job of your own. Write it as "When ___ happens, ___ and then ___." Circle the trigger, number each action, and list the boxes each action needs and which label should fill each one. Keep the sketch for the next module.
Key takeaways
- A trigger starts the automation. Every step after it is an action.
- Data mapping points each box at a label from an earlier step, so every run fills in its own details.
- Typed words in a box never change. Map the box instead.
- Read the sample data first, because labels don't always match your column names.
- Run a test with the sample and check the result before you turn it on.
For the common slips, read triggers, actions and data mapping mistakes, print a sheet from the cheat sheets, or start the free lesson.
