n8n Automation Mastery:
From Zero to Pro

What Is Workflow Automation?

Automation is the practice of connecting apps, services, and data so that repetitive tasks run by themselves. Instead of manually copying form data to a spreadsheet, or posting to three platforms one by one, you build a workflow that handles it forever.

What Is n8n?

n8n (pronounced “n-eight-n”) is an open-source, self-hostable workflow automation platform with a visual node-based editor. It connects 350+ apps and services, and unlike Zapier or Make, you own your data and can write real JavaScript/Python inside nodes.

• ✓ Self-hostable — your data stays on your server
• ✓ 350+ native integrations (Google, Slack, OpenAI, Airtable, etc.)
• ✓ Full JavaScript & Python support inside nodes
• ✓ Webhooks, schedules, event-triggers
• ✓ Free and open-source core

n8n vs Zapier vs Make: Full Comparison

Real-World n8n Use Cases

n8n Installation: Three Options

Option A: n8n Cloud — 5 Minutes

Option B: Self-Hosted via npm

# Install n8n globally via npm
npm install -g n8n

# Start n8n (opens on port 5678)
n8n start

# Visit in your browser
http://localhost:5678

Option C: Docker (Production-Ready)

docker run -it --rm \
  -p 5678:5678 \
  -e N8N_BASIC_AUTH_ACTIVE=true \
  -e N8N_BASIC_AUTH_USER=admin \
  -e N8N_BASIC_AUTH_PASSWORD=your-password \
  -v ~/.n8n:/home/node/.n8n \
  n8nio/n8n

The n8n Canvas: A Visual Walkthrough

When you open n8n, you land on the workflow canvas — a drag-and-drop editor where all automation logic lives.

Understanding Node Types

🌍 First Workflow: Fetch a Random Quote

Build this: every time you click Run, it fetches a random quote from a public API and displays it.

Triggers: How Workflows Start

A trigger wakes up your workflow. Every workflow must start with exactly one trigger node. n8n supports multiple types:

• ⏰ Schedule TriggerRun at fixed intervals — every hour, every Monday 9am, or any cron expression
• 🌐 Webhook TriggerStart when any external service sends HTTP POST/GET to your n8n URL
• 📧 Email TriggerReact to new emails matching specific rules or filters
• 📋 New Row TriggerFire when a new row is added to Google Sheets or Airtable
• 🖱️ Manual TriggerYou click “Run” — useful for testing and on-demand processes

Webhooks: Your Automation Gateway

A webhook gives your workflow a unique URL. Any app that can send HTTP requests can trigger it instantly.

# Production webhook (active workflows)
https://your-n8n.com/webhook/a8f3c2e1-4b9d-11ee

# Test webhook (open 2min during testing)
https://your-n8n.com/webhook-test/a8f3c2e1-4b9d-11ee

n8n Data Structure: JSON Items

n8n passes data between nodes as arrays of JSON items. Every node receives an array and outputs a new array.

// n8n always works with arrays of items
[
  {
    "json": {
      "id": "1",
      "name": "Alice",
      "email": "[email protected]"
    }
  }
]

Expressions: Dynamic Values

Expressions let you use dynamic data from previous nodes anywhere using the {{ }} syntax.

// Access current item data
{{ $json.email }}
{{ $json.name.toUpperCase() }}

// Reference a specific node
{{ $node["HTTP Request"].json.title }}

// Date & time
{{ $now.format("YYYY-MM-DD") }}

// Math & logic
{{ $json.price * 1.2 }}
{{ $json.status === "active" ? "On" : "Off" }}

// Array operations
{{ $json.tags.join(", ") }}
{{ $items().length }}

Automation 1: Email Auto-Responder

When a contact form sends a webhook, automatically send a personalized confirmation email and log the lead to Google Sheets.

{
  "to": "{{ $json.email }}",
  "subject": "Thanks for reaching out, {{ $json.name }}!",
  "body": "Hi {{ $json.name }},\n\nThank you for your message.\n\nWe'll reply within 24 hours.\n\nBest,\nThe Team"
}

Automation 2: Google Sheets → Slack Morning Digest

Every morning at 8am, pull today’s tasks from Sheets and post a formatted summary to Slack.

// Filter rows where date = today and status != done
const today = new Date().toISOString().split('T')[0];
const filtered = items.filter(item => {
  return item.json.date === today && item.json.status !== 'done';
});
return filtered;

Automation 3: HTTP Request + OpenAI API

The HTTP Request node connects to any API. Here’s how to call OpenAI for AI-powered text processing.

{
  "method": "POST",
  "url": "https://api.openai.com/v1/chat/completions",
  "headers": {
    "Authorization": "Bearer {{ $credentials.openAiApiKey }}"
  },
  "body": {
    "model": "gpt-4o-mini",
    "messages": [{
      "role": "user",
      "content": "Summarize in 2 sentences: {{ $json.article_text }}"
    }],
    "max_tokens": 200
  }
}

🟢 Level 1: Auto-Fetch Content Ideas Daily

Pull trending topics from Google Trends and RSS feeds into a Google Sheet every morning — zero manual research.

// RSS Feed Node
{
  "feedUrl": "https://trends.google.com/trends/trendingsearches/daily/rss?geo=US",
  "limit": 10
}

// Set Node — format for Google Sheets
{
  "topic": "{{ $json.title }}",
  "source": "Google Trends",
  "date": "{{ $now.format('YYYY-MM-DD') }}",
  "status": "idea"
}

🟡 Level 2: AI Caption Generation + Airtable Storage

For each idea in the sheet, generate a scroll-stopping caption with OpenAI, then store everything in Airtable.

// OpenAI Node — User Message (dynamic per topic)
"Write an Instagram Reels caption for: {{ $json.topic }}

Requirements:
- Hook in first line (stop the scroll)
- 3-5 sentences max
- 1 call-to-action at the end
- Return ONLY the caption, no explanation"

🟠 Level 3: Full Script + Hashtags + Auto-Schedule

Generate complete 30-second video scripts with AI, generate hashtag sets, and push everything to Buffer for scheduling.

"Write a 30-second Instagram Reels script about: {{ $json.Topic }}

FORMAT:
[HOOK 0-3s]: One shocking statement or question
[PROBLEM 3-10s]: Briefly state the pain point
[SOLUTION 10-25s]: 3 bullet points (text overlays, max 6 words each)
[CTA 25-30s]: Strong call to action"

🟣 Level 4: MASTER — Full Autonomous Pipeline

Every component connected. Runs daily without human input. This is your content factory on autopilot.

{
  "name": "Instagram Reels Full Pipeline",
  "nodes": [
    {
      "id": "trigger",
      "name": "Daily 7am",
      "type": "n8n-nodes-base.scheduleTrigger",
      "parameters": {
        "rule": {"interval": [{"field": "hours", "hoursInterval": 24}]}
      }
    },
    {
      "id": "ai-script",
      "name": "Generate Script + Caption",
      "type": "n8n-nodes-base.openAi",
      "parameters": {
        "model": "gpt-4o-mini",
        "prompt": "Write a 30s Reels script for: {{ $json.topic }}"
      }
    }
  ]
}

Error Handling: Don’t Let Workflows Die Silently

By default, a failed node stops your workflow silently. In production, that’s unacceptable. Here’s how to handle errors properly.

1. Global Error Workflow

Set a dedicated Error Workflow in Settings → Error Workflow. It runs automatically whenever any workflow fails.

// Slack node in your Error Workflow
{
  "channel": "#automation-alerts",
  "text": "🚨 Workflow Failed!\n*Workflow:* {{ $json.workflow.name }}\n*Error:* {{ $json.execution.error.message }}\n*Time:* {{ $now.format('YYYY-MM-DD HH:mm') }}"
}

2. Inline Error Handling Pattern

• ✓ Enable “Continue On Fail” on risky nodes (API calls, external services)
• ✓ Follow with an IF node: check {{ $json.error !== undefined }}
• ✓ TRUE branch handles the error; FALSE branch continues normal flow

3. Retry Logic with Loop + Wait

{
  "maxIterations": 3,
  "waitBetweenRetries": 5000,
  "retryCondition": "{{ $json.error !== undefined }}"
}

Scaling Workflows in Production

Architecture Best Practices

• ✓ One workflow = one responsibility. Don’t build 20-node monsters.
• ✓ Always log outputs to Sheets or a database for debugging.
• ✓ Version control: export workflow JSON to Git regularly.
• ✓ Use tags and folders to organize workflows by project.
• ✗ Don’t store sensitive data in workflow variables — use Credentials.
• ✗ Don’t run AI calls in loops without rate-limit protection.

The Final Project: Personal Automation OS

You’ll build a connected network of workflows that manages your digital work automatically. This is your portfolio piece.

System Architecture Overview

Final Project Checklist

• ✓ Build at least 5 connected workflows (inputs + processing + outputs)
• ✓ Include at least 1 AI node (OpenAI, Claude, or Gemini)
• ✓ Error handling with Slack/email notifications on failure
• ✓ Use sub-workflows for at least 1 reusable component
• ✓ Log all important outputs to Airtable, Sheets, or a database
• ✓ All workflows activated — running without you
• ✓ Export full workflow JSON and document each workflow’s purpose

What to Do After This Course