n8n Tutorial 2026: Build Your First Automation Workflow in 10 Minutes

n8n is a fair-code, node-based workflow automation platform pronounced “n-eight-n” that lets you connect 400+ apps and services through a visual drag-and-drop canvas. It combines no-code speed with full-code extensibility via native JavaScript, custom node SDKs, and self-hosted deployment. In 2026, n8n added an AI Workflow Builder (text-to-workflow), a built-in AI Agent builder, and MCP (Model Context Protocol) support for connecting LLMs to external tools.

Automation is not about replacing people. It is about removing the boring handoffs so humans can do the work that actually needs judgment. n8n is the bridge.

Below is a workflow you can build in 10 minutes: when you star an email in Gmail, n8n filters it, creates a task in your task management tool, and sends a Slack notification. This covers the universal automation pattern: trigger + condition + action + notification.

Why n8n Over Zapier and Make in 2026

Before building, understand what differentiates these three platforms as of mid-2026.

Feature	n8n	Zapier	Make.com
Pricing	Free self-hosted or paid Cloud	Free + tiered paid plans	Free + tiered paid plans
Self-hosting	Full Docker/Kubernetes support	Not supported	Not supported
Custom code	Native JavaScript + Node SDK	Limited Code steps	Limited Code steps
AI tools	Native OpenAI, Anthropic, Gemini, MCP	Limited third-party zaps	Limited native AI options
Integrations	400+ modular, open-source nodes	7,000+ apps	2,000+ apps
Version control	Git-compatible workflows	Not supported	Not supported
AI Workflow Builder	Text-to-workflow generator	Not available	Not available
AI Agent builder	Built-in canvas-based agent design	Not available	Not available
Best for	Developers, hybrid teams, regulated industries	Non-technical users, simple zaps	Visual automation enthusiasts

n8n’s edge in 2026: automation as a first-class development concern. Write JavaScript in Function nodes, version workflows with Git, deploy behind a firewall, and orchestrate AI agents on the same canvas. Zapier and Make are simpler for basic zaps; n8n scales into complex, logic-heavy systems without plan limits.

n8n has surpassed 40,000 GitHub stars and maintains an active community with thousands of shared workflow templates.

What You Need Before Starting

An n8n instance either n8n Cloud (fastest, no setup) or self-hosted via Docker (docker run -it --rm --name n8n -p 5678:5678 n8nio/n8n)
A Gmail account with access to starred emails
A Slack workspace where you can post messages
A task management tool (Todoist, Asana, Notion, ClickUp, or Linear all have native n8n nodes in 2026)

Use n8n Cloud for the fastest start. Self-host when data residency compliance (HIPAA, GDPR, SOC 2) or infrastructure control is required.

Step 1: Create a New Workflow

Open n8n and click New Workflow. A blank canvas appears with a single ”+” node. Data flows left to right through connected nodes.

Step 2: Add Your Trigger Node

Every workflow starts with a trigger node the node that determines when the workflow runs. No trigger, no execution.

Click the ”+” on the canvas
Search for Gmail and select it
Authenticate via OAuth2 (n8n encrypts credentials at rest in a dedicated credentials vault)
Select the trigger type: Email Labeled Trigger (also called “Message Trigger” in newer n8n versions)
Set the label filter to “Starred”

This fires whenever you star an email. In production, use dedicated labels like “n8n-process” to avoid noise. Click Execute Node to test output JSON appears in the right panel.

Step 3: Add a Filter with the IF Node

Before creating tasks, add conditional logic so only relevant emails trigger downstream actions.

Click the ”+” on the connector line after the Gmail node
Search for IF and add it
Configure the condition: Subject contains [your trigger keyword] for example, “task” or “action”
The IF node splits output into true and false branches

The IF node splits data into true (continue) and false (end silently via a NoOp node) branches. Test with both matching and non-matching emails before wiring downstream nodes.

Step 4: Create a Task in Your Task Tool

Wire the true output of the IF node to your task management action.

Click ”+” on the true branch
Search for your task tool ClickUp, Notion, Todoist, Linear, or Asana
Authenticate and select Create Task
Map fields using expressions (JavaScript inside {{ }}):
- Title: {{ $json.subject }}
- Description: From: {{ $json.from }} {{ $json.date }}

Click Execute Node to verify the task appears in your tool.

Step 5: Send a Slack Notification

Add a notification node so you know the automation ran.

Click ”+” after the task node, search for Slack, authenticate via OAuth2
Select Send Message, set the channel (#alerts or your DM), and compose:
- Message Text: Task created from email: {{ $json.subject }} | {{ $now.format('yyyy-MM-dd') }}

Step 6: Connect and Activate

Connect nodes by dragging output ports (right side) to input ports (left side). Final structure:

Gmail Trigger → IF Node → [true] → Create Task → Slack Notification
                         → [false] → NoOp

Toggle the Active switch. Star a matching email in Gmail. Within 5–15 seconds, check Execution History for a successful run, verify the task, and confirm the Slack notification.

If it does not fire, the execution log is your source of truth. Most failures come from:

Wrong field name in an expression verify output JSON matches your reference
Credential lacks permissions re-authenticate with the correct OAuth scope
IF condition does not match check the actual subject against your filter

Key n8n Concepts

Workflow: A connected graph of nodes on the canvas.
Node: One step trigger, action, or logic.
Trigger: The node that starts execution. Event-based (Gmail), schedule-based (Cron), or manual.
Credential: Encrypted auth data (API key, OAuth token) stored in n8n’s vault.
Expression: JavaScript inside {{ }} that references and transforms data from previous nodes.
Execution: One complete run from trigger to final node.
Canvas: The visual drag-and-drop editor.

Essential Nodes Beyond Basics

HTTP Request Connect to any REST API without a native node.
Set Add, modify, or remove JSON fields mid-flow.
Switch Route data down multiple branches (more powerful than IF for 3+ outcomes).
Merge Combine two parallel branches into one stream.
Cron (Schedule Trigger) Run at intervals (hourly, daily 9 AM, custom cron).
Code Write JavaScript or Python for custom logic and direct API calls.
Wait Pause execution for a set duration or until a specific timestamp.

These seven nodes appear in roughly 90% of production workflows above basic complexity.

Production Safety Checklist

Before relying on any workflow in a real business context, run through this checklist:

Test each node individually using Execute Node not Execute Workflow to catch errors at the node level
Confirm all credentials are valid and have the minimum necessary permissions (principle of least privilege)
Verify every expression pulls correct fields by inspecting the JSON output panel
Run the workflow with a normal input (happy path) and an edge-case input (subject without keyword, empty body, etc.)
Check that duplicate protection exists does re-running on the same email create a second task?
Review execution logs for warnings or partial failures
Add an Error Trigger node on critical workflows that sends an alert (Slack, email) when something breaks
Name every node clearly and add a Sticky Note on the canvas describing the workflow’s purpose and owner

Automations are not set-and-forget. They are small, living systems that need owners, monitoring, and periodic review. Schedule a monthly 5-minute check on active workflows.

Cloud vs. Self-Hosted

Factor	n8n Cloud	Self-Hosted
Setup	Minutes	30–90 min (Docker/K8s)
Maintenance	Managed by n8n	Your responsibility
Data privacy	EU/US hosted	Full on-prem, VPC, air-gapped
Custom plugins	Public nodes only	Private plugins supported
Cost	Free tier → paid	Server costs only (~$5/mo)
Compliance	Standard	HIPAA, GDPR, SOC 2 configurable
Best for	Beginners, MVPs	Regulated, high-volume, enterprise

Start with Cloud. Migrate to self-hosted when data residency or cost at scale matters.

Three Workflow Variations

Support Triage: Gmail → IF keywords “billing”/“login failed” → Linear ticket → Slack alert with OpenAI summary.
Lead Capture: Form email → parse sender + company → Clearbit enrichment → HubSpot CRM → Slack DM to sales.
Invoice Processor: Email with PDF → save to Google Drive → AWS Textract extraction → Asana finance task → #finance notification.

All three follow the same trigger + condition + action + notification pattern.

The 2026 n8n Learning Path

According to the March 2026 Towards AI guide and community consensus:

Workflows first, AI second. Learn triggers, actions, and IF logic before touching AI nodes. McKinsey: 50% of work activities can be automated without AI. Standard workflow automation alone delivers 30%–200% year-one ROI.
Master JSON and APIs. All n8n data is JSON. Understanding key-value pairs and reading API docs unlocks the platform.
Learn core nodes deeply. IF, Switch, Merge, Set, HTTP Request, Code, and Schedule Trigger solve 90% of problems.
Add AI incrementally. Start with OpenAI Summarization at the end of a workflow, then sentiment analysis, then full AI Agent workflows.
Build MVPs. Prototype 2–3 nodes, validate, expand. Debugging a 15-node monolith is exponentially harder.

FAQ

How fast do workflows execute? Simple 3–5 node workflows complete in under 10 seconds. LLM-calling workflows (OpenAI, Anthropic) take 15–30 seconds depending on token generation.

What if an app like Slack is down? The workflow fails gracefully at that node. n8n logs the HTTP error code. Use an Error Trigger node for alerts. Cloud plans include auto-retry.

Can I run this on a schedule instead of an email trigger? Yes. Swap the Gmail Trigger for a Schedule Trigger (Cron). Use 0 9 * * 1-5 for weekdays at 9 AM.

How do I monitor long-term? Execution history shows per-node I/O. For production, enable log streaming to external stacks like Grafana or Datadog.

Can I share workflows with my team? Cloud Pro/Enterprise includes role-based sharing. Self-hosted Enterprise supports Git-based version control with push/pull across dev, staging, and production.

Is n8n free? Cloud has a free tier with limited executions. Self-hosting is free and unlimited you pay only for the server. Licensed under sustainable use (fair-code).

N8N Tutorial Build Your First Automation Workflow in 10 Minutes