— Build a real, working n8n workflow from scratch in ~30 minutes. We'll fetch the Bitcoin price every weekday at 9 AM, branch on whether it's above $100k, and notify either by email or Slack. Free tier only, no prior experience required. By the end you'll understand triggers, nodes, expressions, and conditional logic — the foundation everything else builds on.

I've onboarded a few colleagues to n8n over the past year. The pattern is the same every time: they start with the official "Schedule + NASA solar flares" tutorial, build something that works, then have no idea how to apply it to their actual job. The missing piece is a workflow that uses a real-world API and demonstrates why you'd use each node type — not just how.

Here's that workflow.

Five concepts you need before clicking anything

Internalize these. They'll save you hours of confusion later.

• Workflow — a collection of connected nodes that automates a process. One workflow = one automation.
• Node — a single step. Each does one thing: trigger, fetch, transform, send.
• Trigger node — the first node. Decides when the workflow runs.
• Execution — one full run of the workflow, top to bottom. n8n logs every execution for debugging.
• Expression — JavaScript-flavored snippets in {{ }} that reference data from previous nodes.

When something breaks, ask yourself: which node failed, what data did it receive, what did it try to do with that data? Almost every problem maps to those three questions.

What we're building

Schedule (every weekday 9 AM)
        ↓
HTTP Request (fetch BTC price from CoinGecko)
        ↓
Edit Fields (extract price as a clean number)
        ↓
   If (price > 100,000?)
   ┌────┴────┐
   true     false
    ↓         ↓
  Email    Slack
(celebrate) (notify)

Six nodes, two branches, one schedule. Real API, real notifications, every concept a beginner needs.

Setup

Two paths to start:

• n8n Cloud — sign up at n8n.io, 14-day free trial, no credit card. After trial, paid plans from €24/month for 2,500 executions.
• Self-hosted — free forever, runs on your own server with Docker. Requires basic Linux comfort. Full production setup walkthrough in our n8n self-hosting guide.

For this tutorial, Cloud is faster — every step works identically on self-hosted. After signup, click Create Workflow in the upper-right. You'll see an empty canvas with one button: Add first step.

Step 1: Schedule trigger

1. Click Add first step.
2. Search Schedule and pick Schedule Trigger.
3. Trigger Interval: Days
4. Days Between Triggers: 1
5. Trigger at Hour: 9am
6. Optionally: under Trigger on Weekdays, select Mon–Fri only.

Critical detail: the Schedule trigger only fires when the workflow is published. While building, run the workflow manually with the Execute Workflow button at the bottom of the canvas.

Step 2: HTTP Request — fetch BTC price

The HTTP Request node is the most powerful node in n8n. It calls any public API, even ones without dedicated integrations.

1. Click + on the right of the Schedule trigger.
2. Search HTTP Request, select it.
3. URL: https://api.coingecko.com/api/v3/simple/price?ids=bitcoin&vs_currencies=usd
4. Authentication: None (CoinGecko allows unauthenticated calls).
5. Method: GET
6. Click Execute step.

You should see output like:

{
  "bitcoin": {
    "usd": 105432
  }
}

That's the live BTC price. Close the node panel — we'll use this data next.

Pro tip that saves debugging hours: Execute step runs only that single node, with sample data, without firing the entire workflow. Use it on every new node before connecting the next one. This catches 80% of mistakes early, when they're easy to fix.

Step 3: Edit Fields — clean up the data shape

The CoinGecko response nests the price inside bitcoin.usd. To make later steps cleaner, let's promote it to a top-level price field.

1. Click + on the HTTP Request node.
2. Search Edit Fields (also called "Set" in some versions).
3. Under Fields to Set, click Add Field.
4. Name: price
5. Value: toggle the = icon to red (this enables expression mode).
6. Drag bitcoin.usd from the left panel into the value field. The expression becomes {{ $json.bitcoin.usd }}.
7. Click Execute step.

Output should now be:

{
  "price": 105432
}

Expressions are how you reference data from previous nodes. Anything inside {{ }} is JavaScript. $json means "data the previous node returned." You don't need to memorize syntax — drag fields from the left panel and n8n writes the expression for you.

Step 4: If node — conditional branching

The If node creates two branches. We'll route based on whether BTC is above $100k.

1. Click + on the Edit Fields node.
2. Search If, select it.
3. Under Conditions:
   • Value 1: drag price from the left panel → {{ $json.price }}
   • Operation: Number > Larger
   • Value 2: 100000
4. Click Execute step to verify.

The If node now exposes two output connectors: true (top) and false (bottom).

Common gotcha: make sure Operation is set to Number, not String. String comparison treats "5" > "100000" as true (alphabetic order), which silently breaks your logic. This bites everyone at least once.

Step 5: Action nodes (email + Slack)

Email on the "true" branch

1. Click + labeled true on the If node.
2. Search Send Email, select it.
3. Click Create new credential → configure SMTP. Gmail needs an app-specific password; most ESPs accept standard SMTP creds.
4. To Email: your address.
5. Subject: BTC just hit $100k!
6. Text (expression mode): BTC is currently at ${{ $json.price }} — celebration time!
7. Click Execute step to send a test email.

Slack on the "false" branch

1. Back on the canvas. Click + labeled false on the If node.
2. Search Slack, select it.
3. Click Create new credential → OAuth2 flow connects your workspace.
4. Resource: Message, Operation: Send.
5. Pick a channel (e.g., #general).
6. Text (expression mode): BTC is at ${{ $json.price }} — still under $100k.
7. Click Execute step.

If both test sends worked, the workflow is functionally complete. Save it now — Cmd/Ctrl + S or click Save at the top right. n8n doesn't auto-save while you build.

Step 6: Test, then publish

Two final steps separate "kinda works" from "actually runs reliably."

Run the full workflow once manually. Click Execute Workflow at the bottom. Every node turns green on success or red on failure. If anything fails, click the failed node — n8n shows the exact error and the input data that triggered it.

Publish. Toggle Publish at the top of the editor to active. Now the Schedule trigger fires every weekday at 9 AM automatically.

To verify it actually fires, open Executions in the left sidebar. After 9 AM tomorrow, you'll see a fresh execution logged. Click into any execution to see what data flowed through each node — invaluable for debugging.

Six gotchas that bite everyone

1. Forgetting to publish. Most common reason "the schedule isn't firing." If the toggle isn't on Published, the trigger is dormant.
2. String vs Number in If nodes. "5" > "10" returns true alphabetically. Always pick the right operation type.
3. Hardcoding what should be an expression. Typing the literal text $json.price into a regular field doesn't work. Toggle the = icon to red first.
4. Polling APIs every minute on n8n Cloud. A 1-minute schedule = 43,200 executions/month, which exceeds most paid plan limits. Use webhooks where possible.
5. Not testing each node individually. Click Execute step on every new node before connecting the next. Prevents 80% of debugging pain.
6. No backup of N8N_ENCRYPTION_KEY (self-hosted). Lose this and every saved credential is unrecoverable. Back it up to a password manager the moment you generate it.

What to build next

You now know the foundation. Three productive next steps:

1. Replace the Schedule trigger with a Webhook trigger to react to events from external systems instead of polling. Big efficiency gain. New to webhooks? Read this practical webhook primer including testing.
2. Add an error-handling node that fires when any step fails. Without it, silent failures will burn you eventually. The pattern: every critical workflow ends with a "Send Email/Slack on Error" branch.
3. Build something for your actual job. Pick one repetitive task you do every week (compiling stats, posting reports, syncing data) and rebuild it as an n8n workflow. The fastest way to learn is to solve a real problem.

If you're comparing n8n with other automation platforms before committing more time, here's our Zapier vs Make 2026 breakdown covering trade-offs across hosted alternatives.

The most useful first workflow for SMBs

The pattern that pays back fastest: form submission → CRM record → notification. New lead fills a form, data lands in CRM with proper tagging, your team gets notified instantly. Eliminates manual data entry, reduces lead response time from hours to seconds, and uses every concept from this tutorial.

Build this version once and you'll see why n8n's learning curve is worth it.

Originally published on TrackStack — practical write-ups on automation, tracking, and infrastructure for SMBs. If you got stuck on any step, drop a comment with what broke and I'll help debug.