Quick answer: Claude Code waits for you. Grok Bot works without you. That one line decides almost every routing question between them, and it is why I run both daily and have never had them compete for the same task.
Before anything else, the correction that half this SERP needs.
Grok Bot is not Grok Build
These are two different xAI products and several pages ranking for this query compare the wrong one to Claude Code without saying so.Grok Build is xAI's coding tool. That is the product that lines up against Claude Code as a coding tool.
Grok Bot is xAI's agent product. Named persistent bots, each with standing instructions, running on a cloud virtual machine.You do not have to take my word for the split, because xAI's own pricing page lists them as separate rows on different plans:xAI's pricing page, captured September 10, 2026. Grok Build ships on every tier including Free. Grok Bot only on the three individual SuperGrok tiers, and not on Business or Enterprise.
Different rows, different availability, different products. If a page tells you "Grok Bot is a terminal coding agent," it has not opened either one.
For the record: I have access to Grok Build and have not used it, so it gets no verdict on this page.
Claude Code waits for you. Grok Bot works without you
The obvious hypothesis is "does the job need my files." That is the line most comparisons draw, and in my setup it is wrong.
Grok Bot has access to my repo. It knows how to pull it, and if my computer is off, it knows how to SSH into my Mac mini.
It is even routing its browsing through that machine, so the bots do not look like bots and get slowed down by captchas. Nothing shady, just not being treated as a scraper while reading public pages.
So "whose files" does not separate them. Both can reach mine.
The real line is what kind of work it is:
Claude takes the content. All of it. Writing, building, the things where judgment about quality matters and I want to be in the loop while it happens.
Grok Bot is the sidekick. It runs analytics on everything. How is the long-form doing, how are the shorts doing, how is LinkedIn doing, how is the newsletter doing. It logs the wins and the losses. When something pops, it tells me. When someone comments on a thing, it logs it and tells me.
Consistent grunt work, on a schedule, that produces a record.Claude Code
Grok BotShape
Task-shaped, resets around each job
Employee-shaped, persistsWhere it runs
Your machine, your terminal
Its own cloud VM, one per accountWhose logins
Yours
Its own, authenticated onceWhen it works
While you are there
On a schedule, without youWhat I give it
Content and building
Analytics, inbox, monitoringWhat happens at 3am
Nothing
The job runsCost
Included on every paid Claude tier
From $30 on SuperGrokFailure mode
Stops
Can keep spendingWhy not just build the grunt work as workflows?
Fair question, and I did, for a long time.
The difference is not capability. It is that a conventional workflow can break silently.
You find out three weeks later that a thing stopped, and by then the ledger has a hole in it. It is also less interactive: you cannot really talk to it.
A hand-built workflow stack is more customizable, and that is a genuine advantage. It is also its problem. It becomes a machine assembled from scraps. Some good parts, some bad parts, some generic parts, all bolted together and none of it fluid.
Grok Bot is one system, same parent, same heart. Everything flows the way it should because it was built as one thing. More unified, less yours.
That tradeoff is the whole choice, and which side you want depends on whether you enjoy owning the plumbing.My Grok Bot roster as captured August 28, 2026. Named bots with standing instructions on one shared cloud machine, not a workflow canvas.What it grew into by September 10: a Chief of Staff bot that the other bots report into. I ask it one question a day.
Has Grok Bot taken a job away from Claude Code for good?
No.
That is the honest answer and I think it is the most useful sentence on this page, because it is not what a launch-week comparison would tell you.
Grok Bot did not take work off Claude Code. It picked up work that was not happening at all.
The analytics ledger did not exist before. The inbox got triaged by me, badly, or not at all.
Nothing migrated. Something new started.
The thing that makes me think that could change: Codex has genuinely surprised me lately, to the point of generating a tweet. Which makes me suspect the next Grok model might eventually take on work I currently keep on Claude. That model is not out and I am not going to pretend to know what it does.
For now: no job has moved, and I do not switch between them mid-task. I use both.
Where Claude Code actually lives
The mirror image of the roster above is that Claude Code is not a roster. It is a session in a terminal on my machine, plus Cowork as its non-terminal sibling in the desktop app.Claude Code and Cowork in the Claude desktop app. Same brain, two cockpits, both attached to my actual machine and my actual files.
And the honest caveat about the terminal: when I finally got into Claude Code it clicked immediately, but I am used to looking at a terminal window. I do not recommend that for everybody. If the terminal is the blocker rather than the capability, the fork you want is Cowork vs Claude Code, not this page.
Cost and risk, which are not symmetrical
Claude Code is included on every paid Claude tier. Pro at $20, Max 5x at $100, Max 20x at $200, per Anthropic's Max plan page and claude.com/pricing. You are not buying Claude Code, you are buying capacity for it. When you run out, it stops.
Grok Bot is included from $30 on SuperGrok, per xAI's pricing page as of September 10, 2026. Each eligible plan carries a weekly Grok Bot allowance, and overage is reported to bill from model and token cost with no Grok Bot specific spend cap yet.
That asymmetry deserves a sentence of its own. One of these fails by stopping. The other can fail by spending, unattended, at 3am. I have not been surprised by a bill, and I would still watch it closely for a first month.
There is a second risk that is structural rather than financial. All your bots share one cloud machine, along with its logins and its files.
That is convenient, and my read of it is that the bots are not meaningfully isolated from each other. Whatever one bot can log into, you have effectively handed to the whole roster. Scope what you connect accordingly.
Claude Code's risk profile is the opposite and more familiar: it is on your machine, in your files, and the blast radius is local.
Which one to start withYou want an agent doing something useful by Friday and you do not code. Grok Bot. Pick one job you do at the same time every day and hate. Not nine.
You want to build or write things and be in the loop. Claude Code, on any paid Claude plan you already have. And if the terminal is the problem, Cowork.
You are comparing coding tools specifically. Then you want Grok Build against Claude Code, not this pairing.
AI does real work in your week. Both. I do.The reason for "both" is not greed. There is no AI that does it all, and if you are running a business on this you do not want to rely on one. They get cancelled, they get rate limited, they go down, they get changed underneath you. Two vendors means one bad day is not your bad day.
If I were being properly serious about it, the most important jobs would run locally on hardware I own, with the paid frontier models sitting on top for the heavy thinking. Then a subscription change is an inconvenience rather than an outage. I am not there yet. I am running on paid models and I know that is a risk I am choosing.
The neighboring comparisons: Grok Bot vs Claude Cowork if you are choosing between the two agent products, what is Grok Bot for the week-one field test, Grok Bot use cases for the full roster and what each bot produces, and Grok vs Claude if you actually meant the models. More at Claude at Work.
Published and last reviewed September 10, 2026. The Grok Bot and Grok Build plan rows were read and captured that day from xAI's pricing page, screenshotted above. Grok Bot's VM, login and connector mechanics were verified for my week-one field test on August 28, 2026. Claude Code tier inclusion and Claude plan prices were verified for Claude Max 5x vs 20x against Anthropic's Max plan support article and claude.com/pricing. The routing rule, the repo and SSH setup, and the "no job has moved" answer are my own, from my own accounts. The overage-billing point is secondary reporting and labeled as such. A published head-to-head benchmark circulating for this pairing was left out because I could not trace it to the benchmark's own publisher.
Quick answer: these two do not compete, and every page comparing them is comparing the wrong layer. GPT-6 Astra is a model you hand hard work to. Grok Bot is a set of agents with their own computer that run standing jobs while you are asleep. I pay for both and they have never once contended for the same task.
Every result ranking for this pairing is an API aggregator: tokens per second, dollars per million, intelligence index. Useful if you are building software. Useless if you have two subscriptions and one Tuesday.
So here is the version for someone with two subscriptions and one Tuesday.
The category error, first, because it decides everythingGPT-6 Astra
Grok BotWhat it is
A model
Named persistent agentsWhere it runs
Your ChatGPT session, in Work or Codex
Its own cloud virtual machineWhose logins
Yours, in your browser
Its own, authenticated onceWhose files
Whatever you give the session
Its machine, under /workspaceWhen it works
While you are there
On a schedule, without youWhat happens at 3am
Nothing
The job runsHow it is billed
Inside your plan allowance
Weekly allowance, then reported overageRead the last two rows again. That is the entire decision.
Astra is the better thinker in this pairing. But it has never once told me something while I was doing something else.
What Astra actually ran for me
Astra shipped September 3, 2026. OpenAI describes it as state-of-the-art on computer use, browsing, software engineering, cybersecurity, science and professional work, with a context window over a million tokens.
In my week it does two things.
Research, and challenging Claude. It is genuinely good at pushing back on Fable when I want a second opinion on something I already believe. That is a real job and it is worth paying for. Smart enough that the disagreement is worth reading rather than annoying.
And this week, a game. The demos of people building games with Astra are real and I wanted in, so I spent a weekend on a Pokemon-style game. The graphics it generated genuinely stunned me. The game did not get built. Between that and my first week of running maximum effort on everything, I burned through two full allowances and produced something ugly.
That is not a knock on the model. I did not ask it the right way and the learning curve is real. But I want it next to the demo reels, because the demo reels are all successes.Astra running in ChatGPT Work on my Pro $100 account. Note the surface: on Plus, Astra appears only in Work and Codex, never in the Chat picker.
The honest cost note: at $100 I feel the ceiling for the first time. With GPT-5.6 Sol I felt it a little, but it was manageable. This is not.
If you want to build something serious with Astra, my read is you want the $200 plan. At $100 you miss out.
What Grok Bot actually ran for me
Grok Bot launched August 11, 2026. Named agents, each with standing instructions, sharing one cloud machine per account along with its logins and files.
I use it for orchestration. Analytics, publishing, intelligence, all happening in the background.
Every day, my inbox. Starting at 9am, about three times a day, a bot checks and manages it. I do not open it to triage. I open it to read what is left.
Every day, my numbers. A folder of bots scrapes my own analytics roughly three times a day and writes to a ledger. Shorts, newsletter, LinkedIn, comments. Wins and losses get logged rather than remembered. I am no longer posting blind, which sounds small and changed how I work more than any model upgrade this year.
Anything that drops in my space. A news scout watches X. Yesterday it told me OpenAI had shipped a new image generation model, and it was right that it mattered. We are now looking at integrating it into our YouTube thumbnails. That is a bot changing what I did with my afternoon.
And the sniper job. When I see a tweet I want a take on, I dump it into Grok Bot. It reads it instantly because it lives where the tweets are. Pasting that into a Claude chat is a headache. I do not want to open a terminal just for that. This is the fastest path from "interesting" to "what do you think."My account today. Inbox Hawk runs three passes a day on a routine and pings me with only what needs a human. That is the job Astra does not have a shape for.
The benchmark parity, compressed, because it should not decide this
Since somebody will ask: on Artificial Analysis, Astra and Grok 4.6 both sit at Intelligence 61. Astra's context is larger, Grok 4.6 is marginally faster, and API prices differ substantially in Grok's favor. Those are third-party figures and I am reporting them, not endorsing the methodology.
None of it should move you, for one reason: you are on a plan, not an invoice. Price per million tokens describes a bill you will never receive.
And you are not choosing between two models anyway. You are choosing between a model and an employee.
The billing asymmetry nobody prints
This is the most practical difference on this page and I have not seen it anywhere else.
ChatGPT stops you. When your allowance runs out, you wait, use a banked reset, or buy credits deliberately. The worst case is frustration.My ChatGPT meter, September 10, 2026. A ceiling, a reset date, and a $0 balance with auto-reload off. The failure mode here is that work stops.
Grok Bot bills you. Each eligible plan includes a weekly Grok Bot allowance, and extra usage is reported to be billed from model and token cost with no Grok Bot specific spend cap yet. A scheduled agent running unattended with no ceiling is a different category of risk from a subscription that simply stops.
One of these fails by stopping. The other can fail by spending. Watch the second one for a month before you trust it with a schedule.
On price itself, the record needs correcting. Grok Bot is included from SuperGrok at $30, per xAI's pricing page as of September 10, 2026.
Secondary coverage still ties it to SuperGrok Heavy bundling at around $300, and Reworked reported exactly that at launch. Whatever was true then, the page today says otherwise. It is also, notably, not listed as included on Business or Enterprise.xAI's pricing page, September 10, 2026. Grok Bot on the three individual SuperGrok tiers, and not on the two a company would buy.
If you can only pay for one
I asked myself the real version of this: if I had to cancel one tomorrow, which goes?
Astra goes. And I want to be clear that this is not a verdict on quality, because Astra is great and I would miss it and I would have to work out what to do about that.
Which sounds like it contradicts my own buying order above, and it does not. If you have neither, buy the model first, because a model is useful on day one and an agent is useful once you have taught it a job. I have already done that teaching. That is the whole difference.
Grok Bot is serving a more important purpose right now. Tracking the analytics, keeping things updated, doing the things I would otherwise not do. Losing Astra costs me a very good research partner and a sparring opponent. I would feel that. Losing Grok Bot means a category of work simply stops happening in my business.
The way I keep describing the difference: a conventional automation is like a teddy bear you have to move yourself. The moment you stop moving it, it dies. Occasionally it gets up on its own to do a boring chore, and sometimes it trips and falls and stays down. Grok Bot plays on its own, walks more smoothly, and when it falls it can get up or call one of the other bots for help.
That is a feel, not a benchmark. It is also why I would cancel the smarter one first.
So which do you buy?You mostly ask questions and want better answers. Neither of these. You want a good chat plan, and that is ChatGPT Plus or Claude Pro.
You have hard, long, multi-step work. Astra, on ChatGPT. And if you intend to build something serious with it, budget the $200 tier, because $100 has a ceiling you will meet.
You have recurring jobs you do at the same time every day and resent. Grok Bot, from $30. Start with one bot, not nine.
AI does real work in your week. Both, in that order. And honestly, for a reason beyond capability: running two vendors means one closed meter does not end your day.There is no AI that does it all. If you are running a business on this, do not rely on one. If I were making real money from it, I would be on the top tier of all of them and consider it a no-brainer, because it makes the money back.
The neighboring decisions: what GPT-6 Astra actually is, which ChatGPT plans get Astra, what is Grok Bot for the week-one field test, and Grok Bot use cases for the full roster. If your comparison is really against Claude's assistant, that is Grok Bot vs Claude Cowork. More at Claude at Work.
Published September 10, 2026. Grok Bot plan inclusion was read and captured that day from xAI's pricing page, screenshotted above. Grok Bot's VM and connector mechanics were verified for my week-one field test on August 28, 2026. Astra's launch description and context window come from OpenAI's September 3 announcement as captured on September 4; OpenAI's pages could not be fetched directly on September 10 and those facts are not re-dated. The benchmark parity figures are Artificial Analysis's published index, reported as third-party. The overage-billing point is secondary reporting and labeled as such. Screenshots are my own paid accounts, sidebars cropped. Grok 4.7 is unreleased and is deliberately not discussed anywhere on this page.
Quick answer: Grok Bot is for standing jobs, not questions. If a task happens on a schedule, produces something you check later, and does not need files on your laptop, it belongs to a bot. If you would rather just ask and read the answer, use the chat.
Everything ranking for this query is a list of 35 or 50 hypothetical use cases assembled from launch-week hype. Useful for ideas. Nobody behind them has run one for a month.
I have. Here is my actual roster, what each job produces, the one that flopped, and the one I would cancel first.
First, the price thing, because it is wrong everywhere
The most repeated claim about Grok Bot is that it requires a $300 SuperGrok Heavy subscription. Whatever was true at launch, it is not true today, and I can show you the page.xAI's pricing page, captured September 10, 2026. "Grok Bot access" is a listed feature of the $30 SuperGrok tier.
And the feature matrix on the same page has a row that nobody has written about:Same page, same day. Read the Grok Bot row across all seven columns.
Two things fall out of that row:Grok Bot starts at $30, on SuperGrok. Not $300.
Grok Bot is not listed on Business or Enterprise. The two plans a company would actually buy are the two that do not get the agent product. Grok Build, the coding tool, is on every tier including Free. Grok Bot is not.If you are evaluating this for a team, that is the fact to check before anything else on this page.
I pay for SuperGrok Plus at $100 myself, for the headroom rather than for access.
The one-line test for whether a job belongs to a bot
Before the list, the filter I use. A job goes to a bot when all three are true:It repeats on a schedule you could write down.
It does not need files on my laptop. The bot lives on its own cloud machine.
I can check the output later instead of watching it happen.Fail any one of those and it is not a bot job. That third one is the one people skip, and it is why half the use-case lists on the internet describe things nobody could actually verify.
The three folders
I group everything into growth, publishing, and intelligence. Not because the product asks for folders, but because those are the three things I need to happen without me.My account today, September 10, 2026. Inbox Hawk runs three passes a day on a routine, then pings me with only the items that need a human. The message body is blurred because it is my actual inbox.Chief of Staff on the same day. The other bots report into it, and I ask it one question instead of reading each feed.
One mechanic worth knowing before you build a roster: every bot on your account shares one cloud virtual machine, along with its logins and its files. You authenticate once and the whole team inherits it. Durable work belongs under /workspace, because files elsewhere can disappear during recovery.
That is convenient and it is also the security story. My read of that architecture, and it is a read rather than something xAI documents: your bots are not meaningfully isolated from each other. Whatever one of them can log into, you have effectively granted to the roster. Scope what you connect accordingly.
Folder 1: Growth (the ledger)
These exist so I stop posting blind. They scrape my own analytics roughly three times a day and write to a ledger.Bot
What it doesShorts Hawk
Watches short-form performanceSubstack Hawk
Watches newsletter performancePlan Watch
Tracks changes to AI plans and pricingBank Pull
Pulls financial numbers on a scheduleComments
Tracks comments across platforms and tells me when someone is talking to meLinkedIn Hawk
Watches LinkedIn performanceAll six scrape on a schedule, roughly three to four times a day, and write what they find into a ledger.
The point of this folder is not the dashboards. It is that the wins and the losses get logged rather than felt. Before this, I was guessing about what worked from memory, which is the worst analytics system ever built.
Folder 2: PublishingBot
What it doesYouTube long-form uploader
Takes a finished video and gets it publishedSubstack Notes publisher
Posts notes without me opening the appThis is the folder that does something I genuinely could not do before. Not "did it faster." Could not do at all, because it happened at a time when I was doing something else.
Folder 3: IntelligenceBot
What it doesChief of Staff
Oversees the other bots, surfaces what mattersInbox Hawk
Checks and manages my inbox, starting at 9am, about three times a dayNews Scout
Scrapes X for anything that drops in my spaceDistribution Scout
Watches videos I follow and summarizes them my wayNews Scout is the one that changed how I work. Yesterday it told me OpenAI had shipped a new image generation model, which I agreed was a big deal, and we are now looking at integrating it into our YouTube thumbnails. That is a bot changing what I did with my afternoon.
Distribution Scout is the newest one and it has earned its keep fastest. It watches long videos for me and gives me summaries in the format I want, which is not the format any summarizer app gives you.
What is actually good about this, versus a normal automation
I have built the same kinds of jobs before with conventional workflow automation, and the difference is not capability. It is persistence.
A normal automation is a cron job wearing a costume. When it breaks, it tends to break silently, and you find out three weeks later that a thing stopped. A Grok Bot has a good enough sense of its own job that it keeps going, and when it trips, it can pick itself up or escalate.
The way I keep describing it: with a normal workflow, you have to move the thing yourself, and the moment you stop moving it, it dies. It will occasionally get up and do a boring chore, and sometimes it falls over. Grok Bot plays on its own, and when it falls it can get up, or call one of the others for help.
That is a feel, not a benchmark. But it is the reason I stopped rebuilding these as workflows.
The tradeoff is control. A hand-built workflow is customizable to its exact purpose, which is a real advantage, and also its problem: it becomes a machine assembled from scraps, some good, some generic, none of it fluid. Grok Bot is one system with one heart. More unified, less yours.
The honest part: what is not working
I would rather you get this from someone who pays for it than from a listicle.
One flopped outright. In week one I built a lead scout and it produced nothing. The product moved a boundary. It did not become magic.
Shorts Hawk is buggy. It is in the roster and it is not reliable yet.
News Scout is a little rough. Not broken, just inconsistent enough that I read its output with suspicion.
LinkedIn Hawk is the one I would kill first. If xAI doubled the price tomorrow, that is the one that goes. It is fun to watch and I could not honestly tell you what it is doing for me. Writing this page was a decent audit trigger, which is its own lesson: building the plumbing is the easy part, and then you let it run and stop asking whether it earns anything.
Chief of Staff and Inbox Hawk are the ones that stay. Inbox Hawk is not impressive and it has held up. Chief of Staff is managing everything else, which is the job I actually needed.
And the billing risk is real. Each eligible plan includes a weekly Grok Bot allowance, and extra usage is reported to be billed from model and token cost, with no Grok Bot specific spend cap yet, per eesel's pricing writeup. A scheduled agent with no ceiling is a category of risk that a fixed subscription does not have. Watch it closely for the first month.What I actually pay xAI. SuperGrok Plus, for the headroom.
What everyone else runs
The community inventories are genuinely useful for ideas, and I would rather point you at them than pretend I invented the category:Matt Van Horn's 30-day sweep of what people across X, Reddit and YouTube actually use it for.
Sid Saladi's 50-use-case inventory, the most-cited list out there.The categories that recur across the community lists generally, beyond what I run: inbox triage and cleanup, meeting prep, supplier and vendor outreach, dispatch and logistics coordination, and permit or paperwork chasing for trades businesses.
I am deliberately not retelling the individual operator stories that circulate with those lists. Several are compelling and I could not trace them to an original post I could link, so they stay off this page. If you find them, judge them yourself.
How to steal this
If you want one bot by Friday, do this:Pick the job you do at the same time every day and resent. Inbox triage, most likely.
Write the job in three sentences. If you cannot, the bot will not do it well.
Give it a schedule, not a trigger. Standing jobs beat clever ones.
Make it write somewhere you will see. A ledger, a doc, a message. Output you never read is a bot that does not exist.
Audit it in 30 days. Ask what it produced. Kill it if the answer is thin. Mine would not all survive that question, which is the point.The mistake is not building the wrong bot. It is building twelve and never asking any of them what they did.
Deciding whether the product is for you at all? What is Grok Bot is the week-one field test, Grok Bot vs Claude Cowork is the assistant comparison, Grok Bot vs Claude Code is the one for people who already run an agent, and Grok usage limits explained covers the meters. The equivalent collection on the other side is Claude Cowork use cases. More at Claude at Work.
Published September 10, 2026. The plan tiers that include Grok Bot, including its absence from Business and Enterprise, were read and captured that day from xAI's pricing page, screenshotted above. The one-VM-per-account mechanic and the connector catalog were verified for my week-one field test on August 28, 2026. The roster, the bots and the verdicts are my own paid SuperGrok Plus account. The overage-billing point is secondary reporting and is labeled as such. Community operator anecdotes I could not trace to an original source were left out rather than repeated.
Quick answer: stop asking which one wins. They sit in different rooms of your life. Grok Bot is a teammate with its own computer in xAI's cloud that you text from your phone: monitoring, scraping, routines, the always-on stuff. Claude Cowork is the worker at your actual desk, inside your real files and projects, where careful work happens. I pay for both, $100 SuperGrok Plus and a paid Claude plan, and I use both daily. Here is the split as I actually live it.
The Ship Lean split, if you want it in one line: Grok Bot carries your pocket. Cowork carries your desk.
Published August 28, 2026. Last reviewed August 2026 against xAI's and Anthropic's live pages.
Quick decisionYour situation
PickYou want an assistant you text from your phone that works while you sleep
Grok BotYour work lives in documents, folders, and real projects on your machine
Claude CoworkYou bounced off agent tools because setup was too technical
Grok BotYou already pay for Claude Pro or Max
Cowork first; it is already included$30 is your whole experiment budget
Grok Bot on SuperGrokYou are actually choosing between the chatbots
Different page: Grok vs ClaudeGrok Bot is a cloud teammate with its own computer and its own usage pool
Launched August 11, 2026, early beta. Per the launch post: "your team of always-on agents. They have their own computer, work inside tools and apps like you do, and keep working 24/7." The computer is a real machine in xAI's cloud, so jobs do not stall when you step away. You teach a bot by doing a workflow once while it watches; it saves it as a routine and reruns it on its own.
Two facts every comparison page misses, both official:Entry is $30, not $200. xAI's pricing page lists "Grok Bot access" on the SuperGrok tier as of August 28. The enterprise-paywall story ranking around the web is stale.
Its usage is separate. The launch post states bot work "won't count against your existing usage." That matched my week: bots running, chat usage untouched. Details: Grok usage limits explained.Access rides SuperGrok or Cursor plans; the closest OpenAI equivalent is ChatGPT Work, covered in Cowork vs ChatGPT Work.
Claude Cowork is the worker inside your own files, and it now has its own browser
Per Claude's Cowork page: give it a goal and "it works across your files and tools," then delivers work for review. It ships on every paid Claude plan from $20 Pro up, on macOS and Windows desktop, web, and iOS and Android.
And the objection everyone still repeats is dead: Cowork now has a browser built into it, separate from your own logins and tabs, and scheduled tasks run unattended with your laptop closed. If your mental model of Cowork is six months old, it is wrong. Where it sits next to Claude's coding tool is its own question: Claude Cowork vs Claude Code.
Where Grok Bot wins: the pocket and the clock
My real setup after week one: a bot called Partner manages a small team, with each bot on its own computer with its own skills. They read my channel analytics and come back with specific calls. Another bot scrapes AI news for me three times a day. I built all of it in plain English, and I check on it from my phone. (Full week-one story with the roster screenshot: What is Grok Bot.)
This is the OpenClaw dream with the pain removed. OpenClaw was the first "AI on the go" moment and I loved it, but it was buggy and daunting for most people. Grok Bot is that idea with an actual dedicated computer, a stronger model, a genuinely good mobile app that syncs with desktop, and a dedicated usage pool. For the people who could not survive OpenClaw setup, this is the answer, hands down.The pocket side of the split: my real bot team in the Grok Bot macOS app, captured August 28.
Where Cowork wins: the desk
Here is a real Cowork session from my week, not a hypothetical:Cowork watched a 48-second screen recording of a workflow I do by hand, then drafted a reusable version of it and put it up for my approval. It also caught a conflict between two of my own saved preferences and told me which one it followed.
Read what is happening in that screenshot, because no feature grid captures it. Cowork watched me work for 48 seconds, understood the outcome rather than the clicks, proposed a permanent automation, and flagged a contradiction in my own preferences. That is judgment inside my actual system, with my actual files.
That is the lane where, in my week, Grok Bot lost to Claude. When the task was deep, multi-step, and touched things I care about, I did not even consider handing it to a bot in someone else's cloud. Claude is stingier with usage, and that is a real cost I feel, but one 48-second recording turning into a reusable skill is work no phone bot did for me all week.
New to running Claude as a work tool? Start here: Claude at work.
The honest costs on both sides
Grok Bot's honest costs: it is early beta and acts like it. My lead-scout experiment produced nothing in week one and I may kill it. And its whole model means your logins live on a cloud computer that acts as you; think before you hand it accounts that matter.
Cowork's honest costs: Claude usage. Anthropic is the stingy one of the two, and even the current 50% usage boost is an extension, not a promise. Meanwhile my Grok limits have reset weekly, sometimes more than once, and bot work does not touch the chat pool. If your bet is "who gives me more machine per dollar," xAI is playing that game harder. If it is "who does the most careful work," that is Claude.The receipt for the usage claim: my SuperGrok Plus billing screen, August 28, "Reset Available" badge showing.
The comparison creators are circling the same fight: Simon Scrapes titled his review "Did Grok Bot Just Overtake Claude?" and Riley Brown ran a three-way super-app test. Watch both; notice that the disagreement is always about which room of your life the tool sits in.
Claude Cowork vs Grok Bot: which one to start withYou already pay for Claude: open Cowork today; it is in your plan. Start with one folder and one recurring task.
You do not pay for anything yet and want the assistant feeling: SuperGrok at $30. It is the cheapest real agent on the market right now.
You are me, running a one-person operation around a full job: both, split by room. Pocket work to Grok Bot, desk work to Cowork, and neither subscription resents the other.How I know what is on this page
Product facts: xAI's launch post and pricing page, and Claude's official Cowork pages, all read August 28, 2026, dated on my AI plan tracker. The verdicts: my own two paid accounts and my own week, including the Cowork session screenshot above and the bot team on the Grok side. Where a claim is mine and not official, like how my own bots behave day to day, I have said so.
Quick answer: Grok Bot is xAI's AI teammate product, launched August 11, 2026, still labeled early beta. Each bot gets its own computer in the cloud, signs into your tools, and keeps working after you close your laptop. It starts at $30/month, and its work does not count against your Grok chat usage. I pay for it, I built a small team on it in week one, and it is the first agent product I would hand to a non-technical person, beta caveats included.
The Ship Lean read, in one line: Grok Bot rents your assistant a computer, Claude works in your files, and the $30 tier is the whole story.
One naming correction before anything else, because it burns people in search: this is not the @grok bot that replies to tweets. Same company, different product. This one you hire.
Grok Bot Is an Assistant With Its Own Cloud Computer, From $30Question
AnswerWhat is it
AI teammates with their own cloud computers, from xAILaunched
August 11, 2026, early beta, per the launch postCheapest way in
SuperGrok at $30/month lists "Grok Bot access" on xAI's pricing page, checked August 28Where it runs
Desktop app (macOS .dmg) plus iOS; it syncs between themUsage
Separate pool; bot work does not drain your Grok chatWho it is for
People who want an assistant that works while they sleep, without setup pain"Its own computer" is the whole product
Every explainer repeats the phrase and never translates it. Here is the translation.
Your bot lives on a machine in xAI's cloud. It stays awake when you step away, signs into websites and apps there, and works "including platforms with no clean API or MCP" in xAI's own words. You teach it by doing a workflow once while it follows along; it saves the routine and runs it on its own next time.
Bots can even message each other and coordinate.
That is also the honest part nobody says out loud: your logins end up on a cloud computer that acts as you. HN user wiradikusuma asked the exact right question: "How does it work with login-walled sites like LinkedIn then? And what does 'own computer' mean?" The answer is: it works because the computer is real, and you should think before handing it accounts you care about.
I Built Three Bots in Week One, and One Flopped
I am on the $100 SuperGrok Plus plan, and I spent the week attacking my own gaps. Three builds:My actual bot roster in the Grok Bot macOS app, captured August 28. Partner runs the team. Each bot has its own skills and access to my data, and per xAI's docs they all share one persistent cloud computer scoped to my account, which is why a single login covers the whole roster.
A mini marketing team that watches my analytics. My gap is that I make content constantly but only review the numbers for one channel. So I built Partner, a co-founder bot that manages a small team: Friday, Tweet, Steal, and Coach. They read my actual channel data and come back with specific calls: this dropped, steal this video, this flopped because of that.
A mini team hawking my analytics, telling me what to improve every week.
A news scraper. Three times a day it collects the latest AI drops for me. It already cleaned up some of my lists. Simple, boring, exactly what an assistant should do.
A lead scout, which flopped. I pointed a bot at my services page and told it to find my ideal clients and start conversations. First week was a dud. I might drop it. I am telling you this because it is an experiment, not a system, and any page that only shows you wins is selling something.
The thing that actually surprised me: the usage math
I hit my usage limit on the $100 plan this week. Then it reset. In my experience the resets land weekly, sometimes more than once, though xAI does not publish that schedule anywhere. Meanwhile the launch post says Grok Bot "comes with its own usage, separate from your Grok and Cursor plans."
Two pools, one price. The careful version of that claim, with the official quotes and where the docs go quiet, is in Grok usage limits explained.The other half of the subscription: Grok chat running a live "what's trending" search on my desktop, captured August 28. Chat and Bot are separate products on separate meters.
This is the OpenClaw idea, shipped properly
If you remember OpenClaw, that was the first "AI on the go" moment: amazing when it worked, buggy and daunting to set up. Grok Bot is that idea as version 2.0: an actual computer instead of your session, a stronger model (Grok 4.6), a real mobile app that syncs with the desktop, and a dedicated subscription instead of duct tape.
I am not alone in that read. HN user thenbrent put it as: "Right now Grok Bot looks a lot easier to get started and maintain with a simpler UI (arguably better), but OpenClaw and Hermes give you more configurability and choice." That is the honest trade: easier and more polished, less control.
It Starts at $30, Not the $200 Reddit Says
The launch had real pricing confusion, and stale answers are still ranking. Reddit threads claim it needs $120 per seat or a $200 to $300 plan. As of August 28, xAI's pricing page lists "Grok Bot access" on the $30 SuperGrok tier, with SuperGrok Plus at $100 for much higher usage. During the beta, the Bot docs and the pricing page have not always agreed on tiers, and HN user gexla called that out directly: "This is super confusing."
So the practical rule: read the pricing page the day you buy, not a blog post from launch week, mine included. I keep the receipts dated on my AI plan tracker, and my own billing screen is on the worth-it breakdown:My actual billing screen, August 28: SuperGrok Plus, $100, paid August 21. Note there is no published price for Lite or Heavy anywhere on it.
Who should get it, who should not
Get it if you want a personal assistant, not a coding partner. The pitch that lands with normal people is: for $30 budgeted deliberately, you get an assistant with its own computer, on your phone. Tailored news pulls, monitoring, reminders, the boring recurring stuff. For people who bounced off agent tools because setup was too technical, this is the answer, hands down.
Skip it if your work lives in your files. My deep work still happens in Claude, where the agent works inside my actual projects on my actual machine. That comparison gets its own page: Grok Bot vs Claude Cowork. If you are deciding between the model chatbots themselves, that is Grok vs Claude and Grok vs ChatGPT. And for where any of this fits into an employed person's week, start at Claude at work.
Wait if beta bugs scare you. It is labeled early beta, and it earns the label sometimes. My lead scout produced nothing in week one. The product moved a boundary; it did not become magic.
How I know what is on this page
Product and pricing facts: xAI's launch post, bot page, and pricing page, all read August 28, 2026, dated on the tracker. The builds and the usage story: my own paid account, with the bot roster screenshot above from my actual desktop app. The skepticism: Hacker News users quoted verbatim with links, because the confusion is part of the truth of a two-week-old product.
Quick answer: Use Codex when the work lives in a repo and needs judgment, editing, tests, or codebase context. Use n8n when the work needs a trigger, credentials, retries, run history, and repeatable automation. The Ship Lean rule is simple: Codex builds. n8n runs. Human approves.
Here is the receipt behind that rule: I moved about 47 n8n nodes into code, and I kept exactly one workflow running in n8n. Not zero. One. Which one survived, and why, is the most useful part of this page.
Heads up: some links in this post are affiliate links, a small kickback to me at no cost to you. I only recommend tools I've actually run.
Searching for "n8n codex" or "codex with n8n"? You usually do not pick one. You connect them: n8n owns the trigger and the routing, Codex does the build step that needs judgment, and a human approves before anything ships. Jump to the best pattern for the exact split.
Start with the n8n AI Agents hub if you want the whole system. If the workflow specifically needs an n8n agent, use the n8n AI Agent Workflow Builder before touching the canvas.
If you want the templates behind this split, use the public Claude Code Systems Kit. It covers repo-aware builder work, local agent runs, n8n approval gates, and workflow specs.I walk through this on camera in How I Use Claude Code + n8n to Automate What AI Can't (9 min).The Difference in One TableQuestion
Codex
n8nCan it read and edit repo files?
Best
WeakCan it run tests and inspect diffs?
Best
WeakCan it trigger from forms, webhooks, schedules, and apps?
Possible
BestCan it manage app credentials cleanly?
Not the job
BestCan it retry failed workflow steps?
Possible with scripts
BestCan it show run history?
Not the job
BestCan it draft, refactor, and QA content/code?
Best
Needs LLM nodesCan it route human approvals?
Possible
BestThis is why the comparison is not "which tool is smarter?" It is "which tool owns which layer?"The whole split on one card. The pattern that wins uses both.
What I Actually Moved, and the One Thing I Didn't
I ran a serious n8n setup. For content it was genuinely good: it would write, it would post, it would call APIs. I am not going to pretend it was bad. It was impressive when it worked.
Then I moved almost all of it into code.
The reason is the 47-node problem. A complex process might be 47 steps on a canvas. Step one is "scrape this," which is easy enough. But then it is do this, then do that, and now you are embedding complex prompts inside an agent node and wiring specific tools to it.
It takes an hour to build something you could have tested and shipped in that same hour as a skill. And those 47 nodes become one file with far less to maintain.
But I kept one workflow, and it is still running.
It is a scheduled scraper running on a Mac mini. That is exactly the kind of work n8n still does well: very deterministic, scheduled, and cheap enough that the cost never comes up. There was no reason to move it.
That one survivor is the honest boundary of this whole argument. My work moved to code because it was agent-shaped, not because connectors and runners are obsolete. My automation was mostly "think, then write, then decide," which is terrible canvas work and great agent work.
The scraper is the opposite: no judgment, fixed rules, runs on a timer. Code would not make it better. It would just make it mine to maintain.
Check what shape your work is before you copy me.
Is n8n Still Worth Learning in 2026?
This is the question the threads are actually asking, and most comparison pages dodge it. So here is a straight answer.
For most people: no. Do not spend your time there.
If you had asked me a year or two ago, that was the thing to learn. People who knew n8n had a real edge with AI. Today you do not get that edge from it. It is good to know the fundamentals of how automation is shaped, triggers, credentials, retries, approvals, but you can learn that concept in an afternoon without becoming an n8n specialist.
The doubt is widespread among people who invested heavily. One r/n8n post opens: "For the past ~6 months I went all in on n8n. Built a pretty comprehensive 12-hour course (from zero to building quite advanced AI agent workflows)..."
One real exception, and it matters. If you are a business currently running on Zapier, n8n probably still has the edge. It is a little more daunting visually, but it is easier and cheaper to build in once you are past the first hour. That migration is still worth doing.
What n8n does not have anymore is the edge for modern workflows. That is a different claim from "n8n is dead," and the scraper on my Mac mini is the proof of the difference.
Which Agent Should Build Your n8n Workflows?
People argue about this constantly and I use both tools daily, so let me settle it as far as I honestly can.
First, the honest disclosure: I do not build n8n workflows anymore. If I am building a workflow, I am building it in code with Claude or Codex.
But if I genuinely needed one, here is my method, and it is not the one most tutorials sell.
Having AI generate the n8n workflow JSON is a gamble. It comes out clunky, and some of it does not work. You end up debugging someone else's generated structure, which is slower than building it yourself.
So: build it yourself in the canvas, and use Claude to plan the nodes and QA the result. That is faster for me than debugging generated JSON, every time.
The community lands in the same place on model choice. From an r/n8n thread on which agent to use: "Claude is consistently better. Stick with Claude Code. Codex or Gemini will not be more effective."
One update worth knowing if you work outside the editor: there is a first-party n8n CLI. Per n8n's own docs it is "a lightweight command-line client that communicates with a running n8n instance through the n8n API," and it can list and inspect workflows, create a workflow from JSON, check recent executions, create a credential, and manage projects.
Worth knowing what it is not. It is an API client, not a full workflow-as-code system, and its export and import command is still marked preview. So it makes scripting and inspection genuinely practical, but it does not turn the canvas into a repo.n8n's CLI docs, captured August 14, 2026. Note the last item in the page nav: n8n now documents using the CLI as a skill with Claude Code.
Use Codex for Builder Work
Codex is the better choice when the work requires context from your project:refreshing a blog article against Search Console evidence
adding schema, metadata, internal links, or page sections
building a new calculator, tool, or workflow page
reading existing files before making a change
running a build and fixing failures
turning a messy idea into a concrete implementationThat is builder work. It benefits from repo context and judgment.
If you try to force that whole process into n8n, the canvas gets crowded fast. Prompts, examples, brand rules, page templates, and QA checks belong in files where a coding agent can inspect and update them.
Codex ships inside the ChatGPT Pro tiers, per OpenAI's Pro tiers page, so if you already pay for Pro you already have it.
Use n8n for Runner Work
n8n is the better choice when the work needs to happen repeatedly:every Monday, pull Search Console data
when a form is submitted, enrich the lead
when a video is uploaded, create repurposing tasks
when a page draft is ready, notify the human reviewer
when approval is granted, send the next step to GitHub, Slack, Notion, or emailn8n is strongest as the workflow layer because it handles boring operational details: triggers, credentials, retries, node-level debugging, and run history.
That boring part is the part that keeps systems alive. It is also why my one surviving workflow is still there.
The n8n template library listed 11,490 workflow templates as of August 2026, which is a decent shortcut if the runner work you need is a common one.
The Best Pattern: Codex Plus n8n
For organic traffic, the useful system looks like this:Step
Owner
Job1
n8n
Pull Search Console query/page data2
n8n
Filter for impressions, weak CTR, and low position3
Codex
Read the target page and refresh it4
Codex
Run build, SEO QA, and link checks5
Human
Approve the point of view6
n8n/GitHub/Vercel
Route deployment and notifyThat is the arbitrage: n8n finds and routes repeatable signals. Codex turns the signal into a useful asset.
How to use n8n with Codex, step by step
If you searched "n8n with codex" and want the wiring rather than the theory, this is it:Trigger in n8n. A Schedule, Webhook, or Form node starts the run and carries the input data.
Call Codex as a build step. Run it from a script or an Execute Command node so it reads the repo, makes the change, and returns a result. You are not embedding the agent in the canvas.
Capture the output back into the workflow as structured data.
Route it to a human. Slack, email, or a GitHub pull request. Nothing that touches production, customers, money, or the public site ships without approval.
Let n8n handle the boring half: retries, credentials, and run history for the whole thing.The connector-plus-agent pattern is now mainstream rather than a niche trick. Zapier publishes its own Codex integration guide for the same shape of setup, and my plain-English version of that setup is at how to use Zapier with Codex.
When Codex Alone Is Enough
Use Codex alone when the task is one-time or repo-bound:"refresh this tutorial"
"add a hub page"
"fix this favicon"
"build a comparison page"
"run the local build"No workflow runner needed. The value is in the edit.
As one r/codex user framed the division: "Where codex is great is if you want to take an n8n automation and make it a standalone app. Or writing an endpoint that can be triggered by your [workflow]."
When n8n Alone Is Enough
Use n8n alone when the rules are clear:copy a form submission into a CRM
send a Slack notification after a status change
save an RSS item to a database
send a weekly report
route approved data between apps
scrape the same source on a schedule, foreverNo coding agent needed. The value is in the repeatable run. That last line is my one surviving workflow, and it is why this section is not a courtesy.
When You Need Both
Use both when the workflow has a repeatable trigger but the output needs judgment.
Good examples:Search Console opportunity scoring
weekly content refresh queue
transcript-to-blog draft routing
lead triage with human approval
workflow JSON review before importThe model should not publish directly. It should prepare the work, show evidence, and ask for approval when the output touches the public site, customers, money, or production.
The scaling argument from r/codex matches what my own migration found: "For simple workflows, n8n + an LLM might be fine, but once things get serious, Codex handles straight code much better than going through a [canvas]."
My Default Rule
If the problem is "build the system," use Codex.
If the problem is "run the system every week," use n8n.
If the problem is "use real signals to ship useful assets repeatedly," use both.
And if you are sitting on a canvas full of nodes wondering whether to migrate: count how many of them are making a decision. If it is most of them, that is agent-shaped work and it belongs in code. If it is none of them, leave it alone. That is what I did with the one I kept.
Next, read AI coding agent vs workflow automation, then map the runner side with the n8n AI agent workflow example.
Published June 15, 2026. Last reviewed and updated August 14, 2026: corrected the migration receipt to "kept one workflow" from the earlier "kept nothing" phrasing, added the worth-learning verdict, the which-agent section, the n8n CLI, and a step-by-step n8n-with-Codex block. Codex tier inclusion and the n8n template count verified against vendor pages that day, linked inline.
Quick answer: An n8n AI agent is a workflow built on the AI Agent node, connected to tools (HTTP, database, code, APIs, or MCP servers) so an LLM can read context, call those tools, and pick the next step on its own. Without tools, it is just a chatbot in a workflow. Build one scoped agent: pick a single decision, attach the AI Agent node, wire tight tools, force structured output, test on real data, and put a human on anything that ships.
As of mid-2026, n8n also adds the MCP Client Tool (use any MCP server's tools) and the AI Agent Tool node (one agent supervising others on a single canvas). The Ship Lean pattern stays the same: Claude/Codex builds, n8n runs, a human approves anything risky.
Published June 2026. Last reviewed 7 August 2026 against the current AI Agent node docs and the n8n changelog through the 2.34 release.
If you're trying to figure out whether you even need an agent, start with what an n8n AI agent is and n8n AI agent vs workflow automation. Short version: agents are for judgment calls, not every automation.
If you want the whole path in one place, start with the n8n AI Agents hub. It links the definition, workflow pattern, builder tool, and Claude Code handoff.
If your search is specifically for an n8n ai agent workflow or n8n agentic workflow, the canonical workflow page is n8n AI agent workflow for solo builders. Use this tutorial when you want the build sequence: node setup, tools, structured output, testing, and approval.This page owns the build tutorial. The related pages own the shorter definition and workflow-example intents:Query intent
Best owner
Direct answern8n ai agent tutorial
This tutorial
Build one scoped agent around the AI Agent node, tools, structured output, testing, and approval.n8n ai agent workflow
Workflow pattern
Trigger in n8n, let the model make one scoped decision, route the result, then approve risky output.n8n agentic workflow
Workflow pattern
The agentic part is tool use plus structured decisions, not just an LLM prompt.n8n ai agent node
This tutorial
The node is the reasoning step; n8n still owns triggers, credentials, routing, retries, and run history.what is n8n ai agent
Definition page
It is an LLM-powered workflow step that can use tools and return a decision inside automation.n8n ai agent documentation 2026
This tutorial + n8n docs
n8n's docs cover the node reference; this page covers the build sequence and the decisions the docs skip.I built my first "agent" in n8n and felt very smart for about ten minutes.
Then I realized I'd just made a fancy ChatGPT call. Input went in. Output came out. Nothing decided. Nothing checked. No tools.
That's the gap nobody flags in the tutorials: dropping the AI Agent node into a workflow doesn't make it agentic. It makes it an LLM with a trigger.
This post is the version I wish I'd had when I started: what an n8n AI agent actually is, when to use one instead of a normal workflow, and the pattern I use now that keeps me out of multi-agent spaghetti.I walk through this on camera in n8n AI Agent: Build One That Actually Works (Not Theory) (12 min).Before the Node: Plan, Plan, Plan
After two years of running self-hosted n8n, the mistake I see people make most is not a wiring mistake. It is starting in n8n at all.
Figure out what you want to build an agent for before you open the canvas. This is where a chat model earns its keep - brainstorm the use case with Claude, ChatGPT, Gemini, whatever you already pay for. n8n is a time commitment. You do not want to spend hours, days, or weeks building something you will use a little bit, and you want to end up with something you can actually maintain and understand.
Once you land on one, two, or three concrete use cases: do one at a time. Build the simplest version first, then scale. If you build something complex and you are not using it a week or two later, you did not build an agent - you wasted a weekend.
The other half of the mistake is overcomplication at the node level. People hear "AI agent" and reach for the most elaborate thing on the canvas. Strip it back: an AI agent is an LLM call. What makes it interesting is giving it tools - access to your calendar, your database - so it can query and act instead of just answering.
But here is the part that will save you the most time: simpler is better, and most of the time you do not even need the tools. If a plain LLM step solves your problem, ship that. Do not rush toward the agent architecture because it sounds more impressive. More nodes does not make you smarter.
One current product detail worth knowing, because it changed: n8n's AI Agent node now requires at least one tool sub-node to be connected. Separately, as of v1.82.0 the old agent-type selector is gone - every agent is a Tools Agent. So if your use case genuinely needs no tools, the node you want is the Basic LLM Chain, not the AI Agent.
Reach for tools when the job needs them, not because the node is called "agent."
What Changed for n8n AI Agents in 2026?
n8n is no longer just "Zapier, but flexible." It is moving toward a durable AI workflow layer: agent nodes, tools, memory, structured output, retries, credentials, and run history in one canvas.
That matters because the winning pattern is not "let the model do everything." The winning pattern is:Layer
Best owner
WhyPrompt, schema, tool design
Claude Code or Codex
Repo context, writing, code, and judgmentTrigger, credentials, retries
n8n
Durable workflow operationsFuzzy decision
AI Agent node
Reads context and chooses a tool or answerPublic/customer action
Human approval
Keeps trust where it belongsAs of this refresh, n8n's AI Agent node is a versioned node with current support for tools and output parsers. n8n's own Tools Agent docs describe the agent as the piece that can choose external tools and return a standard output format. That is the part solo builders should care about: not "AI magic," but repeatable decisions with visible runs.
Two mid-2026 additions actually matter for solo builders:MCP Client Tool. The AI Agent node can now use tools exposed by remote MCP servers directly. There's also a standalone MCP Client node, so any step in the workflow — not just an agent — can call an MCP server. In plain terms: instead of hand-wiring an HTTP node for every API, you can point the agent at an MCP server that already exposes a clean set of tools.
AI Agent Tool node (single-canvas multi-agent). You can connect multiple AI Agent Tool nodes to one primary AI Agent, letting it supervise and delegate across specialized agents in a single execution, on one canvas. This is the sanctioned way to do "multiple agents" without the multi-workflow spaghetti most tutorials walk you into.Three things shipped since the last review that change the build (all from n8n's changelog):Human-in-the-loop for AI tool calls (v2.6, January 2026). You can now require explicit human approval before an agent executes a specific tool. Wherever this guide tells you to route risky output through a Slack or Telegram approval step, check this native gate first - it is built into the tool call now, so you may not need to wire the approval hop yourself.
One-click MCP servers (v2.22, May 2026). Apify, Linear, monday.com, Notion, and PostHog can be connected by picking the server from a panel and signing in. Where the MCP notes above describe pointing an agent at a server, that setup is now closer to installing an app than hand-wiring a connection.
Native web search for agents (v2.25, June 2026). An Advanced-panel toggle, rather than bolting on a search API as a custom tool.New since the July review (2.29–2.34, from the changelog):The autonomous AI Assistant (2.29.9, July 2026) is NOT the AI Agent node — don't confuse the two. The Assistant is n8n's build-time copilot: you describe a workflow in plain language and it plans, builds, test-runs, and fixes errors until the automation works. Cloud-only for now, self-hosted support promised. The AI Agent node is the runtime piece — the node inside your workflow that makes a decision on every execution. Plain rule: the Assistant helps you BUILD the workflow once; the Agent node RUNS inside it forever. Everything in this guide is about the second one, and the Assistant doesn't change a single step of it — though it's now a legitimately fast way to scaffold the boring parts around your agent.
MCP got sturdier (2.29–2.29.9): dynamic field resolution (live Slack channels, Sheets tabs, not stale lists), custom and community nodes usable in MCP workflow builds, and version history you can browse and restore. If the MCP Client Tool felt beta when you last tried it, it's grown up.
2.34 (August 2026) is plumbing, not AI: large webhook responses offload to binary storage. Only matters if your agent workflows return big payloads.The changelog as of this review (August 7, 2026): stable 2.33.6, beta 2.34.3 — the AI Assistant and MCP server updates are the entries that touch agent builders.
A note on n8n 2.0: it was a security/reliability/performance release (sandboxed Code-node execution by default, a Publish/Save workflow paradigm) - not an AI-feature release. Worth upgrading for the platform maturity; don't expect it to change how you build agents.
Use current language when you build:AI Agent node for the reasoning step
Tools for API/database/app actions — or an MCP Client Tool when a server already exposes them
AI Agent Tool node when one agent genuinely needs to delegate to another (not before)
Structured Output Parser when downstream nodes need clean fields
Memory only when the task needs prior conversation or prior user state
Retries and run history for boring reliabilityIf you only remember one thing, remember this: n8n is the runner, not the whole brain. The AI Agent node should own one fuzzy decision. Everything before and after that should be boring workflow automation — and MCP tools don't change that rule, they just make the tool layer faster to wire.
What Is an n8n AI Agent, Exactly?
An n8n AI agent is a workflow built around the AI Agent node with tools attached: usually HTTP Request, a database, Airtable, code, or other n8n nodes. That lets the LLM do three things in a loop:Read the input and current context
Decide whether to call a tool (and which one)
Use the tool's output to pick the next action or final answerThe "agentic" part is the loop. The model isn't just generating text. It's choosing actions based on what it finds.n8n's own docs, captured August 2026: the AI Agent node requires at least one tool sub-node, and the old agent-type picker is gone — everything runs as a Tools Agent now.
Without tools, the AI Agent node is a fancy LLM call. With tools, it can look things up, write to a database, hit an API, and reason about the result before answering.
For AEO purposes, this is the clean definition:An n8n AI agent is a workflow where the AI Agent node can use tools, memory, and structured output to make a judgment step inside a larger automation.n8n AI Agent vs Regular Workflow Automation: When to Use Which
I default to plain workflow automation. Agents are the exception, not the rule.Situation
Use a regular workflow
Use an AI agentInputs are predictable (form fields, structured webhook)
✅Logic fits a clean if-then tree
✅You need messy text classified or summarized✅You need it to look something up before deciding✅Output has to be structured every time, no surprises
✅Edge cases keep slipping through your filters✅Cost per run matters and volume is high
✅Rule of thumb I use:If I can write the rules in 10 minutes, it's a workflow. If I'd need 50 if-statements and still miss cases, it's an agent.A workflow that classifies email tone with keyword matching will miss "I've been waiting three weeks and this is getting ridiculous." An agent reads it and routes it correctly. That's the kind of decision worth paying tokens for.One of mine: a Reddit idea scraper I ran for months. Everything around the edges is boring workflow — the ONE agent (with its model, memory, and output parser hanging off it) exists because "is this post actually a content idea" is exactly the messy-text judgment a filter can't make. Note the Error Trigger → Gmail alert in the corner: boring reliability, wired first.
If the decision is "did the Stripe webhook fire? then send the receipt," don't put an LLM in the path.
For a deeper split, read n8n AI agent vs workflow automation. If the question is whether Codex, Claude Code, or n8n should own the work, use AI coding agent vs workflow automation.
How Do You Structure an n8n AI Agent Workflow?
Here's the layout I use now. It's not clever. That's the point.1. n8n handles the trigger and routing.
Webhook, RSS, schedule, Airtable change: n8n is good at this. Don't make the LLM do it.
2. The LLM handles judgment.
This is the AI Agent node (or a Claude Code call via HTTP). It reads context, calls tools, returns a structured decision. One agent, one job.
3. Tools are scoped tight.
Read-only when possible. Pre-filtered queries, not "here's the whole database." Every tool is one more thing you have to trust.
4. A human approves anything that ships.
Sends an email to a customer, charges a card, posts to a public account, deploys code: that goes to a Slack/Telegram approval step before it executes. The agent drafts; you click yes.
5. Claude Code does the building, n8n does the running.
I draft prompts, tool definitions, and workflow logic in Claude Code or Codex. n8n runs the workflow on a schedule. GitHub holds the workflow JSON. Vercel hosts anything customer-facing. Each tool does what it's good at.
That's the whole stack. No swarm of sub-agents. No "AI orchestrator" picking other agents. One agent, scoped tools, human in the loop where it matters.
Still deciding which side of that build/run line your work belongs on? Read Claude Code vs n8n for solo builders: short version, Claude Code owns the judgment and the code, n8n owns the trigger and the repeat.
The 2026 Build Checklist
Before you touch the n8n canvas, write these five things down:Decision
Good answerAgent job
"Score this Search Console query as BUILD, REFRESH, or IGNORE."Input
Query, URL, impressions, clicks, position, current page summaryTools
Read page content, inspect sitemap, write row to task tableOutput
JSON with decision, reason, priority, next_actionApproval
Human approves new public pages and page refreshesIf you cannot fill in that table, the workflow is not ready. You do not have an agent problem yet. You have a scope problem.
What Do You Need Before Building an n8n AI Agent?An n8n instance. When I ran n8n I self-hosted on Hostinger to skip per-execution fees — a Mac mini at home does the same job free.
An API key. I use Claude Sonnet for most agent work because the structured output behaves.
A clear, single decision you want automated
Airtable or a database if your agent needs memoryHeads up: some links in this post are affiliate links — a small kickback to me at no cost to you. I only recommend tools I've actually run.
If n8n is new to you, run through the n8n tutorial for beginners first.
Use a manual trigger while you're building. You'll run the thing 30+ times tweaking prompts, and you don't want an RSS feed or webhook firing each time.The 60-second version, from my Shorts: Build your first AI agent (no code, under an hour).Step 1: Pick One Decision
Every agent needs one job. Not three. One.
Bad: "Read my inbox, write replies, schedule meetings, and update the CRM."
Good: "For each new RSS post, decide if it's worth sharing with my list. Output SHARE or SKIP and a one-line reason."
The narrower the scope, the easier it is to prompt, test, and trust. If you can't describe the agent's job in one sentence, the agent isn't ready to be built.
Step 2: Trigger and Input
For the example, we'll keep using the content filter: an RSS feed pulls new posts, each post becomes input.
The trigger's job is to give the agent enough context to make the call: title, link, full text, source. If your input is thin, the agent's decisions will be thin too.
Step 3: Add the AI Agent Node
Drop in the AI Agent node. Connect the trigger.What the node looks like placed in a real build (a LinkedIn lead scraper I used to run): the agent sits mid-flow, and the Chat Model / Memory / Tool sockets underneath are where everything from Step 4 attaches.
Configure:Provider/model: Claude Sonnet is my default for judgment work
System prompt: define the job, the criteria, and the output format
Output parser: use structured output when another node needs reliable fields
Memory: add it only if the workflow needs prior conversation or prior user stateExample system prompt:
You are a content relevance filter for a newsletter aimed at solo AI builders
who use Claude Code, n8n, and ship products on the side.For each post, decide:
- Relevance: High / Medium / Low (does it help this audience build or ship?)
- Quality: High / Medium / Low (is it specific and actionable, or generic?)
- Decision: SHARE or SKIP
- Reason: one line, plain languageDefault to SKIP when uncertain. We'd rather miss a marginal post than share a weak one.This alone is not an agent yet. It's an LLM with a prompt. It reads, it answers, that's it.
The next step is what changes that.
Step 4: Attach Tools and Structured Output
Tools are how the agent does things instead of just saying things.
In n8n, common tool options:HTTP Request: call any API
Database / Airtable / Postgres: look up or write history
Code: custom logic when needed
Other n8n nodes: wrapped as toolsFor the content filter, attach an Airtable tool pointing at a "Shared Posts" table. Update the prompt:
Before deciding, use the Airtable tool to check the "Shared Posts" table for
posts shared in the last 30 days. If a similar topic was already covered,
lean toward SKIP unless this post is meaningfully better or newer.Now the agent isn't analyzing a post in a vacuum. It's checking history, comparing, and using that to decide. That's the loop.
You don't need n8n's sub-agent feature for this. I almost never reach for it. One agent + a few tools handles most things I've thrown at it.
When the next node expects clean data, do not make it parse paragraphs. Require structured output:
{
"decision": "SHARE",
"reason": "Specific walkthrough for solo AI builders.",
"confidence": 0.82,
"approval_required": true
}This is the difference between a demo and a workflow you can run every week.
Step 5: Wire the Decision to Action
The agent returns something like:
Decision: SHARE
Reason: Concrete walkthrough of building a Claude Code subagent. Fits the audience.Downstream, you don't need a 12-branch if-then. You need one router checking Decision === "SHARE". The complexity lives in the agent's reasoning, not in the canvas.
For anything that goes out the door, like a tweet, an email, or a published post, route it to a human approval step. A Slack message with Approve/Reject buttons works fine. The agent drafts. You ship.
If you are building this for Ship Lean-style traffic work, the approval step matters even more. New pages, refreshed titles, comparison claims, and public recommendations should not publish automatically. The workflow should prepare the draft and evidence. A human should approve the point of view.
Step 6: Test on Real Data, Not Your Imagination
Your first version will be wrong. That's fine. Plan for it.
What I run into most:Vague prompts: agent makes inconsistent calls because the criteria are fuzzy
Tool not actually wired: agent "tries" the tool but the connection is broken
Output drifts: sometimes structured, sometimes prose
Real inputs are messier than your test inputsFix loop is always: tighten the prompt, add an example or two of correct output, narrow the tool's scope.
Step 7: Add the Boring Reliability
This is where n8n earns its keep.
For any workflow you plan to keep:Log every run somewhere boring: a Sheet, Airtable table, Postgres row, or Notion database.
Save the input, decision, model, cost estimate, and approval result.
Add retries where the failure is likely temporary.
Alert yourself when the workflow fails or the output parser breaks.
Keep credentials in n8n, not pasted into prompts.AI builders love the agent part. Operators love the run history. Organic traffic comes from writing about the version that actually survives contact with real inputs.
What Does a Real Production n8n AI Agent Look Like?
When I checked my own n8n workspace, the pattern was obvious: lots of experiments, one production workflow doing a clear job.
The active workflow is not a mystical multi-agent swarm. It is a content scheduling runner:A Notion trigger starts the run.
n8n grabs the page, length, and assets.
A filter, code step, and switch route the item.
Blotato nodes send the asset to YouTube, Instagram, X, TikTok, and LinkedIn.
n8n updates the status back in Notion.The actual canvas. Notice what's NOT in it: no AI Agent node anywhere. Scheduling posts is deterministic — trigger, grab, switch, post, update. This ran my whole distribution and it's plain workflow automation end to end, which is exactly the point of the table earlier.
That is the lesson. The workflows that survive are not always the flashiest ones. They are the ones with a narrow trigger, clear routing, visible status, and boring handoffs.
Most of the other workflows in my account are paused experiments: idea engines, social research, lead routing, newsletter systems, job prep, payment reminders, and old tests. That is normal. n8n becomes more valuable when you label the experiments, retire the stale ones, and keep production workflows boring enough to trust.
The best public example from that inventory is not the active content scheduler. It is the lead qualification pattern.
The private workflow has the shape that actually teaches the idea:A webhook receives a lead.
n8n enriches the lead data.
An AI step qualifies the lead.
A structured parser turns the model response into fields.
n8n routes the result into hot lead, nurture, Slack, and email paths.That is the useful proof: the model makes one judgment call, then n8n routes the outcome. For a public template, I would not publish the private workflow raw. I would publish the cleaned pattern instead, with fake sample data and no credentials.
You can download that starter pattern here: n8n human approval workflow JSON. I also published the proof asset on GitHub: n8n AI lead qualification workflow with human approval.
What I Got Wrong Early
My first n8n agent system was a faceless YouTube pipeline: Reddit scrape to script to 11Labs voiceover to Creatomate render. Took me a couple weeks. Had four agents where one would've done.
It worked. The output wasn't great, but it ran. The lesson wasn't "agents are powerful." It was: I built before I validated, and I overcomplicated every step.
The rewrite was always the same: collapse to one agent, scope its tools, put a human at the publish step.
That's the version I'd build today, and it's the version above.
What Are the Most Common n8n AI Agent Mistakes?
1. Using the AI Agent node with no tools.
You built a chatbot. Tools = autonomy. No tools = no decisions worth calling agentic.
2. Multi-agent setups before you need them.
Sub-agents and agent loops exist. Skip them until a single agent has clearly hit its ceiling. It usually hasn't.
3. Vague system prompts.
"Make good decisions" isn't a prompt. Spell out criteria, output format, and what to do when uncertain.
4. No human approval on outbound actions.
The first time an agent emails a customer something weird, you'll wish you had this. Add it before you need it.
5. Testing only on data you wrote.
Real inputs break things synthetic ones don't. Test on actual feeds, actual emails, actual rows.
6. Adding memory because it sounds advanced.
Memory is useful for ongoing conversations. It is usually unnecessary for one-shot scoring, routing, enrichment, and drafting workflows. Start stateless, then add memory only when the missing context is actually hurting results.
7. Treating structured output as optional.
If n8n needs to route the result, make the agent return fields. Prose is for humans. JSON is for the next node.
n8n AI Agent FAQ
What is the n8n AI Agent node?
The AI Agent node is the reasoning step in an n8n workflow. It connects a model to tools, memory, and an output parser so the workflow can make a decision instead of only moving data. n8n still owns the trigger, credentials, routing, retries, and run history around it.
What's the difference between the n8n AI Assistant and the AI Agent node?
The AI Assistant (July 2026, Cloud) builds workflows for you: describe what you want in plain language and it plans, wires, test-runs, and fixes the workflow until it works. The AI Agent node runs inside a workflow and makes a decision on every execution. Use the Assistant to scaffold; use the Agent node when the workflow itself has to think. They're complementary, not competing.
What makes an n8n workflow agentic instead of just an LLM call?
The workflow is agentic when the AI Agent node can choose a tool, inspect the result, and return a structured decision. A plain prompt with no tools attached is a chatbot in a workflow, not an agent. The agentic part is the loop: read context, call a tool, use the output to pick the next action.
Can an n8n AI agent use MCP tools?
Yes. As of mid-2026 the AI Agent node supports the MCP Client Tool, so the agent can call tools exposed by a remote MCP server without hand-wiring an HTTP node for every API. There is also a standalone MCP Client node so any step in the workflow, not just the agent, can hit an MCP server.
How do you run multiple agents in n8n?
Use the AI Agent Tool node. You connect one or more AI Agent Tool nodes to a primary AI Agent so it can supervise and delegate across specialized agents in a single execution on one canvas. Reach for this only after one well-scoped agent has clearly hit its ceiling, which is rare.
When should you use an n8n AI agent instead of a normal workflow?
Use a normal workflow when the logic is predictable and rule-based. Use an AI agent when the work needs judgment: messy text classification, summarization, or looking something up before deciding. If you can write the rules in ten minutes, it is a workflow, not an agent.
Does an n8n AI agent need memory?
Usually no. Add memory only when the workflow needs conversation history or prior user state. For stateless tasks like scoring a lead or classifying a query, structured input plus a tool is cleaner and cheaper. Start stateless, then add memory only when the missing context is actually hurting results.
Where to Go From Here
Pick one decision you make repeatedly that's annoying because it requires reading something: inbox triage, lead scoring, content filtering, support routing.
Build that. One agent, one tool, one decision. Run it manually for a week. Watch where it gets confused. Tighten the prompt.
Once that's working, the second one takes half the time. The third feels normal.
For more patterns, see 7 n8n workflow examples, what an n8n AI agent is, n8n AI agent vs workflow automation, and n8n vs Make for AI agent workflows. If you're still deciding which tool should own the work, Claude Code vs n8n for solo builders and Codex vs n8n draw the line clearly.
The AI Agent node is a building block, not the whole building. Tools are what turn it into something that decides. Keep the rest of the stack boring: n8n for plumbing, Claude Code for judgment, GitHub and Vercel for everything that ships. Then you can spend your time on the decisions, not the wiring.
Quick answer: Use Zapier when you want the fastest simple automation between popular apps. Use n8n when you need a real AI agent workflow: tools, structured output, branching, retries, self-hosting, and deeper control. For Ship Lean-style systems, Zapier is a shortcut. n8n is the runner layer.
Heads up: some links in this post are affiliate links — a small kickback to me at no cost to you. I only recommend tools I've actually run.
If you are new to the concept, start with what an n8n AI agent is. If you already know you want n8n, use the n8n AI Agent Workflow Builder.
Quick ComparisonQuestion
n8n AI Agent
Zapier AI ActionsBest for
Custom AI workflows with tools
Fast app-to-app AI actionsBuilder type
Technical solo builder, operator, team
Nontechnical operator, speed-first builderAgent depth
Stronger for tool-using workflows
Better for simple AI-assisted actionsHosting
Cloud or self-hosted
CloudWorkflow control
High
MediumDebugging
Node-level runs and logs
Simpler task historyBest first use
Agentic routing, enrichment, approval
Simple summaries, drafts, app updatesThis is not a moral decision. It is an architecture decision.
What n8n Does Better
n8n is stronger when the workflow has real logic:the agent needs to choose between tools
the output needs a structured schema
you need custom code in the middle
you want to self-host
the workflow needs approvals before publishing
the run history matters because this is becoming an operating systemThat makes n8n a better fit for durable AI workflows.
For example, a Search Console workflow might:Pull query/page data.
Ask an AI Agent node to classify the opportunity.
Use a tool to inspect the current page.
Return structured fields: refresh, build, or ignore.
Create a draft task.
Ask for human approval before publishing.That is more than "summarize this row." It is a small operating loop.
What Zapier Does Better
Zapier is stronger when speed and app coverage matter more than control.
Good Zapier use cases:summarize a form submission
draft a Slack reply
move a lead into a CRM
create a simple email draft
connect two common SaaS tools quicklyIf the workflow is simple, Zapier may be the better first move. The fastest useful automation often wins.
The Hidden Question: Do You Need an Agent?
Most workflows do not need an agent.
Use simple automation when the rule is clear:Task
UseNew form submission goes to CRM
Simple automationNew meeting gets a Slack reminder
Simple automationSupport message needs urgency classification
AI stepSearch query needs refresh/build/ignore judgment
AI agentPublic content needs approval
AI agent plus human reviewIf the workflow is just moving data, do not make it agentic. If the workflow needs judgment, tools, and routing, n8n gets more interesting.
The Ship Lean Pick
For a solo builder trying to grow organic traffic, I would use:Codex or Claude Code to build and refresh pages
n8n to pull recurring signals, route tasks, and manage approvals
Zapier only when a simple SaaS handoff is faster than building a custom n8n workflowThat keeps the core system owned by you while still allowing shortcuts when they are actually shortcuts.
When I Would Choose Each
Choose Zapier if:you need a working automation today
the workflow has two or three simple steps
you do not care about self-hosting
you do not need custom agent toolsChoose n8n if:you are building an AI agent workflow
you need structured output and branching
you want lower-level control
you want self-hosting or deeper data ownership
you want the workflow to become part of your operating systemFor deeper n8n patterns, read the n8n AI Agent Tutorial and n8n AI agent vs workflow automation.This post is part of the n8n AI agents hub: definitions, tutorials, workflow patterns, and the build-vs-run decision pages in one place.
For AI agent workflows, I would usually pick n8n over Make.
Heads up: some links in this post are affiliate links — a small kickback to me at no cost to you. I only recommend tools I've actually run.
Not because Make is bad. Make is clean, visual, and easier for a lot of app-to-app automations.
But for the technical or technical-adjacent solo builder, n8n has the better shape:Need
PickEasiest visual app automation
MakeSelf-hosting and control
n8nCode nodes and custom logic
n8nAI agent workflows with tools
n8nSimple marketing ops workflows
Make or n8nLower marginal cost at scale
n8n self-hostedWhere Make wins
Make is good when the workflow is visual and app-heavy.
Use it when:you want the easiest builder
you are connecting common SaaS apps
the workflow is not deeply technical
you do not care about self-hosting
you want a polished visual interfaceIf the goal is "move this from app A to app B with some formatting," Make is fine.
Where n8n wins
n8n is stronger when you want control.
Use it when:the workflow needs code
you want self-hosting
you care about cost at scale
you need custom API calls
you want agent tools and more flexible logic
you are comfortable debuggingThat last point matters. n8n is not always easier. It is more flexible.
The AI agent workflow angle
AI agent workflows tend to need:context gathering
tool access
memory/history
conditionals
retries
logging
approval steps
custom actionsn8n fits that shape well.
Make can do plenty, but n8n feels more natural when the workflow starts drifting from "connect apps" into "build an operating system."
My recommendation
If you are a solo builder using Claude Code, GitHub, Vercel, APIs, and custom workflows, start with n8n.
If you are a non-technical operator who wants polished app automation fast, start with Make.
If you already have Make working, do not migrate for sport. Move only when you hit control, cost, or flexibility limits.
Build your first n8n agent map with the n8n AI Agent Workflow Builder.
FAQ
Is n8n or Make better for AI agent workflows?
n8n is usually better for technical solo builders who want control, code nodes, self-hosting, and agent-style workflows. Make is easier for visual app automation.
Should solo builders start with n8n or Make?
Start with Make if you want the easiest visual builder. Start with n8n if you want more control and expect to build AI agent workflows.This post is part of the n8n AI agents hub: definitions, tutorials, workflow patterns, and the build-vs-run decision pages in one place.
Use normal workflow automation when the rules are clear.
Use an n8n AI agent when one step needs judgment.
Heads up: some links in this post are affiliate links — a small kickback to me at no cost to you. I only recommend tools I've actually run.
That is the whole decision. If you already know you need the agent version, the full n8n AI agent workflow pattern shows the build: trigger, context, scoped tools, human approval, and logging.Situation
UseCopy data from form to CRM
Normal workflowSend Slack alert after status changes
Normal workflowClassify messy customer messages
AI agentScore Search Console queries for content ideas
AI agentDraft a newsletter from a build log
AI agent plus approvalPublish automatically to production
Probably notWorkflow automation is for known steps
Normal automation is best when you can describe the rule clearly:when this happens, do that
if status is approved, send email
every Monday, pull this report
when form submits, create taskYou do not need an AI agent for that.
Adding one usually makes the workflow slower, harder to debug, and more expensive.
AI agents are for fuzzy steps
Use an agent when the workflow needs to interpret something:Is this lead qualified?
Is this query worth a page?
Does this transcript contain a strong proof moment?
Is this support message urgent?
Should this draft be published, revised, or killed?That is not a simple if/then branch. That is judgment.
The clean hybrid pattern
The best setup is usually both:n8n triggers the workflow.
n8n gathers data.
The agent handles the fuzzy decision.
n8n routes the result.
A human approves high-risk output.That gives you automation without pretending the agent should own the whole process.
Use the Claude Code + n8n Workflow Planner to split the work before building. If you're choosing between a coding agent and a workflow runner, read AI coding agent vs workflow automation.
What solo builders should build first
Start with a workflow where bad output is annoying, not catastrophic.
Good:content idea scoring
transcript repurposing
newsletter draft creation
lead triage draft
workflow planningBad:customer refunds
publishing without review
deleting production data
sending sales emails with no approvalThe goal is not to make the agent powerful. The goal is to make it useful and bounded.
FAQ
What is the difference between an n8n AI agent and workflow automation?
Workflow automation follows known rules. An n8n AI agent handles the judgment step inside a workflow.
Should every n8n workflow use an AI agent?
No. Use normal automation when the steps are clear and rule-based. Add an agent only when the workflow needs reasoning.This post is part of the n8n AI agents hub: definitions, tutorials, workflow patterns, and the build-vs-run decision pages in one place.
An n8n AI agent is a workflow step that uses an LLM plus tools to make decisions inside an automation. The agent reads context, chooses or calls tools, returns a structured result, and lets n8n route the next step.
Heads up: some links in this post are affiliate links — a small kickback to me at no cost to you. I only recommend tools I've actually run.
The short version:Part
Jobn8n
Trigger, gather data, route output, retry failuresAI agent
Read context, decide, draft, classify, score, or planTools
Let the agent check data or take actionHuman approval
Protect anything public, expensive, or brand-sensitiveThe mistake is thinking the AI Agent node is magic by itself. It is not.
The node becomes useful when it has a clear job, enough context, and access to the right tools.
If you want the full build sequence, read the n8n AI agent tutorial. If you want the repeatable pattern, use the n8n AI agent workflow. This page is the short definition.
The plain-English version
Think of n8n as the operations desk.
It knows when something happened. A form came in. A video published. A Search Console export landed. A Notion status changed.
The AI agent is the person at the desk who can read the packet and make a call.
Should this lead go to sales? Should this query become a tool page? Should this transcript become a newsletter? Is this task worth automating?
That decision is the agent's job.
The routing, logging, retries, and notifications are n8n's job.
What makes it agentic?
An agentic workflow has more than a prompt.
It has:a trigger
context
a decision
tools or actions
memory or history when needed
a clear output
an approval gate when consequences existWithout tools or actions, the agent is usually just an LLM response inside a workflow.
That can still be useful. But it is not the same as an agent that checks, decides, and routes.
A simple n8n AI agent workflow
Here is the pattern I would start with:n8n detects a new input.
n8n gathers the context.
The agent makes one specific decision.
n8n saves the decision.
A human approves if needed.
n8n routes the output.Use the n8n AI Agent Workflow Builder to map that before you build.
For the full Ship Lean path, use the n8n AI Agents hub. It connects this definition to the workflow pattern, builder tool, and Claude Code/n8n handoff.
The distinction matters:Search intent
Best next pagewhat is n8n ai agent
Stay here for the definition.n8n ai agent tutorial
Use the build tutorial.n8n ai agent workflow
Use the workflow pattern.Good first use cases
For solo builders, good use cases are boring:score Search Console queries
classify inbound leads
turn a build log into a newsletter draft
summarize support requests
route content ideas
check if a workflow is worth automatingBad first use case: "run my whole business."
Start with one judgment step.
n8n AI agent vs Claude Code
n8n AI agents are good inside recurring workflows.
Claude Code is better when the task needs repo context, file edits, code changes, or a real implementation pass.
Use both when the workflow needs a trigger and a code-aware operator:n8n detects and gathers
Claude Code edits or drafts
human approves
n8n routesRead the full decision rule in Claude Code vs n8n.
FAQ
What is an n8n AI agent?
An n8n AI agent is an automation step that uses an LLM plus tools to reason over context and take actions inside a workflow.
Is the n8n AI Agent node agentic by itself?
Not really. It becomes agentic when it can use tools, check context, make decisions, and route work instead of only generating text.
When should solo builders use an n8n AI agent?
Use it when one repeatable workflow needs judgment, classification, drafting, scoring, or routing.
What is the difference between an n8n AI agent and an n8n AI agent workflow?
The agent is the judgment step. The workflow is the full system around it: trigger, context, tools, approval, routing, logging, and retries.
Chris Alarcon 
