
n8n Tutorial: A Step-by-Step Beginner's Guide for 2026
Quick Summary
- •Start with n8n Cloud to learn, migrate to self-hosted for scale
- •Every workflow needs a trigger node and at least one action node
- •Test with real data before activating - the Test Step button is your friend
n8n Tutorial: A Step-by-Step Beginner's Guide for 2026
n8n is a visual workflow automation tool. You drag nodes onto a canvas, connect them, and watch data flow from one step to the next. It is open-source, self-hostable, and powerful enough to run production automations for teams of any size.
If you are new to n8n, this tutorial gets you from zero to a working workflow in under 30 minutes. No prior automation experience required. Just follow the steps.
What Is n8n?
**n8n** is an open-source workflow automation platform that connects apps and services through a visual node-based editor. Instead of writing code to move data between tools, you build workflows by dragging nodes together and configuring each step.
Each node represents an action: read an email, send a Slack message, query a database, call an API. You connect nodes with edges that define the order of execution. Data passes from node to node as JSON, and you can transform, filter, or branch that data at any point.
n8n supports over 400 integrations out of the box, plus community nodes for niche tools. It runs either in n8n's cloud or on your own server.
How to Get Started with n8n
You have two options for running n8n:
1. **n8n Cloud** — Sign up at n8n.io/cloud, get a managed instance in minutes. Best for beginners who want to focus on workflows, not infrastructure.
2. **Self-hosted** — Install n8n with Docker on your own server. Best for data privacy, unlimited executions, and internal network access.
This tutorial works with either. If you chose self-hosted, make sure your instance is running and accessible before continuing.
Building Your First Workflow

A workflow is a sequence of nodes that automate a task. Let us build one that watches for new Gmail emails and sends a Slack notification.
Step 1: Create a New Workflow
Log in to n8n. Click **Add Workflow** on the dashboard. You will see an empty canvas with a **+** button.
Step 2: Add a Trigger Node
Every workflow starts with a trigger. Click **+**, search for **Gmail**, and select **Gmail Trigger**.
Configure it:
- **Authentication:** Connect your Google account via OAuth
- **Trigger Event:** Select **Message Received**
- **Filters:** Leave empty for now (catches all emails)
Click **Test Step**. If you have unread emails, n8n will show sample data. This confirms the connection works.
Step 3: Add an Action Node
Click the **+** next to the Gmail node. Search for **Slack**, select **Send a Message**.
Configure it:
- **Authentication:** Connect your Slack workspace
- **Channel:** Pick a channel or enter one (like `#general`)
- **Text:** Enter a message. You can reference Gmail data with expressions. Try:
New email from {{ $json.from }}: {{ $json.subject }}
The `{{ }}` syntax is n8n's expression engine. `$json` refers to the data from the previous node.
Step 4: Save and Activate
Press **Ctrl+S** (or **Cmd+S**) to save. Toggle the **Active** switch in the top right. Your workflow now runs automatically whenever a new email arrives.
Test it by sending yourself an email. Check Slack for the notification.
Understanding How n8n Works
Nodes and Edges
A **node** is a single step. It either triggers the workflow (trigger node) or performs an action (action node). An **edge** is the connection between two nodes. It controls execution order and can include logic like "only run if condition X is true."
The Data Flow
Data in n8n is JSON. Each node receives an array of items from the previous node. Every item is a JSON object. You access fields with expressions like `{{ $json.fieldName }}`.
If a node returns multiple items (like multiple emails), the next node runs once for each item by default. This is called **item mapping** and it is one of n8n's most powerful features.
Expressions and Variables
Expressions let you reference and transform data dynamically. Common patterns:
- `{{ $json.id }}` — Access the `id` field from incoming data
- `{{ $now }}` — Current timestamp
- `{{ $json.amount > 100 ? "high" : "low" }}` — Ternary logic
You write expressions inside `{{ }}` brackets. n8n evaluates them at execution time.
Error Handling
Workflows fail. Nodes time out, APIs return 500s, data is missing. n8n gives you two ways to handle this:
1. **Continue On Fail** — In a node's settings, enable this to let the workflow continue even if the node errors. Use with caution.
2. **Error Workflow** — Create a separate workflow that runs when the main workflow fails. Perfect for sending alerts to Slack or logging errors.
To set up an error workflow, create a new workflow, add an **Error Trigger** node, and connect your alerting logic. Then in your main workflow's settings, set **Error Workflow** to this new workflow.
Core n8n Concepts Every Beginner Needs
Workflows vs Executions
A **workflow** is the blueprint you design on the canvas. An **execution** is one run of that blueprint. You can view all executions in the left sidebar under **Executions**. This is where you debug failures and inspect exactly what data passed through each node.
Credentials
Credentials store authentication details securely. Instead of pasting API keys into every node, you create a credential once and reuse it across workflows. n8n encrypts credentials at rest.
Webhooks
A **Webhook** node lets external systems trigger your workflow. You get a unique URL. When a service sends data to that URL, your workflow runs. This is how you connect n8n to real-time events from GitHub, Stripe, or your own applications.
Scheduling
The **Schedule Trigger** node runs workflows at fixed intervals. Use cron expressions for precise control. For example, `0 9 * * 1` runs every Monday at 9 AM. Set your time zone in n8n's settings or the workflow will run in UTC.
Three Practical Workflows to Build Next
Once you understand the basics, try these:
1. RSS to Social Media
**Trigger:** RSS Feed Trigger (new article published)
**Action:** HTTP Request to your social media scheduler, or post directly via the X/Twitter node
**Why it matters:** Automates content distribution without manual copy-paste
2. Form Submission to CRM
**Trigger:** Webhook (catches form submissions from your site)
**Actions:** Filter spam with an IF node, format data, create a lead in HubSpot or Salesforce
**Why it matters:** Instant lead capture with validation
3. Database Backup Notification
**Trigger:** Schedule Trigger (daily at 2 AM)
**Actions:** Run a database query, save results to Google Drive or S3, send a Slack confirmation
**Why it matters:** Operations automation that runs while you sleep
Common Beginner Mistakes
**Forgetting to activate the workflow**
A workflow only runs automatically if the **Active** toggle is on. Save and activate. This trips up almost every beginner.
**Hardcoding data instead of using expressions**
If you type a static email address into every node, your workflow breaks when that address changes. Use expressions to reference data dynamically.
**Not testing with real data**
The **Test Step** button shows you exactly what data a node receives and produces. Use it before activating. Guessing what the data looks like leads to broken expressions.
**Ignoring error handling**
Your workflow will fail eventually. Set up basic error handling from day one. At minimum, enable **Continue On Fail** on non-critical nodes.
**Running everything on the main thread**
Large workflows with many branches can slow down. Split independent operations into separate workflows and trigger them via the **Execute Workflow** node.
When to Move from Cloud to Self-Hosted
n8n Cloud is perfect for learning. Consider self-hosting when:
- You need more than 5,000 executions per month (cloud limits)
- You handle sensitive data that cannot leave your infrastructure
- You want to connect to internal APIs behind a firewall
- You need custom community nodes that cloud blocks
Our n8n self-hosted setup guide covers the full install process if you are ready to make the switch.
How Synta Speeds Up n8n Workflow Building
Once you know how n8n works, the bottleneck becomes building workflows fast enough. Synta is an MCP server for n8n that lets you describe workflows in plain English and generates them automatically.
Instead of dragging nodes and writing expressions manually, you tell Claude Code or Cursor what you want: "Build a workflow that watches Stripe refunds, checks if the customer is high-value, and alerts the success team in Slack." Synta creates the nodes, wires them together, and validates the logic.
It is not a replacement for understanding n8n. It is an accelerator once you know the basics. Learn n8n first, then add Synta when you want to ship workflows in minutes instead of hours.
FAQ
**Is n8n free to use?**
Yes. n8n is open-source and free to self-host. n8n Cloud offers a free tier with limited executions. Paid cloud plans start when you need more scale.
**Do I need to know how to code?**
No. n8n's visual editor handles most use cases without code. For advanced transformations, the **Code** node lets you write JavaScript or Python.
**How long does it take to learn n8n?**
You can build basic workflows within an hour. Mastery takes a few weeks of building real automations. The learning curve is shallow compared to coding the same logic from scratch.
**Can n8n replace Zapier or Make?**
For most use cases, yes. n8n offers deeper customization, self-hosting, and lower long-term costs. The trade-off is that you manage the infrastructure yourself if you self-host.
**What is the best way to learn n8n?**
Build real workflows that solve problems you have. Start simple, add complexity gradually, and use the execution log to debug. Tutorials help, but hands-on practice teaches faster.
- Synta homepage CTA
- Synta MCP docs for readers ready to accelerate workflow building
- n8n self-hosted guide internal cross-link