🧠 This is the roadmap I wish I had when I started. No fluff. No skipping ahead to AI agents before you understand triggers. Just a structured, day-by-day path from absolute beginner to building production-ready automations that save you hours every week.
In 30 days, you will go from opening n8n for the first time to building your own AI agents, MCP servers, and full-business automation systems. Every day includes a clear goal, a practical task, and a warning about the most common mistake people make at that stage.
- A free n8n.cloud account, or Docker installed if you plan to self-host from day one.
- A Google account (for Gmail and Google Sheets exercises in Week 2).
- 45–90 minutes a day. This roadmap is built around consistency, not marathon sessions.
- Zero coding experience required for Weeks 1–2. Week 3 introduces light JavaScript inside expressions — you will be walked through it.
- An OpenAI, Google AI Studio, or free OpenRouter API key for Week 3 (needed before Day 15).
Ready? Let us begin.
Week 1: Solid Foundations (Days 1‑7)
Theme "Understand before you build. Master the basics before you fly."
Goal: Understand n8n's philosophy and why it beats Zapier and Make.
Key Concepts: n8n stands for "nodemation" — node‑based automation. Unlike Zapier (which charges per step), n8n charges per execution — a 50‑step workflow costs the same as a 5‑step workflow. You can start with drag‑and‑drop, then add JavaScript when you need more control. n8n is open‑source and can be self‑hosted for free.
Goal: Master the three main trigger types.
Key Concepts: Webhook (starts when it receives an HTTP request), Schedule (starts at a specific time), Form (starts when a built‑in form is submitted).
Goal: Understand that each node does one job, and you connect them in sequence.
Key Concepts: Node = one step in your workflow. You drag nodes from the sidebar and drop them onto the canvas. Each node has inputs and outputs. Data flows between nodes as JSON.
Goal: Understand that n8n passes data as JSON between nodes.
Key Concepts: JSON = JavaScript Object Notation. Data has fields you can map from one node to the next. Example: { "name": "Ahmed", "email": "[email protected]" }
return { json: { message: "Hello " + $json.name } }. Send a POST request with { "name": "Ahmed" } and see the response.Goal: Master using expressions to access and manipulate data.
Key Concepts: Expressions are written between {{ }}. {{ $json.field }} — access a field from the current data. {{ $node["Node Name"].json.field }} — access data from a previous node. Functions: {{ new Date() }}, {{ $json.amount * 1.15 }}
total = {{ $json.price * $json.quantity }}. Send a request with { "price": 10, "quantity": 3 } and expect total: 30.Goal: Learn how to route your workflow based on conditions.
Key Concepts: IF node checks one condition and branches into two paths (true/false). Switch node checks multiple values and branches into different paths.
{{ $json.score }} > 50, send an email. Otherwise, log the data to Google Sheets. Test both scenarios.Goal: Combine everything you learned into one integrated workflow.
Week 2: Building Real Automations (Days 8‑14)
Theme "Solve a real problem you face every week."
Goal: Automate reading, classifying, and replying to emails.
Key Concepts: Gmail Trigger node (monitors incoming mail), Gmail node (send and receive emails), combine with IF for email classification.
Goal: Read, write, and update data in Google Sheets.
Key Concepts: Google Sheets node (read, append, update, delete), map JSON data to spreadsheet columns.
Goal: Learn how to call any public API from n8n.
Key Concepts: HTTP Request node (GET, POST, PUT, DELETE), headers and authentication, handling JSON responses.
Goal: Create a Telegram bot that interacts with users.
Key Concepts: Telegram Trigger node (receives messages), Telegram node (sends messages), combine with IF for conditional replies.
/start with a welcome message and /help with a list of available commands.Goal: Read, write, and process files in n8n.
Key Concepts: Read Binary File node (reads files), Extract from File node (extracts text from PDF or Excel), Spreadsheet node (reads and writes spreadsheets).
Goal: Build systems that handle errors intelligently.
Key Concepts: Error Trigger node (catches errors from another workflow), send alerts when a workflow fails, automatic retries.
Goal: Build a workflow that combines 4+ nodes from this week.
Week 3: AI Agents & MCP (Days 15‑21)
Theme "Take a workflow you already understand and add intelligence to it."
Goal: Understand how n8n integrates with AI models.
Key Concepts: Model types (OpenAI, Anthropic, Google Gemini, local models via Ollama), AI Agent node, difference between simple automation and intelligent workflows.
Goal: Understand the AI Agent node structure and components.
Key Concepts: Memory (Window Buffer Memory, Conversation Buffer Memory), System Prompt (guides the agent's behaviour), Tools (what the agent can use — HTTP Request, Google Sheets, etc.).
Goal: Enable the agent to take real actions.
Key Concepts: Connecting tools to the agent (tool loop), tool description (what it does and what inputs it expects), executing the tool and using the result.
Goal: Run AI models locally for free.
Key Concepts: Installing Ollama, downloading a local model (e.g., llama3, mistral), connecting Ollama to n8n.
llama3.2 model. Create a workflow that uses Ollama instead of OpenAI. Test the difference in speed and cost.Goal: Build an AI system that can answer questions from your own documents.
Key Concepts: RAG = Retrieval-Augmented Generation. Indexing documents in a vector database, retrieving relevant documents and adding them to the model's context.
Goal: Understand MCP and how it connects agents to external tools.
Key Concepts: MCP = Model Context Protocol — a standard that allows agents to discover and call external tools. MCP Server (exposes tools to the agent). MCP Client (consumes tools from the server). In n8n, the MCP Server Trigger node connects to Tool nodes through ai_tool connections only — never through the regular main chain.
Goal: Build a fully integrated AI agent with memory, tools, and a local or cloud model.
Week 4: Production & Professionalism (Days 22‑30)
Theme "Turn your knowledge into real value."
Goal: Deploy n8n on your own server.
Key Concepts: Why self‑host? (full control, no execution limits). Deployment methods (Docker, npm, Railway, Oracle Cloud). Setting up Nginx and SSL.
Goal: Secure your workflows and sensitive data.
Key Concepts: Managing credentials in n8n, using environment variables, restricting access to sensitive workflows.
Goal: Track workflow performance and detect problems early.
Key Concepts: Execution log, failure alerts, OpenTelemetry integration (available in n8n v1.88+).
Goal: Create n8n templates that can be exported and shared.
Key Concepts: Exporting workflows as JSON, using customisable variables, documenting the template for others.
Goal: Build a workflow that solves a real business problem.
Goal: Make your workflows faster and more efficient.
Key Concepts: Split In Batches for batch processing, reducing API calls, caching data.
Goal: Use one workflow as a node inside another workflow.
Key Concepts: Execute Workflow node (runs a workflow from inside another workflow), Subworkflow Trigger node (receives data from a parent workflow), reusing logic across multiple projects.
Goal: Learn how to debug n8n errors effectively.
Key Concepts: Reading error messages, using the Debug node, searching the n8n community, common errors (404, timeout, 401, JSON Parse Error).
Goal: Build a complete automation system from start to finish.
Quick Summary: Weekly Map
Downloadable Starter Workflow (JSON)
This is the exact "Form to Email" pattern from Day 7, built as a ready-to-import n8n workflow. It receives a webhook, checks a score field, and routes to two different response messages. Import it, study how the nodes connect, then rebuild it yourself from scratch — that second step is what actually makes it stick.
{
"name": "Day 7 - Form to Email Starter",
"active": false,
"nodes": [
{
"parameters": {
"httpMethod": "POST",
"path": "day7-starter-YOUR_UNIQUE_PATH_HERE",
"responseMode": "responseNode",
"options": {}
},
"id": "1a1a1a1a-0001-0001-0001-000000000001",
"name": "Webhook",
"type": "n8n-nodes-base.webhook",
"typeVersion": 2,
"position": [240, 300]
},
{
"parameters": {
"conditions": {
"options": {
"caseSensitive": true,
"leftValue": "",
"typeValidation": "strict"
},
"conditions": [
{
"id": "c1c1c1c1-0001-0001-0001-000000000001",
"leftValue": "={{ $json.body.score }}",
"rightValue": 50,
"operator": {
"type": "number",
"operation": "gt"
}
}
],
"combinator": "and"
},
"options": {}
},
"id": "2b2b2b2b-0002-0002-0002-000000000002",
"name": "IF Score Check",
"type": "n8n-nodes-base.if",
"typeVersion": 2,
"position": [460, 300]
},
{
"parameters": {
"assignments": {
"assignments": [
{
"id": "d1d1d1d1-0003-0003-0003-000000000003",
"name": "message",
"type": "string",
"value": "=Thanks {{ $json.body.name }}, you qualified! Our team will reach out within 24 hours."
}
]
},
"options": {}
},
"id": "3c3c3c3c-0003-0003-0003-000000000003",
"name": "Set Qualified Message",
"type": "n8n-nodes-base.set",
"typeVersion": 3,
"position": [680, 200]
},
{
"parameters": {
"assignments": {
"assignments": [
{
"id": "e1e1e1e1-0004-0004-0004-000000000004",
"name": "message",
"type": "string",
"value": "=Thanks {{ $json.body.name }}, we've received your submission and will follow up soon."
}
]
},
"options": {}
},
"id": "4d4d4d4d-0004-0004-0004-000000000004",
"name": "Set Default Message",
"type": "n8n-nodes-base.set",
"typeVersion": 3,
"position": [680, 400]
},
{
"parameters": {
"respondWith": "json",
"responseBody": "={{ { \"message\": $json.message } }}",
"options": {}
},
"id": "5e5e5e5e-0005-0005-0005-000000000005",
"name": "Respond to Webhook",
"type": "n8n-nodes-base.respondToWebhook",
"typeVersion": 1.1,
"position": [900, 300]
},
{
"parameters": {
"content": "## Setup Instructions\n1. Activate this workflow after importing.\n2. Open the Webhook node and copy the Production URL.\n3. Send a POST request with body: { \"name\": \"Ahmed\", \"score\": 65 }\n4. Replace YOUR_UNIQUE_PATH_HERE in the Webhook node with your own path before activating.",
"height": 220,
"width": 320
},
"id": "6f6f6f6f-0006-0006-0006-000000000006",
"name": "Sticky Note",
"type": "n8n-nodes-base.stickyNote",
"typeVersion": 1,
"position": [240, 60]
}
],
"connections": {
"Webhook": {
"main": [
[
{ "node": "IF Score Check", "type": "main", "index": 0 }
]
]
},
"IF Score Check": {
"main": [
[
{ "node": "Set Qualified Message", "type": "main", "index": 0 }
],
[
{ "node": "Set Default Message", "type": "main", "index": 0 }
]
]
},
"Set Qualified Message": {
"main": [
[
{ "node": "Respond to Webhook", "type": "main", "index": 0 }
]
]
},
"Set Default Message": {
"main": [
[
{ "node": "Respond to Webhook", "type": "main", "index": 0 }
]
]
}
}
}4 Things to Skip This Month
Skipping these on purpose will save you more time than any tutorial will:
- Custom Code nodes before Week 3. Almost everything in Weeks 1‑2 can be done without a single line of JavaScript. Reach for Code only when Set and IF genuinely cannot do the job.
- Self-hosting before Day 22. Use n8n Cloud's free tier for the first three weeks. Learning Docker, Nginx, and SSL at the same time as JSON and triggers is how people quit in Week 1.
- Building an AI agent from a blank canvas. Start from the template in Week 3, understand every node in it, then modify it. Building agents from scratch on Day 15 is the single fastest way to burn a weekend on a workflow that never runs.
- Connecting 10 tools in your first workflow. Pick two or three services you actually use every week. A working 2-tool automation beats a broken 10-tool one every time.
Printable 30-Day Progress Checklist
Check items off as you complete them. This box does not save your progress between visits — screenshot it, print it, or copy it into your own notes app to track it properly.
Week 1 — Foundations
- Day 1 — n8n account set up, interface explored
- Day 2 — Built 3 workflows, one per trigger type
- Day 3 — Explored 5 core nodes
- Day 4 — Extracted a field with a Code node
- Day 5 — Built a calculated field with Set + expressions
- Day 6 — Built an IF-branching workflow
- Day 7 — Shipped your first end-to-end real workflow
Week 2 — Real Automations
- Day 8 — Gmail classify + auto-reply workflow
- Day 9 — Google Sheets read/process/write workflow
- Day 10 — Public API call with error handling
- Day 11 — Telegram bot with /start and /help
- Day 12 — CSV file read and processed
- Day 13 — Error Trigger + alert workflow built
- Day 14 — Shipped an integrated multi-node project
Week 3 — AI Agents & MCP
- Day 15 — First AI Agent node test
- Day 16 — Agent with memory and system prompt
- Day 17 — Agent using a real tool
- Day 18 — Local model running via Ollama
- Day 19 — Basic RAG workflow built
- Day 20 — MCP concept understood
- Day 21 — Shipped a full AI agent with tools + memory
Week 4 — Production & Professionalism
- Day 22 — n8n self-hosted on a VPS
- Day 23 — Credentials secured, no hard-coded keys
- Day 24 — Monitoring + failure alerts set up
- Day 25 — First reusable template exported
- Day 26 — Business automation built end-to-end
- Day 27 — Batch processing optimisation tested
- Day 28 — Sub-workflow built and reused
- Day 29 — Deliberately broke and fixed a workflow
- Day 30 — Capstone project completed 🎉
Frequently Asked Questions
No. n8n is a visual drag‑and‑drop platform. This roadmap starts from absolute zero and gradually introduces concepts. JavaScript is optional and only introduced when you are ready.
Almost nothing. n8n.cloud has a free tier with 2,500 executions per month. For more, you can self‑host on a $5 VPS. API keys like OpenAI cost pennies per thousand calls.
That is normal. Every day builds on the previous one, but you can always go back. If you feel frustrated, take a break and return to the day you left off. Consistency matters more than speed.
Yes, but I do not recommend it. Each day builds a foundation for the next. If a day feels easy, you can move faster. If it feels hard, take extra time.
Understanding how data flows between nodes as JSON. Once you master this, everything else becomes intuitive. Spend extra time on Day 4 and Day 5.
n8n community forum (community.n8n.io), n8n Discord, Reddit r/n8n, and the TriggerWorkflow Fixed Error Hub for common error fixes.
You can adapt any project to your own context. The goal is not to copy‑paste — it is to understand the pattern so you can build your own solutions. Think of a repetitive task you do weekly and build that.
Plan 45‑90 minutes per day. Some days are shorter (concept‑heavy), some are longer (building‑heavy). The most important thing is to show up every day.
→ How to Build an AI Agent with n8n (2026 Guide)
→ n8n MCP Server: Connect Your AI Agent to Any Tool
→ Build an AI Content Factory with n8n, DeepSeek & Gemini
→ Workflow Execution Failed – Complete Guide
→ Automate Invoice Processing & Reminders
→ Fix Check URL Node & Execution Timeout
Your 30‑Day Journey Starts Today
You now have a complete roadmap — daily goals, practical tasks, a downloadable starter template, and a checklist to track it all. Start with Day 1. Build something simple tonight. By Day 30, you will have built skills that most people take years to develop.
The only way to become an n8n hero is to start. So start today. 🚀