The example business is Harbor Lane Bookkeeping, a made-up firm where the office manager, Priya, wants every website inquiry added to a client tracker and emailed to her.
What are the most common data mapping mistakes?
| # | Mistake | Fix |
|---|---|---|
| 1 | Words typed into a box instead of mapped | Map the box to a label from the trigger |
| 2 | A box mapped to the wrong label | Read the sample, then pick the label that holds that detail |
| 3 | Mapping before reading the sample data | Test the trigger first and read its labels and values |
| 4 | Expecting labels to match your column names | Match by meaning: Date received comes from submitted_at |
| 5 | Turning it on without a test run | Run once with the sample data |
| 6 | Checking that it ran, not what it wrote | Read the new row like a client would see it |
| 7 | Opening the tool before writing the recipe | Write "When ___, then ___ and ___" first |
Why does every row say the same thing?
1. Words typed into a box. In the lesson, the Notes box in the Add a row action starts with "Needs bookkeeping help" typed in. It looks fine on the first test. But typed words stay the same on every run, so every new client's row would get that same note, and their real message would be lost. The fix is to click the box and map it to the message label, so each inquiry fills in its own words.
The rule of thumb: if a box should be different for every run (a name, an email, a message, a date), it must be mapped. Only text that really is the same every time, like a fixed subject line, should be typed.
Why is a column blank or wrong?
2. The wrong label. A box is only as good as the label it points at. If Client name points at email, you get an email address in the name column. If it points at nothing, you get a blank. The lesson's advice: if a box comes out blank, go back and check which label you picked.
3. Mapping before reading the sample. The trigger hands over data as labels and values, like name: Maria Lopez. Every tool shows you a sample like this after you test the trigger. Read it before you map anything, so you know what each label holds.
4. Expecting labels to match your columns. Your sheet has a Date received column. The form's label for that detail is submitted_at. Labels don't always match your column names, so match by meaning, not by spelling. In the lesson, all five boxes map like this: Client name from name, Email from email, Service from service, Notes from message, Date received from submitted_at.
The field mapping entry explains the idea in a few lines. For tool-specific examples, see n8n data mapping examples and Make data mapping examples.
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 lessonWhat goes wrong at the test step?
5. No test run. Every tool lets you run the automation once with the sample data. In the lesson you click Run test with the sample before anything is turned on. A test costs you a minute. A broken automation that runs for a week costs you a week of bad rows.
6. Checking that it ran, not what it wrote. A green tick tells you the step finished. It doesn't tell you the row is right. In the lesson you click the new row and check each column: the right name, the right email, the right service, Maria's real message in the notes, and the date. Check the result like a customer would see it.
What goes wrong before you start?
7. Opening the tool before writing the recipe. The lesson's module text says people who skip the three ideas copy steps they do not understand, then can't tell why a column comes out blank. Write the automation as one sentence first: "When a new inquiry is sent from the website contact form, add a row to the client tracker spreadsheet, then email Priya." The part after "when" is the trigger. Each part after "then" is an action. For each action, list the boxes it needs and which label should fill each one.
A related slip is thinking you must relearn everything when you switch tools. You don't. n8n calls the automation a workflow made of nodes, Make calls it a scenario made of modules, and Zapier calls it a Zap made of a trigger and action steps. The ideas, and these mistakes, are the same in all three.
Key takeaways
- Map every box that should change from run to run. Typed words never change.
- Read the sample data before you map, and match labels by meaning.
- If a column is blank, check which label the box points at.
- Run one test with the sample and read the new row, column by column.
- Write the recipe as one sentence before you open any tool.
Questions about the basics are answered in the triggers, actions and data mapping FAQ. When you are ready to add AI to a workflow, read when to add AI to an automation.