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

Most n8n tutorials teach you one workflow and leave you guessing when it comes time to build your own. This guide is different. By the end, you will understand the universal pattern behind every n8n automation — and you will have built three real ones to prove it.

I recorded a full video walkthrough of everything in this post. If you prefer watching over reading, here it is:

What Is n8n and Why Should You Care?

n8n is an open-source workflow automation tool. Think Zapier or Make, but with a critical difference: it scales without punishing you on pricing, and it gives you full control over your data and logic. You can self-host it, run it locally, or use their cloud offering.

If you are building an AI agency or automating business processes for clients, n8n is one of the most important tools in your stack. It sits at the center of everything — connecting APIs, routing logic, triggering AI calls, and logging results.

The 5 Node Categories You Need to Know

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

Triggers — what starts the workflow. A schedule, a webhook, a form submission, or an incoming message.
Actions — built-in integrations with apps like Gmail, Google Sheets, Slack, and hundreds more.
HTTP Request — the universal connector. If an app has an API, this node can talk to it.
Logic — switch nodes, if/else, merge, split, and filter. This is how you route data down different paths.
AI — nodes that connect to language models like GPT, Claude, or local models for analysis, summarization, and generation.

Every automation you will ever build is some combination of these five categories. The only thing that changes is which specific nodes you pick and how you wire them together.

How APIs Actually Work (No Jargon)

Before we build anything, you need to understand APIs — because the HTTP Request node is the most powerful node in n8n, and it talks to APIs.

Think of an API like a vending machine. You walk up, press a specific button (the endpoint), insert payment (your API key), and the machine gives you exactly what you asked for (the response). You do not need to know how the machine works inside. You just need to know which button to press and what you will get back.

That is exactly how the HTTP Request node works. You give it a URL, tell it what method to use (GET for reading, POST for sending), include any required authentication, and it returns the data.

Build 1: Daily Weather Email

The first build is simple by design. A workflow that runs every morning at 6 AM, fetches the current weather from a free API, and sends you an email with the forecast.

This uses three node categories: a Schedule Trigger to kick it off daily, an HTTP Request to hit the weather API, and an Action node (Gmail) to send the email. Three nodes, three categories, one useful automation.

The key lesson here is the pattern. Trigger → Fetch Data → Do Something With It. This pattern powers 80% of all automations.

Build 2: Client Intake Router

The second build is where things get practical for agency owners. A client fills out an n8n form with their name, email, company size, and revenue range. Based on the revenue range, the workflow routes them down different paths — enterprise leads get one email, mid-market leads get another, and smaller leads get a third.

Every path also logs the lead to a Google Sheet for tracking. This workflow introduces the Switch node for conditional routing and shows how a single form can power an entire intake pipeline.

The pattern here is: Trigger → Collect Data → Route by Condition → Take Action Per Path. This is the pattern behind every CRM integration, lead scoring system, and support ticket router you will ever build.

Build 3: AI Crypto Research Assistant

The third build combines everything. The workflow hits a live cryptocurrency API, pulls current prices for the top coins, filters for the ones that moved more than 5% in the last 24 hours, aggregates the filtered data into a single payload, sends it to GPT for analysis, and saves the AI-generated report to Google Sheets.

This is where n8n really shines. You are combining real-time data, filtering logic, AI analysis, and storage — all in one visual workflow that runs on a schedule.

The pattern: Trigger → Fetch Live Data → Filter and Clean → AI Analysis → Store Results. This is the same pattern behind AI-powered market research, competitor monitoring, social media analysis, and dozens of other high-value automations.

The Universal Pattern Behind Every Workflow

After building these three, the meta-pattern becomes clear:

Something triggers the workflow — a schedule, a webhook, a form, a message.
Data comes in — from an API, a database, a form field, or an incoming request.
Logic decides what happens — routing, filtering, transforming, or combining.
Actions execute — send emails, update sheets, call AI models, push to CRMs.

Every automation you will ever build follows this pattern. The weather emailer, the client router, and the crypto assistant are all the same skeleton with different organs. Once you see it, you cannot unsee it — and that is the point.

Where to Go From Here

If you want to go deeper on building and selling AI automations, I run a community where we do exactly that. Join us at skool.com/sprint — it is where agency owners learn to build, package, and sell AI agent systems to real clients.

And if you are a business owner looking to implement AI automation without building it yourself, my team at Kingstone Systems handles that for you.