The Only n8n Tutorial You Need: Build 3 Real Automations From Scratch

Introduction

Most n8n tutorials teach you one thing and leave you stranded when you try to build something real. This guide is different. By the end, you'll understand the universal pattern behind every n8n workflow well enough to build pretty much anything inside the platform.

We build three progressively complex automations — a daily weather email, a client intake router with smart lead routing, and an AI-powered crypto research assistant — and along the way, you'll learn how every piece of n8n fits together.

Video Tutorial

Watch the full step-by-step video tutorial — everything in this post is covered in detail with screen recordings and live builds:

What Is n8n?

n8n is an open-source workflow automation platform. Think of it as a visual programming environment where you connect nodes together to create automations — without writing code. It's self-hostable, which means your data stays on your servers, and it supports hundreds of integrations out of the box.

Why does n8n beat Zapier or Make at scale? Three reasons:

• Self-hosted: No per-execution pricing. Run as many workflows as your server can handle.
• Code when you need it: Drop into JavaScript or Python inside any workflow for custom logic.
• AI-native: First-class support for LLM nodes, vector stores, and agent chains — not bolted-on afterthoughts.

The n8n Canvas & Your First Nodes

When you open n8n, you see a blank canvas. This is where you'll build every workflow. The canvas works like a flowchart: you place nodes (boxes that do things), connect them with wires, and data flows left to right.

Each node receives data from the previous node, processes it, and passes results to the next one. That's the entire mental model. Every automation you'll ever build follows this pattern.

On the left side, you'll find the Executions tab — this shows every time your workflow has run, what data flowed through, and whether anything failed. It's your debugging dashboard. Below that is the Credentials section where you store API keys and login details securely.

The 5 Node Categories

Every n8n workflow is built from just five types of nodes. Once you understand these categories, you can build anything:

That's it. Every workflow you'll ever build is some combination of these five categories wired together.

APIs Explained Like a Vending Machine

If APIs confuse you, think of them like a vending machine:

• You (the client) walk up to the machine and press a button — that's your request
• The machine (the server) checks if you've paid (your API key), finds the item, and drops it — that's the response
• The button you press is the endpoint — different buttons give you different things
• The coins you insert are your authentication — no coins, no snack

In n8n, the HTTP Request node is your hand pressing the button. You give it a URL (which vending machine), a method (which button), and optionally some authentication (coins), and it returns whatever the API sends back.

Build #1: Daily Weather Email

Our first build is simple but demonstrates the full pattern: trigger → fetch data → send output.

Step 1: Schedule Trigger

Add a Schedule Trigger node and set it to fire every day at 6:00 AM. This is what kicks off the workflow automatically — no human needed.

Step 2: Hit a Free Weather API

Add an HTTP Request node. Point it at a free weather API (like Open-Meteo or WeatherAPI) with your city's coordinates. The node sends a GET request and receives back temperature, conditions, and forecast data as JSON.

Step 3: Send the Email

Add a Send Email node (Gmail or SMTP). In the body, reference the weather data from the previous node using n8n's expression syntax: {{ $json.temperature }}, {{ $json.conditions }}, etc. Wire it all together and you have a weather briefing landing in your inbox every morning.

Build #2: Client Intake Router

This build adds branching logic — the workflow makes decisions based on the data it receives.

Step 1: n8n Form Trigger

Instead of a schedule, we use an n8n Form Trigger. This creates a hosted form with fields like name, email, company, and annual revenue. When someone submits the form, the workflow fires with their data.

Step 2: Switch Node — Route by Revenue

Add a Switch node that checks the revenue field. Leads over $1M go down one path, $100K–$1M go down another, and everyone else goes to a third. This is your routing logic — different leads get different treatment.

Step 3: Personalized Emails

Each branch gets its own Send Email node with messaging tailored to that segment. High-value leads get a personal touch from the founder. Mid-tier leads get a consultation booking link. Smaller leads get a self-serve resources email.

Step 4: Log to Google Sheets

All three branches merge back and flow into a Google Sheets node that logs every submission — name, email, revenue tier, timestamp, and which email was sent. Now you have a CRM-lite running on autopilot.

Build #3: AI Crypto Research Assistant

Our final build brings AI into the mix. This workflow fetches live cryptocurrency data, identifies big movers, and uses GPT to generate analysis — all automatically.

Step 1: Fetch Live Coin Data

An HTTP Request node hits a crypto API (like CoinGecko) to pull current prices, 24h change percentages, and market caps for the top coins.

Step 2: Clean and Filter for Big Movers

A Code node (or Filter + Set nodes) processes the raw data, keeping only coins that moved more than 5% in the last 24 hours. This cuts noise and focuses the AI on what matters.

Step 3: Aggregate for One AI Call

An Aggregate node combines all the filtered coin data into a single item. This is important — instead of sending 10 separate AI requests (expensive), we send one request with all the data (cheap).

Step 4: Send to GPT for Analysis

An OpenAI node receives the aggregated data with a prompt like: "Analyze these cryptocurrency movements. Identify potential catalysts, correlations, and whether any moves look like outliers." GPT returns a structured analysis.

Step 5: Save to Google Sheets

The AI analysis gets logged to a Google Sheet with a timestamp. Run this daily and you build a rolling research journal of crypto market movements with AI commentary.

Step 6: Switch to Schedule Trigger

Replace the manual trigger with a Schedule Trigger and set it to run daily. Now your AI crypto analyst works while you sleep.

The Universal Pattern Behind Every Workflow

Every n8n automation follows the same skeleton:

1. Trigger: Something starts the workflow (schedule, webhook, form, email)
2. Fetch: Get the data you need (HTTP request, database query, app integration)
3. Process: Transform, filter, or route the data (code, switch, merge, AI)
4. Output: Do something with the result (send email, update sheet, post message, save to DB)

That's it. The weather email is Trigger → Fetch → Output. The intake router adds Process (routing). The crypto assistant adds Process (filter + AI). But the skeleton is always the same.

Once you see this pattern, building new automations becomes a matter of swapping pieces. Need a Slack bot instead of email? Swap the output node. Need to pull from a database instead of an API? Swap the fetch node. The structure stays the same.

Frequently Asked Questions

Is n8n free?

n8n has a free self-hosted version (unlimited workflows, unlimited executions) and a paid cloud version. For most users getting started, the cloud free tier is enough. For production, self-hosting on a $5/mo VPS is the best value.

Do I need to know how to code?

No. All three builds in this tutorial are done visually with zero code. However, n8n does let you drop into JavaScript or Python when you need custom logic — which is one of its biggest advantages over Zapier and Make.

Can I use n8n with OpenClaw?

Yes. n8n can trigger OpenClaw actions via webhooks, and OpenClaw can call n8n workflows via HTTP. This lets you combine structured automations (n8n) with autonomous agent behavior (OpenClaw) in the same system.

How is n8n different from Zapier?

Zapier charges per execution and locks you into their cloud. n8n is self-hostable (no per-execution cost), supports code nodes for custom logic, and has first-class AI/LLM support. At scale, n8n is dramatically cheaper and more flexible.