What is n8n? - A Complete Beginner Guide

1. THE PROBLEM N8N SOLVES#

Imagine This Scenario#

You work at a pizza shop. Every day you have to:

Check new orders (from your website)
Send a confirmation email to the customer
Send the order to the kitchen printer
Update your inventory spreadsheet
If the order is above $50, send a text to the manager

You do this manually for every single order. 50 orders a day = 50 times doing the same 5 steps.

That's exhausting. That's what n8n fixes.

n8n is a tool that says: "Tell me the steps ONCE, and I'll do them automatically forever."

Now Think About Prairie Materials#

Every day, trucks deliver aggregate (rock, gravel, limestone) to job sites. Every delivery creates a ticket in the database with weight, customer, truck info, etc.

Someone has to:

Take that ticket data
Format it into HaulHub's required JSON format
Send it to HaulHub's API
Check if it succeeded
Handle errors if it didn't

Doing this manually for hundreds of tickets per day is insane. That's why Karl wants n8n.

2. WHAT IS N8N?#

The Simple Answer#

n8n is a robot assistant that does repetitive tasks for you automatically.

You tell it: "When THIS happens, do THAT." And it does it. Forever. Without complaining. Without forgetting. Without making mistakes.

The Technical Answer#

n8n (pronounced "n-eight-n") is an open-source workflow automation platform. It connects different apps, services, and APIs together so data flows between them automatically.

Think of it Like This#

        1
2
3
4
5
6
7
8
9
10
11
        n8n is like a CONVEYOR BELT in a factory.

Without conveyor belt:
  Worker picks up box → carries it to Station A → carries it to Station B → carries it to Station C
  (slow, tiring, error-prone)

With conveyor belt:
  Box automatically moves from Station A → Station B → Station C
  (fast, automatic, reliable)

n8n is the conveyor belt for your DATA.

What n8n is NOT#

n8n is NOT...	It IS...
A database	A tool that MOVES data between databases
A programming language	A visual tool where you drag-and-drop steps
An app you give to customers	A behind-the-scenes robot that does work for you
AI	An automation tool (but it CAN connect to AI)
A one-time script	A permanent workflow that runs on schedule or on events

3. HOW DOES N8N WORK?#

The Core Concept: NODES and WORKFLOWS#

n8n has two main concepts:

NODE = One Step / One Action#

A node is one single thing that happens. Examples:

"Fetch data from an API"
"Send an email"
"Wait 5 minutes"
"Check if a value is greater than 100"
"Save data to a Google Sheet"

WORKFLOW = Multiple Nodes Connected Together#

A workflow is a chain of nodes. Data flows from one node to the next, like water through pipes.

        1
2
3
4
5
6
7
8
        Simple Workflow:

  [Trigger]  →  [Do Something]  →  [Do Something Else]  →  [Done]

Example:

  [Every morning   →  [Fetch weather    →  [Send email to    →  [Done]
   at 8 AM]            from API]            me with forecast]

How You Build a Workflow (Visual)#

n8n has a drag-and-drop visual editor. It looks like this:

        1
2
3
4
5
6
7
8
9
10
11
12
13
        ┌──────────────────────────────────────────────────────────────┐
│                     n8n Editor (Browser)                     │
│                                                              │
│   ┌───────────┐     ┌──────────┐     ┌──────────┐            │
│   │ Schedule  │────>│  HTTP    │────>│  Gmail   │            │
│   │ Trigger   │     │ Request  │     │  Send    │            │
│   │           │     │          │     │          │            │
│   │ Every 1hr │     │ GET /api │     │ To: boss │            │
│   └───────────┘     └──────────┘     └──────────┘            │
│                                                              │
│   You drag these boxes onto the canvas and connect them      │
│   with lines. No coding required (but you CAN add code).     │
└──────────────────────────────────────────────────────────────┘

The 3 Types of Nodes#

1. TRIGGER NODES (The Starting Point)#

These START the workflow. Something has to kick it off.

Trigger	When It Fires
Schedule Trigger	Every X minutes/hours/days (like an alarm clock)
Webhook Trigger	When someone calls a URL (like someone knocking on a door)
Email Trigger	When you receive an email
Database Trigger	When a new row is added to a database

2. ACTION NODES (The Workers)#

These DO things with data.

Node	What It Does
HTTP Request	Calls any API (GET, POST, etc.)
Gmail / Email	Sends emails
Google Sheets	Reads/writes spreadsheet data
Slack	Sends Slack messages
Code / Function	Runs custom JavaScript code
IF	Makes decisions ("if X, do Y, otherwise do Z")
Set	Transforms/modifies data

3. OUTPUT NODES (The Destination)#

These deliver the final result.

Node	What It Does
Respond to Webhook	Returns data to whoever called the webhook
Write to File	Saves data to a file
Database Insert	Saves data to a database

4. REAL-WORLD EXAMPLES#

Example 1: The Weather Email (Simplest Possible)#

Goal: Every morning at 8 AM, email me today's weather.

        1
2
3
4
5
6
        WORKFLOW:

  [Schedule Trigger]  →  [HTTP Request]  →  [Gmail Send]
   Every day 8 AM         GET weather API     To: me@email.com
                          for Chicago          Subject: Today's Weather
                                               Body: {{temperature}}°F

What happens:

8:00 AM hits → trigger fires
n8n calls the weather API → gets back { "temperature": 45, "condition": "sunny" }
n8n sends you an email: "Today's Weather: 45°F, Sunny"
You did nothing. It just happened.

Example 2: New Customer Alert (Webhook)#

Goal: When a new customer signs up on your website, notify the sales team on Slack.

        1
2
3
4
5
        WORKFLOW:

  [Webhook Trigger]  →  [Slack Node]
   POST /new-customer     Channel: #sales
                          Message: "New customer: {{name}} - {{email}}"

What happens:

Your website has a signup form
After signup, your website calls: POST https://your-n8n.com/webhook/new-customer with body: { "name": "John", "email": "john@test.com" }
n8n receives this and sends a Slack message: "New customer: John - john@test.com "

Example 3: Daily Sales Report (With Conditions)#

Goal: Every night, check today's sales. If sales > $1000, email the boss. If not, do nothing.

        1
2
3
4
5
6
        WORKFLOW:

  [Schedule Trigger]  →   [HTTP Request]  →  [IF Node]  → TRUE  →  [Gmail Send]
   Every day 11 PM        GET /api/sales     sales > 1000?          To: boss@company.com
                          ?date=today                                "Great day! ${{total}}"
                                                        → FALSE → [Nothing / Stop]

What happens:

11 PM hits → trigger fires
n8n calls your sales API → gets { "total": 1523 }
IF node checks: is 1523 > 1000? YES!
Email sent to boss: "Great day! Sales hit $1,523 today!"
Next day, sales are $800 → IF says NO → no email sent

Example 4: Our Prairie Project (The Real One)#

Goal: Every hour, send new delivery tickets to HaulHub.

        1
2
3
4
5
6
7
8
        WORKFLOW:

  [Schedule Trigger]  →  [HTTP Request]           →  [IF Node]     →  [HTTP Request]       →  [Email]
   Every 1 hour           GET our-api/                count > 0?        POST to HaulHub         Notify Karl
                          haulhub-batch                                  with ticket data        "Sent 15 tickets"
                          ?limit=100
                                                      count = 0?   →  [Stop]
                                                                       "No new tickets"

What happens every hour:

Trigger fires
n8n calls YOUR API to get tickets in HaulHub format
If there are tickets → sends them to HaulHub
If no tickets → does nothing
Emails Karl the result

Nobody has to do anything. It just runs. 24/7. Forever.

Short Answer: NO, but it CAN connect to AI.#

n8n itself is not AI. It's an automation tool. It doesn't "think" or "learn." It follows exact rules you set.

Think of it this way:

        1
2
3
4
5
        AI (like ChatGPT)  = A brain that thinks and generates answers
n8n                = A conveyor belt that moves things from A to B

They are completely different things.
BUT... you can PUT the brain ON the conveyor belt.

How n8n Can USE AI#

n8n has nodes that connect to AI services:

        1
2
3
4
5
6
        EXAMPLE: Auto-reply to customer emails using AI

  [Email Trigger]  →  [OpenAI Node]        →  [Gmail Send]
   New email           "Read this email         Send AI's reply
   received             and write a              back to customer
                        helpful reply"

        1
2
3
4
5
6
        EXAMPLE: Analyze sales data with AI

  [Schedule Trigger]  →  [Database Query]  →  [OpenAI Node]         →  [Slack]
   Every Monday           Get last week's      "Analyze this sales      Post summary
                          sales data            data and give me         to #reports
                                                insights"                channel

So n8n + AI = Powerful Combo#

Without AI	With AI
n8n moves data from A to B exactly as you told it	n8n moves data from A to B, but asks AI to transform/analyze it along the way
"Send this exact email"	"Write a smart email based on this data, then send it"
Can only follow rules	Can make intelligent decisions

For Our Prairie Project: We Don't Need AI#

Our task is straightforward:

Read ticket data
Transform it to HaulHub format (exact field mapping, no thinking needed)
Send it

This is pure automation. No AI required.

6. N8N VS OTHER TOOLS#

n8n is not the only automation tool. Here are the main ones:

The Big Comparison Table#

Tool	Free?	Self-Hosted?	Code Needed?	Best For
n8n	Free (open source)	Yes (or cloud)	Optional	Developers who want full control
Zapier	No (paid, $20+/mo)	No (cloud only)	No	Non-technical users, simple automations
Make (formerly Integromat)	Freemium	No (cloud only)	No	Visual thinkers, complex workflows
Power Automate	Paid (Microsoft)	No	No	Companies already using Microsoft 365
Apache Airflow	Free (open source)	Yes	Yes (Python)	Data engineers, heavy data pipelines
Pipedream	Freemium	No	Yes (JS)	Developers who prefer code
IFTTT	Freemium	No	No	Personal automations (smart home, etc.)

n8n vs Zapier (Most Common Comparison)#

        1
2
3
4
5
6
7
8
9
10
11
12
13
        ZAPIER:
  - Super easy to use (no coding at all)
  - Expensive ($20-$100+/month)
  - You CANNOT host it yourself (their servers only)
  - Limited: you can only do what their pre-built integrations allow
  - Great for: small businesses, non-developers

N8N:
  - Slightly harder to learn (but still visual drag-and-drop)
  - FREE if you host it yourself
  - You CAN host it on your own server (full control)
  - Unlimited: you can write custom code, call any API
  - Great for: developers, companies who need control and custom integrations

Why Karl Chose n8n for This Project#

Free — n8n is open source, no monthly fees
Self-hosted on Hostinger — Karl already has a Hostinger server, so n8n runs there for free
Custom API calls — We need to call our custom API + HaulHub's API. n8n handles this easily
Developer-friendly — Since you're a developer, n8n gives you more power than Zapier
Runs 24/7 — Once set up on Hostinger, it runs forever without anyone touching it

Quick Summary of Each Tool#

Zapier#

        1
2
3
4
5
6
        Best analogy: Uber — easy to use, but you pay for every ride
Pricing: $20-$100+/month
Hosting: Cloud only (their servers)
Difficulty: Very Easy (no code)
Example: "When I get a Gmail, save attachment to Google Drive"
Good for: Non-technical people

Make (Integromat)#

        1
2
3
4
5
6
        Best analogy: LEGO — very visual, snap pieces together
Pricing: Free tier available, then $9+/month
Hosting: Cloud only
Difficulty: Easy-Medium
Example: "When Shopify order comes in, create invoice in QuickBooks, email customer"
Good for: Visual thinkers, medium-complexity workflows

Power Automate#

        1
2
3
4
5
6
        Best analogy: Microsoft's butler — works great inside Microsoft world
Pricing: Included with Microsoft 365, or $15/month standalone
Hosting: Cloud (Microsoft)
Difficulty: Easy-Medium
Example: "When someone submits a Microsoft Form, create a row in Excel, notify in Teams"
Good for: Companies already deep in Microsoft ecosystem

Apache Airflow#

        1
2
3
4
5
6
        Best analogy: Industrial factory machinery — powerful but complex
Pricing: Free (open source)
Hosting: Self-hosted (requires Python skills)
Difficulty: Hard (requires coding)
Example: "Every night, pull data from 5 databases, transform it, load into data warehouse"
Good for: Data engineers at large companies

Pipedream#

        1
2
3
4
5
6
        Best analogy: GitHub for workflows — code-first but visual
Pricing: Free tier, then $19+/month
Hosting: Cloud
Difficulty: Medium (JavaScript knowledge helps)
Example: "When Stripe payment comes in, call my API, update Airtable, send Slack notification"
Good for: Developers who prefer writing code over drag-and-drop

IFTTT (If This Then That)#

        1
2
3
4
5
6
        Best analogy: A light switch — super simple, one trigger, one action
Pricing: Free (limited), $3.49+/month
Hosting: Cloud only
Difficulty: Very Easy
Example: "If it's going to rain, send me a notification"
Good for: Personal use, smart home, simple 1-to-1 automations

7. HOW N8N FITS IN OUR PRAIRIE PROJECT#

The Architecture (Big Picture)#

        1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
                            PRAIRIE MATERIALS SYSTEM
                    ========================

  ┌──────────────┐
  │   TRUCKS     │  Trucks deliver aggregate, cross the scale
  │   & SCALES   │  Scale records weight, creates ticket
  └──────┬───────┘
         │
         ▼
  ┌──────────────┐
  │   SUPABASE   │  Ticket data stored in tkhist1 table
  │   DATABASE   │  (ticketno, weight, customer, product, etc.)
  └──────┬───────┘
         │
         ▼
  ┌──────────────┐
  │   YOUR API   │  Express.js backend (what you built)
  │  (Port 5000) │  - Reads data from Supabase
  │              │  - Joins customer/location/order data
  │              │  - Transforms to HaulHub format
  │              │  - Generates PDFs
  └──────┬───────┘
         │
         │  n8n calls your API on a schedule
         ▼
  ┌──────────────┐
  │     N8N      │  Workflow automation (on Hostinger)
  │  (Hostinger) │  - Runs every hour (or on schedule)
  │              │  - Calls your API to get ticket data
  │              │  - Sends data to HaulHub
  │              │  - Sends PDFs via email
  │              │  - Handles errors, sends notifications
  └──────┬───────┘
         │
         ▼
  ┌──────────────┐
  │   HAULHUB    │  Government compliance platform
  │              │  - IDOT/contractors see delivery data
  │              │  - Prairie gets paid
  └──────────────┘

What Each Piece Does#

Component	Role	Analogy
Trucks & Scales	Create raw data	The factory that makes products
Supabase	Stores the data	The warehouse
Your API	Reads, transforms, formats data	The packaging department
n8n	Orchestrates and schedules everything	The delivery truck driver
HaulHub	Receives and displays data	The customer's store

Why Can't We Just Skip n8n?#

Good question. You technically COULD skip n8n by:

Writing a cron job in your Node.js server
Using setInterval() to run every hour
Having your server call HaulHub directly

But n8n gives you:

Feature	Without n8n (DIY)	With n8n
Schedule management	Write your own cron code	Visual schedule picker
Error handling	Write try/catch, logging code	Built-in error handling + notifications
Monitoring	Build your own dashboard	n8n shows execution history, success/fail
Changing the flow	Edit code, redeploy	Drag-and-drop in browser, no deploy needed
Non-developer friendly	Karl can't modify it	Karl can see and tweak workflows himself
Email notifications	Write email sending code	Drag an email node onto the canvas
Retry on failure	Write retry logic	Built-in retry settings

The biggest reason: Karl (the client) can see and manage n8n workflows himself without being a developer. If he wants to change the schedule from every hour to every 30 minutes, he just clicks a dropdown. No code changes. No redeployment.

8. KEY TERMINOLOGY#

Term	Meaning	Example
Workflow	A complete automation from start to finish	"Fetch tickets and send to HaulHub"
Node	One single step in a workflow	"Call the API" or "Send an email"
Trigger	The event that starts a workflow	"Every hour" or "When webhook is called"
Webhook	A URL that starts a workflow when someone calls it	`https://n8n.example.com/webhook/my-flow`
Execution	One run of a workflow from start to end	"The 3 PM run sent 15 tickets"
Credentials	Login info for external services stored in n8n	API tokens, email passwords, DB connections
Expression	Dynamic values using `{{ }}` syntax	`{{$json.ticketno}}` gets the ticket number from data
Self-hosted	Running software on YOUR server, not someone else's	n8n on Karl's Hostinger server
Cloud-hosted	Running software on the COMPANY'S servers	Zapier runs on Zapier's servers
Open source	Code is free and public, anyone can use/modify it	n8n's code is on GitHub for free
API	A way for two software systems to talk to each other	Your API talks to Supabase and HaulHub
Cron	A schedule format (e.g., "every hour" or "daily at midnight")	n8n uses cron behind the scenes

FINAL SUMMARY#

        1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
        Q: What is n8n?
A: A free, visual tool that automates repetitive tasks by connecting services together.

Q: How does it work?
A: You create a "workflow" by connecting "nodes" (steps).
   A trigger starts it, nodes do the work, data flows through like a pipeline.

Q: Is it AI?
A: No. It's automation (follows exact rules). But it CAN connect to AI services.

Q: Why do we need it for Prairie?
A: To automatically send ticket data to HaulHub every hour without anyone doing it manually.

Q: Could we use something else?
A: Yes — Zapier, Make, Power Automate, etc. But n8n is free and self-hosted, which is
   why Karl chose it.

Q: Do I need to learn n8n to do my job?
A: Not deeply. Your job is building the API (which is done).
   n8n just CALLS your API. Karl or someone else can set up the n8n workflows
   using the guide we already created (N8N-WORKFLOW-SETUP-GUIDE.md).

Guide created: February 23, 2026

What is n8n? - A Complete Beginner Guide

1. THE PROBLEM N8N SOLVES#

Imagine This Scenario#

You work at a pizza shop. Every day you have to:

Check new orders (from your website)
Send a confirmation email to the customer
Send the order to the kitchen printer
Update your inventory spreadsheet
If the order is above $50, send a text to the manager

You do this manually for every single order. 50 orders a day = 50 times doing the same 5 steps.

That's exhausting. That's what n8n fixes.

n8n is a tool that says: "Tell me the steps ONCE, and I'll do them automatically forever."

Now Think About Prairie Materials#

Every day, trucks deliver aggregate (rock, gravel, limestone) to job sites. Every delivery creates a ticket in the database with weight, customer, truck info, etc.

Someone has to:

Take that ticket data
Format it into HaulHub's required JSON format
Send it to HaulHub's API
Check if it succeeded
Handle errors if it didn't

Doing this manually for hundreds of tickets per day is insane. That's why Karl wants n8n.

2. WHAT IS N8N?#

The Simple Answer#

n8n is a robot assistant that does repetitive tasks for you automatically.

You tell it: "When THIS happens, do THAT." And it does it. Forever. Without complaining. Without forgetting. Without making mistakes.

The Technical Answer#

n8n (pronounced "n-eight-n") is an open-source workflow automation platform. It connects different apps, services, and APIs together so data flows between them automatically.

Think of it Like This#

        1
2
3
4
5
6
7
8
9
10
11
        n8n is like a CONVEYOR BELT in a factory.

Without conveyor belt:
  Worker picks up box → carries it to Station A → carries it to Station B → carries it to Station C
  (slow, tiring, error-prone)

With conveyor belt:
  Box automatically moves from Station A → Station B → Station C
  (fast, automatic, reliable)

n8n is the conveyor belt for your DATA.

What n8n is NOT#

n8n is NOT...	It IS...
A database	A tool that MOVES data between databases
A programming language	A visual tool where you drag-and-drop steps
An app you give to customers	A behind-the-scenes robot that does work for you
AI	An automation tool (but it CAN connect to AI)
A one-time script	A permanent workflow that runs on schedule or on events

3. HOW DOES N8N WORK?#

The Core Concept: NODES and WORKFLOWS#

n8n has two main concepts:

NODE = One Step / One Action#

A node is one single thing that happens. Examples:

"Fetch data from an API"
"Send an email"
"Wait 5 minutes"
"Check if a value is greater than 100"
"Save data to a Google Sheet"

WORKFLOW = Multiple Nodes Connected Together#

A workflow is a chain of nodes. Data flows from one node to the next, like water through pipes.

        1
2
3
4
5
6
7
8
        Simple Workflow:

  [Trigger]  →  [Do Something]  →  [Do Something Else]  →  [Done]

Example:

  [Every morning   →  [Fetch weather    →  [Send email to    →  [Done]
   at 8 AM]            from API]            me with forecast]

How You Build a Workflow (Visual)#

n8n has a drag-and-drop visual editor. It looks like this:

        1
2
3
4
5
6
7
8
9
10
11
12
13
        ┌──────────────────────────────────────────────────────────────┐
│                     n8n Editor (Browser)                     │
│                                                              │
│   ┌───────────┐     ┌──────────┐     ┌──────────┐            │
│   │ Schedule  │────>│  HTTP    │────>│  Gmail   │            │
│   │ Trigger   │     │ Request  │     │  Send    │            │
│   │           │     │          │     │          │            │
│   │ Every 1hr │     │ GET /api │     │ To: boss │            │
│   └───────────┘     └──────────┘     └──────────┘            │
│                                                              │
│   You drag these boxes onto the canvas and connect them      │
│   with lines. No coding required (but you CAN add code).     │
└──────────────────────────────────────────────────────────────┘

The 3 Types of Nodes#

1. TRIGGER NODES (The Starting Point)#

These START the workflow. Something has to kick it off.

Trigger	When It Fires
Schedule Trigger	Every X minutes/hours/days (like an alarm clock)
Webhook Trigger	When someone calls a URL (like someone knocking on a door)
Email Trigger	When you receive an email
Database Trigger	When a new row is added to a database

2. ACTION NODES (The Workers)#

These DO things with data.

Node	What It Does
HTTP Request	Calls any API (GET, POST, etc.)
Gmail / Email	Sends emails
Google Sheets	Reads/writes spreadsheet data
Slack	Sends Slack messages
Code / Function	Runs custom JavaScript code
IF	Makes decisions ("if X, do Y, otherwise do Z")
Set	Transforms/modifies data

3. OUTPUT NODES (The Destination)#

These deliver the final result.

Node	What It Does
Respond to Webhook	Returns data to whoever called the webhook
Write to File	Saves data to a file
Database Insert	Saves data to a database

4. REAL-WORLD EXAMPLES#

Example 1: The Weather Email (Simplest Possible)#

Goal: Every morning at 8 AM, email me today's weather.

        1
2
3
4
5
6
        WORKFLOW:

  [Schedule Trigger]  →  [HTTP Request]  →  [Gmail Send]
   Every day 8 AM         GET weather API     To: me@email.com
                          for Chicago          Subject: Today's Weather
                                               Body: {{temperature}}°F

What happens:

8:00 AM hits → trigger fires
n8n calls the weather API → gets back { "temperature": 45, "condition": "sunny" }
n8n sends you an email: "Today's Weather: 45°F, Sunny"
You did nothing. It just happened.

Example 2: New Customer Alert (Webhook)#

Goal: When a new customer signs up on your website, notify the sales team on Slack.

        1
2
3
4
5
        WORKFLOW:

  [Webhook Trigger]  →  [Slack Node]
   POST /new-customer     Channel: #sales
                          Message: "New customer: {{name}} - {{email}}"

What happens:

Your website has a signup form
After signup, your website calls: POST https://your-n8n.com/webhook/new-customer with body: { "name": "John", "email": "john@test.com" }
n8n receives this and sends a Slack message: "New customer: John - john@test.com "

Example 3: Daily Sales Report (With Conditions)#

Goal: Every night, check today's sales. If sales > $1000, email the boss. If not, do nothing.

        1
2
3
4
5
6
        WORKFLOW:

  [Schedule Trigger]  →   [HTTP Request]  →  [IF Node]  → TRUE  →  [Gmail Send]
   Every day 11 PM        GET /api/sales     sales > 1000?          To: boss@company.com
                          ?date=today                                "Great day! ${{total}}"
                                                        → FALSE → [Nothing / Stop]

What happens:

11 PM hits → trigger fires
n8n calls your sales API → gets { "total": 1523 }
IF node checks: is 1523 > 1000? YES!
Email sent to boss: "Great day! Sales hit $1,523 today!"
Next day, sales are $800 → IF says NO → no email sent

Example 4: Our Prairie Project (The Real One)#

Goal: Every hour, send new delivery tickets to HaulHub.

        1
2
3
4
5
6
7
8
        WORKFLOW:

  [Schedule Trigger]  →  [HTTP Request]           →  [IF Node]     →  [HTTP Request]       →  [Email]
   Every 1 hour           GET our-api/                count > 0?        POST to HaulHub         Notify Karl
                          haulhub-batch                                  with ticket data        "Sent 15 tickets"
                          ?limit=100
                                                      count = 0?   →  [Stop]
                                                                       "No new tickets"

What happens every hour:

Trigger fires
n8n calls YOUR API to get tickets in HaulHub format
If there are tickets → sends them to HaulHub
If no tickets → does nothing
Emails Karl the result

Nobody has to do anything. It just runs. 24/7. Forever.

Short Answer: NO, but it CAN connect to AI.#

n8n itself is not AI. It's an automation tool. It doesn't "think" or "learn." It follows exact rules you set.

Think of it this way:

        1
2
3
4
5
        AI (like ChatGPT)  = A brain that thinks and generates answers
n8n                = A conveyor belt that moves things from A to B

They are completely different things.
BUT... you can PUT the brain ON the conveyor belt.

How n8n Can USE AI#

n8n has nodes that connect to AI services:

        1
2
3
4
5
6
        EXAMPLE: Auto-reply to customer emails using AI

  [Email Trigger]  →  [OpenAI Node]        →  [Gmail Send]
   New email           "Read this email         Send AI's reply
   received             and write a              back to customer
                        helpful reply"

        1
2
3
4
5
6
        EXAMPLE: Analyze sales data with AI

  [Schedule Trigger]  →  [Database Query]  →  [OpenAI Node]         →  [Slack]
   Every Monday           Get last week's      "Analyze this sales      Post summary
                          sales data            data and give me         to #reports
                                                insights"                channel

So n8n + AI = Powerful Combo#

Without AI	With AI
n8n moves data from A to B exactly as you told it	n8n moves data from A to B, but asks AI to transform/analyze it along the way
"Send this exact email"	"Write a smart email based on this data, then send it"
Can only follow rules	Can make intelligent decisions

For Our Prairie Project: We Don't Need AI#

Our task is straightforward:

Read ticket data
Transform it to HaulHub format (exact field mapping, no thinking needed)
Send it

This is pure automation. No AI required.

6. N8N VS OTHER TOOLS#

n8n is not the only automation tool. Here are the main ones:

The Big Comparison Table#

Tool	Free?	Self-Hosted?	Code Needed?	Best For
n8n	Free (open source)	Yes (or cloud)	Optional	Developers who want full control
Zapier	No (paid, $20+/mo)	No (cloud only)	No	Non-technical users, simple automations
Make (formerly Integromat)	Freemium	No (cloud only)	No	Visual thinkers, complex workflows
Power Automate	Paid (Microsoft)	No	No	Companies already using Microsoft 365
Apache Airflow	Free (open source)	Yes	Yes (Python)	Data engineers, heavy data pipelines
Pipedream	Freemium	No	Yes (JS)	Developers who prefer code
IFTTT	Freemium	No	No	Personal automations (smart home, etc.)

n8n vs Zapier (Most Common Comparison)#

        1
2
3
4
5
6
7
8
9
10
11
12
13
        ZAPIER:
  - Super easy to use (no coding at all)
  - Expensive ($20-$100+/month)
  - You CANNOT host it yourself (their servers only)
  - Limited: you can only do what their pre-built integrations allow
  - Great for: small businesses, non-developers

N8N:
  - Slightly harder to learn (but still visual drag-and-drop)
  - FREE if you host it yourself
  - You CAN host it on your own server (full control)
  - Unlimited: you can write custom code, call any API
  - Great for: developers, companies who need control and custom integrations

Why Karl Chose n8n for This Project#

Free — n8n is open source, no monthly fees
Self-hosted on Hostinger — Karl already has a Hostinger server, so n8n runs there for free
Custom API calls — We need to call our custom API + HaulHub's API. n8n handles this easily
Developer-friendly — Since you're a developer, n8n gives you more power than Zapier
Runs 24/7 — Once set up on Hostinger, it runs forever without anyone touching it

Quick Summary of Each Tool#

Zapier#

        1
2
3
4
5
6
        Best analogy: Uber — easy to use, but you pay for every ride
Pricing: $20-$100+/month
Hosting: Cloud only (their servers)
Difficulty: Very Easy (no code)
Example: "When I get a Gmail, save attachment to Google Drive"
Good for: Non-technical people

Make (Integromat)#

        1
2
3
4
5
6
        Best analogy: LEGO — very visual, snap pieces together
Pricing: Free tier available, then $9+/month
Hosting: Cloud only
Difficulty: Easy-Medium
Example: "When Shopify order comes in, create invoice in QuickBooks, email customer"
Good for: Visual thinkers, medium-complexity workflows

Power Automate#

        1
2
3
4
5
6
        Best analogy: Microsoft's butler — works great inside Microsoft world
Pricing: Included with Microsoft 365, or $15/month standalone
Hosting: Cloud (Microsoft)
Difficulty: Easy-Medium
Example: "When someone submits a Microsoft Form, create a row in Excel, notify in Teams"
Good for: Companies already deep in Microsoft ecosystem

Apache Airflow#

        1
2
3
4
5
6
        Best analogy: Industrial factory machinery — powerful but complex
Pricing: Free (open source)
Hosting: Self-hosted (requires Python skills)
Difficulty: Hard (requires coding)
Example: "Every night, pull data from 5 databases, transform it, load into data warehouse"
Good for: Data engineers at large companies

Pipedream#

        1
2
3
4
5
6
        Best analogy: GitHub for workflows — code-first but visual
Pricing: Free tier, then $19+/month
Hosting: Cloud
Difficulty: Medium (JavaScript knowledge helps)
Example: "When Stripe payment comes in, call my API, update Airtable, send Slack notification"
Good for: Developers who prefer writing code over drag-and-drop

IFTTT (If This Then That)#

        1
2
3
4
5
6
        Best analogy: A light switch — super simple, one trigger, one action
Pricing: Free (limited), $3.49+/month
Hosting: Cloud only
Difficulty: Very Easy
Example: "If it's going to rain, send me a notification"
Good for: Personal use, smart home, simple 1-to-1 automations

7. HOW N8N FITS IN OUR PRAIRIE PROJECT#

The Architecture (Big Picture)#

        1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
                            PRAIRIE MATERIALS SYSTEM
                    ========================

  ┌──────────────┐
  │   TRUCKS     │  Trucks deliver aggregate, cross the scale
  │   & SCALES   │  Scale records weight, creates ticket
  └──────┬───────┘
         │
         ▼
  ┌──────────────┐
  │   SUPABASE   │  Ticket data stored in tkhist1 table
  │   DATABASE   │  (ticketno, weight, customer, product, etc.)
  └──────┬───────┘
         │
         ▼
  ┌──────────────┐
  │   YOUR API   │  Express.js backend (what you built)
  │  (Port 5000) │  - Reads data from Supabase
  │              │  - Joins customer/location/order data
  │              │  - Transforms to HaulHub format
  │              │  - Generates PDFs
  └──────┬───────┘
         │
         │  n8n calls your API on a schedule
         ▼
  ┌──────────────┐
  │     N8N      │  Workflow automation (on Hostinger)
  │  (Hostinger) │  - Runs every hour (or on schedule)
  │              │  - Calls your API to get ticket data
  │              │  - Sends data to HaulHub
  │              │  - Sends PDFs via email
  │              │  - Handles errors, sends notifications
  └──────┬───────┘
         │
         ▼
  ┌──────────────┐
  │   HAULHUB    │  Government compliance platform
  │              │  - IDOT/contractors see delivery data
  │              │  - Prairie gets paid
  └──────────────┘

What Each Piece Does#

Component	Role	Analogy
Trucks & Scales	Create raw data	The factory that makes products
Supabase	Stores the data	The warehouse
Your API	Reads, transforms, formats data	The packaging department
n8n	Orchestrates and schedules everything	The delivery truck driver
HaulHub	Receives and displays data	The customer's store

Why Can't We Just Skip n8n?#

Good question. You technically COULD skip n8n by:

Writing a cron job in your Node.js server
Using setInterval() to run every hour
Having your server call HaulHub directly

But n8n gives you:

Feature	Without n8n (DIY)	With n8n
Schedule management	Write your own cron code	Visual schedule picker
Error handling	Write try/catch, logging code	Built-in error handling + notifications
Monitoring	Build your own dashboard	n8n shows execution history, success/fail
Changing the flow	Edit code, redeploy	Drag-and-drop in browser, no deploy needed
Non-developer friendly	Karl can't modify it	Karl can see and tweak workflows himself
Email notifications	Write email sending code	Drag an email node onto the canvas
Retry on failure	Write retry logic	Built-in retry settings

8. KEY TERMINOLOGY#

Term	Meaning	Example
Workflow	A complete automation from start to finish	"Fetch tickets and send to HaulHub"
Node	One single step in a workflow	"Call the API" or "Send an email"
Trigger	The event that starts a workflow	"Every hour" or "When webhook is called"
Webhook	A URL that starts a workflow when someone calls it	`https://n8n.example.com/webhook/my-flow`
Execution	One run of a workflow from start to end	"The 3 PM run sent 15 tickets"
Credentials	Login info for external services stored in n8n	API tokens, email passwords, DB connections
Expression	Dynamic values using `{{ }}` syntax	`{{$json.ticketno}}` gets the ticket number from data
Self-hosted	Running software on YOUR server, not someone else's	n8n on Karl's Hostinger server
Cloud-hosted	Running software on the COMPANY'S servers	Zapier runs on Zapier's servers
Open source	Code is free and public, anyone can use/modify it	n8n's code is on GitHub for free
API	A way for two software systems to talk to each other	Your API talks to Supabase and HaulHub
Cron	A schedule format (e.g., "every hour" or "daily at midnight")	n8n uses cron behind the scenes

FINAL SUMMARY#

        1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
        Q: What is n8n?
A: A free, visual tool that automates repetitive tasks by connecting services together.

Q: How does it work?
A: You create a "workflow" by connecting "nodes" (steps).
   A trigger starts it, nodes do the work, data flows through like a pipeline.

Q: Is it AI?
A: No. It's automation (follows exact rules). But it CAN connect to AI services.

Q: Why do we need it for Prairie?
A: To automatically send ticket data to HaulHub every hour without anyone doing it manually.

Q: Could we use something else?
A: Yes — Zapier, Make, Power Automate, etc. But n8n is free and self-hosted, which is
   why Karl chose it.

Q: Do I need to learn n8n to do my job?
A: Not deeply. Your job is building the API (which is done).
   n8n just CALLS your API. Karl or someone else can set up the n8n workflows
   using the guide we already created (N8N-WORKFLOW-SETUP-GUIDE.md).

Guide created: February 23, 2026

What is n8n? A Beginner’s Guide to Workflow Automation

What is n8n? - A Complete Beginner Guide

1. THE PROBLEM N8N SOLVES#

Imagine This Scenario#

Now Think About Prairie Materials#

2. WHAT IS N8N?#

The Simple Answer#

The Technical Answer#

Think of it Like This#

What n8n is NOT#

3. HOW DOES N8N WORK?#

The Core Concept: NODES and WORKFLOWS#

NODE = One Step / One Action#

WORKFLOW = Multiple Nodes Connected Together#

How You Build a Workflow (Visual)#

The 3 Types of Nodes#

1. TRIGGER NODES (The Starting Point)#

2. ACTION NODES (The Workers)#

3. OUTPUT NODES (The Destination)#

4. REAL-WORLD EXAMPLES#

Example 1: The Weather Email (Simplest Possible)#

Example 2: New Customer Alert (Webhook)#

Example 3: Daily Sales Report (With Conditions)#

Example 4: Our Prairie Project (The Real One)#

5. IS N8N RELATED TO AI?#

Short Answer: NO, but it CAN connect to AI.#

How n8n Can USE AI#

So n8n + AI = Powerful Combo#

For Our Prairie Project: We Don't Need AI#

6. N8N VS OTHER TOOLS#

The Big Comparison Table#

n8n vs Zapier (Most Common Comparison)#

Why Karl Chose n8n for This Project#

Quick Summary of Each Tool#

Zapier#

Make (Integromat)#

Power Automate#

Apache Airflow#

Pipedream#

IFTTT (If This Then That)#

7. HOW N8N FITS IN OUR PRAIRIE PROJECT#

The Architecture (Big Picture)#

What Each Piece Does#

Why Can't We Just Skip n8n?#

8. KEY TERMINOLOGY#

FINAL SUMMARY#

संबंधित लेख

What is n8n? A Beginner’s Guide to Workflow Automation

What is n8n? - A Complete Beginner Guide

1. THE PROBLEM N8N SOLVES#

Imagine This Scenario#

Now Think About Prairie Materials#

2. WHAT IS N8N?#

The Simple Answer#

The Technical Answer#

Think of it Like This#

What n8n is NOT#

3. HOW DOES N8N WORK?#

The Core Concept: NODES and WORKFLOWS#

NODE = One Step / One Action#

WORKFLOW = Multiple Nodes Connected Together#

How You Build a Workflow (Visual)#

The 3 Types of Nodes#

1. TRIGGER NODES (The Starting Point)#

2. ACTION NODES (The Workers)#

3. OUTPUT NODES (The Destination)#

4. REAL-WORLD EXAMPLES#

Example 1: The Weather Email (Simplest Possible)#

Example 2: New Customer Alert (Webhook)#

Example 3: Daily Sales Report (With Conditions)#

Example 4: Our Prairie Project (The Real One)#

5. IS N8N RELATED TO AI?#

Short Answer: NO, but it CAN connect to AI.#

How n8n Can USE AI#

So n8n + AI = Powerful Combo#

For Our Prairie Project: We Don't Need AI#

6. N8N VS OTHER TOOLS#

The Big Comparison Table#

n8n vs Zapier (Most Common Comparison)#

Why Karl Chose n8n for This Project#