Why this matters
n8n is a workflow automation tool. It connects the apps a business already uses and does the repeat work between them: when a form comes in, log it; every Monday, send the reminder; when an email lands, summarise it. Each job is drawn as a workflow on a canvas, and n8n runs it the same way every time.
In this module you help Clearview Bookkeeping, a small firm that gets new client inquiries by phone, email and sticky note and loses a few every month. You build its first workflow: an n8n form that catches every inquiry, and a step that turns the answers into a one-line summary. On the way you meet the five ideas behind every n8n workflow: triggers, nodes, items, expressions, and test runs versus publishing.
What you’ll build
A two-node workflow: On form submission (a hosted form with two questions) and Edit Fields, which writes "Dana Ortiz needs help with: Monthly bookkeeping for my design studio" from each submission.
You also see your saved runs in Executions, and the difference between the form's Test URL and its Production URL.
What you need
- Nothing to start the practiceThe editor and the form are a practice copy. Clearview Bookkeeping and Dana Ortiz are made up.
- An n8n account, to do it for realn8n Cloud has a free trial with no credit card. Sign up with this link (affiliate link: I may earn a commission, at no cost to you).
- No other apps or keysThis workflow uses only n8n's own form and Edit Fields nodes.
Concepts
3 ideas you’ll use in the practice.
Workflows, triggers and actions
A workflow is a chain of steps called nodes. The first node is a trigger: the event that starts the workflow, such as a button, a schedule, a form or a new email. Every node after it is an action that does something with the data.
n8n's own form trigger, On form submission, hosts a web form for you, so you need no form tool and no webhook.
Items and expressions
Each form submission arrives as one item with a field per question. The next node runs once for every item.
Drag a field from the INPUT panel onto a parameter and n8n writes an expression such as {{ $json.Name }}: "this item's Name". It changes with every submission.
Test runs and publishing
Execute step runs one node so you can see real data. Every run is saved under Executions.
The form has two addresses. The Test URL only listens while you test in the editor; the Production URL works around the clock once you Publish the workflow. See Test URL vs Production URL.
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.
Downloads
- n8n Beginner cheat sheet (PDF)Triggers, nodes, items, expressions and the Execute buttons on one page.
Quick check
3 questions to check you’ve got it.
1. What is the first node in every n8n workflow?
- An action
- A trigger: the event that starts it
- A credential
Show the answer
A trigger: the event that starts it. A trigger starts the workflow: a button, a schedule, a form, a webhook or an app event. Everything after it is an action.
2. A client fills in your form once. How many items does the form trigger output?
- One item, with a field per question
- One item per question
- None until you publish
Show the answer
One item, with a field per question. Each submission is one item. Each answer is a field on that item.
3. You put the Test URL on your website and nothing arrives after you close n8n. Why?
- The form is broken
- The Test URL only listens while you test in the editor; publish and use the Production URL
- Edit Fields is wrong
Show the answer
The Test URL only listens while you test in the editor; publish and use the Production URL. Test URLs listen only during a test. The Production URL works once the workflow is published.
n8n: Items, JSON and Expressions, Explained by Doing
You have built a workflow. Next, look closely at the data inside it: items, JSON and expressions, the part every beginner gets stuck on.
Start module 3 →