Reading about n8n only takes you so far. It really clicks the moment you build something yourself, even if it’s small. This tutorial walks through putting together a genuinely useful first workflow - one that runs on a schedule, pulls data from a spreadsheet, and sends a message summarizing it.
We’ll go through it step by step, exactly as you’d click through it in the n8n editor, so you can follow along on your own screen.
What We’re Building
A workflow that runs automatically every weekday morning, checks a Google Sheet for new rows added since the last run, and sends a summary to Slack (or email, whichever you’d rather use). This mirrors a real use case - daily lead summaries, inventory checks, task reminders - rather than a made-up toy example.
Step 1: Create a New Workflow
From the n8n dashboard, click “Add Workflow” to open a blank canvas. Name it something clear right away - “Daily Sheet Summary” works fine - because workflows pile up fast once you’re comfortable, and vague names get confusing within a week.
Step 2: Add the Schedule Trigger
Click the plus icon on the canvas and search for “Schedule Trigger.” This node starts your workflow automatically at a time you set, with nobody clicking anything. Set it to run once per day, on weekdays, at whatever time makes sense - 9:00 AM, say. This is the first node on your canvas; every workflow needs exactly one starting point like it.
Step 3: Connect the Google Sheets Node
Add a Google Sheets node and connect it to the output of the Schedule Trigger by dragging a line between them. Set it to “read” from your target spreadsheet and sheet tab. Authenticate your Google account through n8n’s guided connection flow the first time - after that it’s saved as a reusable credential.
Worth pausing here to click “execute node” and test just this one step by itself. n8n shows you the actual data that came back in a panel below the canvas, and getting into the habit of testing each node before chaining the next one on will save you a lot of confusion later.
Step 4: Filter for New Rows
Depending on how your sheet is set up, you might want a Filter node here so only unprocessed rows pass through - rows where a “Notified” column is still empty, for instance. Otherwise your summary message just repeats the same old data every day.
Step 5: Format the Data
Add an “Edit Fields” (Set) node to shape the data into something readable. This is where you’ll write your first expressions - small snippets like {{ $json.name }} that pull a specific value out of whatever the previous node returned. Build a plain text summary: something like “3 new entries today: [names].”
Step 6: Send the Notification
Add a Slack node (or an Email/Gmail node, your call) and connect it after the formatting step. Drop your formatted summary text into the message field using the expression from the previous node. Set the destination channel or email address, then test the whole chain end to end with “execute workflow” from the Schedule Trigger.
Step 7: Activate the Workflow
Once the test run looks right, flip the “Active” toggle in the top right of the editor. From here on, the workflow runs on its own schedule with no manual involvement at all.
| Step | Node | Purpose |
|---|---|---|
| 1 | Schedule Trigger | Starts the workflow automatically |
| 2 | Google Sheets | Reads current data |
| 3 | Filter | Keeps only new/unprocessed rows |
| 4 | Edit Fields | Formats data into a readable summary |
| 5 | Slack/Email | Delivers the notification |
Common First-Timer Mistakes
- Skipping node-by-node testing: Building all five nodes before testing any of them makes it much harder to find where something broke.
- Forgetting to activate: A perfectly built workflow does nothing until the Active toggle is switched on.
- Ignoring the data panel: New users often guess at field names instead of checking the actual JSON output sitting right below the canvas.
Where to Go From Here
Once this pattern feels natural, try swapping the destination - send to a database instead of Slack, or trigger from a webhook instead of a schedule. Need to connect to a service without a dedicated node? Our guide to the HTTP Request node covers exactly how.
Key Takeaways
- Every n8n workflow starts with a single trigger node - here, a Schedule Trigger.
- Test each node on its own before connecting the next one; it makes debugging much easier later.
- Expressions such as
{{ $json.fieldName }}pull data from earlier nodes into later ones. - A workflow sits idle until you switch it to “Active” - nothing runs before that.
- This trigger, read, filter, format, notify pattern shows up across dozens of real business use cases.
Want to build this alongside a live instructor instead of solo? Join a free n8n demo or enroll in full n8n training to go well beyond your first workflow.