Here's the thing nobody admits about automation tutorials: most of them start with a workflow that's already half-built. The narrator says "so here's the workflow I prepared earlier," and you're already lost — because the part you actually needed to see was how the empty screen became that.
New to n8n? Start with the complete beginner's guide — every concept explained once, with the whiteboard diagrams, then come back here.
So this one starts with nothing. A blank canvas. And by the end of it — about five minutes — you'll have built a real, working automation that reaches out to the internet and brings back the live price of Bitcoin. Not a demo. Not a mock-up. A real number, fetched by something you built.
You don't need to know how to code. You don't need an API key, a credit card, or a sign-up. And you don't need to have used n8n before, because we're going to define every word as it appears.
What we're building, in three steps
The whole thing is three moves:
- Add a trigger — the switch that starts everything
- Add a step that reaches out to the internet and grabs the price
- Press run, and watch a real number come back
That's it. That's the entire video. If that sounds too small to be useful — good. The point of a first workflow isn't to be impressive; it's to make the pieces stop being abstract. Once you've seen data arrive on your own screen, every other n8n tutorial suddenly makes sense.
First: what actually IS n8n?
n8n is a tool for connecting things that don't naturally talk to each other. A spreadsheet and an email inbox. A website and a chat app. A price on the internet and a message on your phone.
You build these connections visually — you drag boxes onto a canvas and draw lines between them — instead of writing code. The technical name for one of these connected chains is a workflow.
And each box in that chain is called a node. One node, one job. A node might fetch something, filter something, send something, or wait for something. String a few together and you've automated a task you used to do by hand.
That's the whole mental model. Canvas → workflow → nodes. Everything else in n8n is a variation on those three words.
Step 1: The trigger — the switch that starts everything
Every workflow needs a first step, and it's always a trigger.
A trigger is the answer to one question: when should this run? It might be "when I click a button." It might be "every morning at 9am." It might be "whenever someone fills in my form." Until you answer that question, n8n has no idea when to do anything, so it does nothing.
For your first workflow, we use the simplest possible trigger: manual. It runs when you press the button, and not before. Nothing happens behind your back, nothing runs while you're asleep, nothing costs you anything. Perfect while you're learning.
You'll see it on the canvas as a small box labelled "When clicking 'Execute workflow'". That box is your on switch.
Step 2: The HTTP Request node — talking to the internet
Now for the piece that does the real work — and the piece with the most intimidating name.
What even is an HTTP request?
Strip away the acronym and it's this: your workflow needs to talk to the internet, so it goes to a web address and brings back whatever's there. That's the whole job.
It's the same thing your browser does when you type an address and press Enter. You ask for a page, a server sends it back. An HTTP request is that exact transaction, except your workflow is doing the asking instead of you.
So when you add an HTTP Request node, you're adding a box that says: "go to this address, and bring me back what you find."
The address we use is a free, public one that returns the current Bitcoin price. No key, no sign-up, no account. You paste it in, and that's the configuration finished.
Step 3: Press run — and the number arrives
Click Execute step, and the panel on the right fills up.
That panel is called the output, and it's where your data lives. Inside it you'll see the live price of Bitcoin — the real number, right now, pulled off the internet by a thing you built about ninety seconds ago.
This is the moment worth pausing on. Not because the number is interesting, but because you now have data inside a workflow. Everything else n8n can do — filtering it, reformatting it, emailing it, posting it to Slack, feeding it to an AI — starts from exactly this point.
The trap: two orange buttons that do different things
Here's the one thing that trips up almost everybody, and it's worth burning into your memory now rather than losing an hour to it later.
There are two orange buttons in n8n, and they are not the same.
- The small one, inside a node's settings panel, is Execute step. It runs just that one box. Use it while you're building, to test one piece at a time.
- The big one, at the bottom of the canvas, is Execute workflow. It runs the whole chain, start to finish.
Same colour, completely different jobs. When something "doesn't work" in n8n for a beginner, this is very often why — one box ran, the rest never did.
One more word: "items"
You'll see the word item everywhere in n8n, so let's define it while it's still simple.
An item is one piece of data moving through your workflow. One price. One email. One row from a spreadsheet. If a node fetches fifty rows, that's fifty items — and here's the useful part: every node after it quietly runs once for each one.
You don't write a loop. You don't manage a counter. You build the workflow as if there's one item, and n8n repeats it for however many turn up. That single behaviour is most of what makes visual automation feel effortless once it clicks.
What you just built
Two boxes. A trigger, and an HTTP request. One real, live number on your screen.
And here's the genuinely useful part: swap that address for a different one, and it just works. A different coin. A weather API. A currency rate. The workflow doesn't care what's at the other end of the address — the shape of what you built stays identical.
You didn't follow a tutorial. You built a tool.
Where to go next
The obvious limitation of what you've built is that it only runs when you press the button. The natural next step is making it run on its own — every morning, at a time you choose, without you being there.
That's a schedule trigger, and it's a five-minute change to the workflow you already have — it's the next tutorial in this series.
If you'd rather not have to remember to come back for it: subscribe and I'll email you when the next one lands. One email per tutorial — the workflow, the exact settings, and the mistakes that cost me hours so they don't cost you any. It's free, and one click gets you off the list.
You can also browse the whole n8n series if you'd rather jump ahead.
FAQ
Do I need to pay for n8n?
No. n8n is free to self-host, and there's a cloud trial if you'd rather not install anything. Nothing in this tutorial costs money.
Do I need an API key?
Not for this one. The Bitcoin price endpoint used here is public and free — no key, no account, no sign-up. You'll need keys later for services like Gmail or OpenAI, and we cover creating those properly when we get there.
Why isn't my workflow running automatically?
Because a manual trigger only fires when you press the button — that's what makes it safe to learn with. Nothing runs on its own until you swap in a schedule trigger and publish it.
I clicked run and nothing happened.
Check which orange button you pressed. The small one inside the node runs only that node; the big one at the bottom of the canvas runs the whole workflow. This is the single most common beginner stumble in n8n.
What's the difference between a node and a workflow?
A workflow is the whole chain. A node is one box inside it. One node does one job; a workflow is what you get when you connect several.
