Parts describe the agent. The loop is how it uses them.
How it actually works
The agent loop
Reason → Act → Observe → Repeat. Same loop we walked in Episode 01.
1
Reason
Look at the goal and decide the next step.
2
Act
Use a tool — search, write, send, look something up.
3
Observe
Read what came back. Did it help? Did it fail?
4
Repeat
Decide again until the goal is met — or it must ask you.
The missing word
The harness is the kitchen
The model is the chef. The harness is everything around her: tools, rules, context, and what she is allowed to touch.
ChatGPT
Mostly a table and a conversation. She can talk. She has almost no stove.
Result: an answer
Claude Code
A workshop. Files, terminal, git — Episode 02’s kitchen.
Result: a change in the repo
n8n
A line that can serve. Sheets, Gmail, LinkedIn — and a rule: ask before you plate.
Result: something happens in the real world
In the kitchen
Same chef. Studio apartment, food truck, restaurant. The talent did not change. The knives, the fridge, and the house rules did. That whole setup is the harness.
We are not hiring a smarter chef today. We are building the kitchen.
n8n is the harness
Want the full mental model?
Go back to Episode 01 — The Agentic Trail
Chatbots, assistants, workflows, agents, and when not to build one. Recording and slides are on the episode page.
Scan for the recording
Or open the episode page on your phone. We stay here to build. That session is the map.
Today we connect that loop to n8n — and make it act in the real world.
Before agents
We had workflows
TaskStep 1Step 2Step 3Result
For example
New formSave contactSend emailUpdate CRM
We decide the path.And when we already know what should happen, that is exactly what we want.
In the kitchen
A recipe. Chop, sear, simmer, plate — the same steps in the same order, and the same dish every time.
Step two
When a workflow runs by itself
TriggerStepsResult
Every Monday9:00 AMGoogle SheetsRead next postLinkedInPublish itGoogle SheetsMark as published
That's automation.
Where is the intelligence here?
There isn't any. Every decision was already made — by us, in advance.
In the kitchen
The rice cooker on a timer. You load it at seven and walk away. Nobody is in the kitchen, and it still cooks only what it was set to cook.
Step three
What if different things should happen?
New leadIF
VIPNotify sales
RegularAdd to list
Rule-based automation IF this → THEN that
Who made the decision?
We did — when we wrote the rule.
In the kitchen
A note pinned to the recipe: if a guest is vegetarian, use paneer instead of chicken. The cook follows it — but you wrote it last week.
Step four
Now let's add AI
MessageLLMClassifyWorkflow continues
The model can
UnderstandExtractSummarizeGenerate
Using AI doesn't automatically make something an agent.
Agree or disagree?
In the kitchen
A cook who can taste. She tells you the sauce is too salty, and she is genuinely useful. She still does not decide what is for dinner.
Step five
Now give the AI a goal and tools
Agentgoal + instructions
Research
Create image
Read data
Publish
ReasonActObserveRepeat
Who decides what happens next?
The agent — inside the boundaries we give it.
In the kitchen
You tell a chef: dinner for six at eight, one vegetarian. She checks the fridge, plans the menu, swaps basil for mint when the shop is out, and asks you — chaye or coffee? Then she chooses: chop the ginger, or grind it fresh.
A recipe tells you what to do. A goal tells you what to achieve.
Your turn
Agent or not?
Four scenarios, one at a time. For each one, pick the label that fits it.
A · Workflow
We run it
B · Automation
It runs itself
C · AI-powered
AI does one job inside it
D · Agentic
It decides
Each letter is the right answer exactly once.
Agent or not?
Four scenarios
A workflow · B automation · C AI-powered workflow · D agentic
1You click run. It saves the contact, sends the welcome email, updates the CRM.A · Workflow
2Every Monday at 9, read the next post from a sheet and publish it to LinkedIn.B · Automation
3A new review arrives. AI summarizes the sentiment and saves the summary.C · AI-powered
4“Grow engagement for tomorrow's AI event.” It researches, decides whether an image would help, writes the content, picks its tools, and asks before publishing.D · Agentic
What is fundamentally different about the fourth one?
We gave it an outcome, not a path.
The tool
So where does n8n fit?
AI / Agent
n8n
The real world
Connect AI to the real world.
GmailLinkedInGoogle SheetsSlackDatabasesAPIshundreds more
ConnectOrchestrateAutomate
n8n started as a workflow automation platform. Today it also gives us AI and agent-building capabilities.
In one line
A visual canvas where you connect apps and let AI act inside them
Visual canvas
You drag boxes and connect them. You can see every step and the data that came out of it.
400+ connections
Gmail, Sheets, Slack, LinkedIn, databases, and any API you can call.
AI built in
An AI Agent node that can pick from those same connections as its tools.
Cloud or your own server
Source available. Start on their cloud, self-host later if you want the control.
The same canvas carries a simple automation and a full agent.
Three ways we'll see it
From workflow to agent
1 · Workflow
Trigger → Step → Step → Result
We control the path.
2 · Workflow + agent
Workflow → Agent → Tools → Workflow
AI gets decision-making responsibility inside the process.
3 · Agent-first
Goal → Agent → Search Image LinkedIn
We give it a goal, instructions and tools.
Today we'll see both sides of n8n — not pretend every workflow is an agent.
Reading the canvas
The building blocks of n8n
Triggers
Start the workflow.
Schedule · Webhook · Form · New email
Action nodes
Do something in another system.
Sheets · Gmail · LinkedIn · Slack · Database
AI / agent nodes
Understand, reason, generate or decide.
LLM · AI Agent
Tools
Capabilities an agent can choose to use.
Search · Send email · Query DB · Create image
Control / logic
Control how execution moves.
IF · Switch · Loop · Merge · Wait
Data / transformation
Prepare information between steps.
Edit Fields · Code · Extract · Parse
TriggerProcess / agentTools & actionsResult
Nodes build the system. Tools give the agent capabilities.