Whether you search it as "Claude Code vs n8n" or "n8n vs Claude Code," the answer is the same: they are not competitors. They are different parts of the same operating system.
Use Claude Code when the task needs judgment, file edits, writing, reasoning, or codebase awareness.
Use n8n when the task needs triggers, data movement, scheduled runs, retries, and integrations.
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 boring answer is the useful answer: Claude Code builds and thinks. n8n runs and routes.
Quick comparisonUse case
Claude Code
n8nEdit website files
Best
WeakBuild an internal script
Best
PossibleTrigger when a form is submitted
Possible
BestMove data between tools
Possible
BestWrite content in your voice
Best
Needs LLM nodeSchedule a daily workflow
Possible
BestInspect a repo and make changes
Best
WeakRoute content through approvals
Possible
BestThe 10-second decision rule
Ask this:
Does the task need context and judgment, or does it need a reliable trigger?
If it needs context and judgment, use Claude Code.
If it needs a reliable trigger, use n8n.
If it needs both, use both.
That sounds too simple, but it prevents the common mistake: trying to make n8n think like an operator or trying to make Claude Code behave like a durable scheduler.Save this one. It settles the argument in ten seconds.
When to use Claude Code: messy work with context
Use Claude Code for work where the prompt is the product.
Examples:writing a blog draft from a real build log
refactoring a site page
creating a new Astro page
reviewing a workflow
generating a script
turning a messy idea into an implementation planClaude Code is strongest when it can read the surrounding context and make decisions.
Claude Code is especially strong for solo builders because your business context often lives in files:site copy
product docs
workflow notes
analytics exports
newsletter drafts
messy markdown docs
code and configThat is not a clean API problem. That is an "understand the room before touching things" problem.
When to use n8n: repeatable work with triggers
Use n8n for the plumbing.
Examples:when a YouTube video is uploaded, create content tasks
when a Notion status changes, trigger a writing workflow
when an RSS item matches a topic, save it for review
every Friday, prepare the newsletter draft queue
when a form is submitted, add the person to MailerLiten8n is strongest when the workflow has a clear trigger and repeatable steps.
It also gives you visibility. When a workflow fails, you can inspect the run, find the bad node, fix the credential, retry the step, and keep moving.
That matters once the workflow touches real business operations.
The best pattern: Claude Code plus n8n plus human approval
The clean pattern is:n8n detects the event.
n8n gathers the inputs.
Claude handles the judgment-heavy step.
n8n saves the output.
A human approves.
n8n publishes or routes the result.That is the Ship Lean pattern: automation for the boring parts, human review for the parts with consequences.
Here is what that looks like for content:Step
Owner
Job1
n8n
Detect new video, build log, or GSC CSV2
n8n
Gather transcript, URL, notes, metadata3
Claude Code
Create brief, draft, edit, and file diff4
Human
Approve quality and positioning5
n8n/GitHub
Route PR, deploy, notifyThat is the version I trust. Not "AI posts directly to production while you sleep." That sounds good until it publishes something stale, generic, or wrong.
What should solo builders choose first?
If your problem is "I need to build or improve the system," start with Claude Code.
If your problem is "I keep copying data between apps," start with n8n.
If your problem is "I shipped a thing and nobody knows it exists," use both. Claude Code turns the proof into assets. n8n routes and schedules them.
Common mistake: using n8n as the whole brain
n8n can call LLMs. That does not mean the whole system should live inside n8n.
Once prompts, examples, brand rules, page templates, and content logic get serious, they become easier to maintain in a repo. That is where Claude Code shines.
Use n8n to collect inputs and trigger the run. Use the repo for durable instructions. Use Claude Code to operate on the repo. Use n8n again to notify and route the result.
Common mistake: using Claude Code for recurring ops
Claude Code can write a script. It can run a command. It can help you publish.
But recurring business operations need:schedules
retries
run history
credential handling
webhook triggers
alerts
handoff to other appsThat is n8n territory.
The Ship Lean setup I would run
For a solo builder trying to grow traffic:Claude Code owns the content system in the repo.
n8n watches for inputs: Search Console exports, YouTube videos, build logs, and newsletter notes.
Claude Code creates the page/tool/workflow draft.
The editor skill checks for thinness, reader fit, and whether the page actually helps.
Visual skill generates a diagram or comparison asset.
Human approves.
GitHub/Vercel ships.Want to estimate whether an automation is worth building? Run the automation priority audit. Want the stack cost? Use the AI stack cost calculator.
If your specific question is whether n8n should run an agent workflow, read what an n8n AI agent is and then map it with the n8n AI Agent Workflow Builder.
If you use Codex instead of Claude Code, the decision rule is almost the same. Read Codex vs n8n for the repo-agent version, or AI coding agent vs workflow automation for the broader split.
And if you have never opened a terminal at all, start one door earlier: Claude Cowork vs Claude Code - the same engine without the command line.
FAQ
Can n8n replace Claude Code?
No. n8n can call an LLM, but it does not replace a code-aware agent working inside your repo.
Can Claude Code replace n8n?
Sometimes for small scripts. But for recurring workflows with integrations, triggers, and retries, n8n is cleaner.
What is the best first workflow?
A content repurposing workflow is usually a strong first build because it turns work you already did into distribution.
Should I learn n8n if I already use Claude Code?
Yes, if you want recurring workflows that touch multiple apps. Claude Code helps you build and maintain the system. n8n helps the system run on schedule.
Last reviewed: July 2026.This post is part of the n8n AI agents hub: definitions, tutorials, workflow patterns, and the build-vs-run decision pages in one place.
Quick answer: I pay for both, every month, and use both every day.
If you can only justify one $20 subscription for work, take ChatGPT Plus: it is more general, you will use it for more things, and its limits bend instead of break. Take Claude Pro instead when your work is depth: long documents, serious writing, analysis where the AI must do exactly what you said.
The honest one-liner: Claude wins quality per message. ChatGPT wins messages. Real workloads want both.
If you searched "claude pro vs chatgpt plus" or "chatgpt plus vs claude pro," here is the comparison I wish existed when I started paying for these: current numbers from the official pages (July 2026), what real users say after months on each, and a verdict by the kind of person you are, not a fake universal winner.
The two plans in one table (July 2026, official pages)Claude Pro
ChatGPT PlusPrice
$17/mo billed annually ($200 up front), or $20 monthly
$20/mo, no annual optionUsage limit style
5-hour session limit + a separate weekly cap
Up to 160 GPT-5.5 messages per 3 hoursWhen you hit the limit
Hard stop until reset
Downgrades to a smaller model, keeps workingWhat shares the allowance
One bucket: chat + Claude Code + Cowork
Chat; the Codex coding agent has its own poolModels
Opus, Sonnet, Haiku. Fable 5 is NOT included - Pro pays usage credits for it
GPT-5.5 Instant and ThinkingIncluded agent tools
Claude Code, Cowork, Design, Research, unlimited projects
Agent mode, custom GPTs, scheduled automationsUpgrade path
Max: $100 (5x) or $200 (20x), and Max is where Fable 5 becomes included
Pro tiers: 5x and 20x Plus usageCorrection (July 31, 2026). This table used to list Fable as a Claude Pro model. That is no longer true, and it is the single most important change on the Claude side this year. Per Anthropic's Fable 5 plan page, the promotion that included Fable 5 in Pro's weekly usage limits ended July 19, 2026 at 11:59:59 PM PT. On Pro today, "Fable 5 isn't included in your plan's usage limits" - you pay usage credits on top of the $20. On Max it is included as standard, up to 50% of your weekly limits.
That reshapes the $20-vs-$20 question this whole page is about, so it gets its own section below.
Two structural details still matter more than any benchmark. First, the limit style: Claude stops you; ChatGPT demotes you. A hard stop mid-workday feels very different from quietly getting a smaller model. Second, the bucket: on Claude, every product drains one allowance, so a heavy agent session eats your chat capacity too.
The two ceilings, in plain language
People searching for "claude pro vs chatgpt plus limits" are usually trying to work out why they got stopped, so here is the mechanism.
Claude Pro runs two separate ceilings at once. There is a rolling five-hour session cap, and on top of that a weekly cap that applies across all models. You can be nowhere near your weekly limit and still get stopped by the session one.
That is why being cut off feels random. It usually is not - you hit whichever ceiling came first.
One more thing worth knowing before you buy: Cowork burns your allowance faster than chatting because multi-step tasks are compute-intensive. The feature most likely to sell you on Claude is also the one most likely to run you into a wall.
The complaint you will actually feel: Claude's weekly cap
The single loudest pain in the Claude community right now is the $20 tier's weekly limit. In a heavily upvoted r/ClaudeAI thread with close to 300 comments, "Claude Pro feels amazing, but the limits are a joke," u/iameastblood says it plainly: "Even though I use it quite sparingly, my weekly limit is already mostly drained by mid-week (currently sitting at 74% used)... it feels like I'm paying for a premium service I can barely use."
The consensus across those roughly 300 comments is uncomfortable but consistent: for heavy users, the $20 Pro plan works like a trial tier, and serious daily use points to Max at $100 and up.
Here is the de-blame part, because the complaints usually read like user error and they are not: the $20 tiers are designed differently on purpose. Claude Pro sells you a smaller amount of a very deep tool. ChatGPT Plus sells you a large amount of a very general tool. Neither is a scam. They are different bets, and you should pick the bet that matches your work.
Where each one actually wins (from people doing real work)
The pattern across every long-term comparison I have read, and my own daily use, is consistent:
Claude wins on depth and obedience. The best summary I have seen comes from a four-month "paid for both" comparison on r/ClaudeAI: for long-form writing, analysis, and structured documents, "claude wins... its not close." The same post nails instruction-following: "tell it 'respond in 1 sentence' and it actually does. gpt-5 negotiates." And a reply from u/Ashtonator28 became my favorite one-line review of both companies: "anthropic accidentally built a brilliant coworker. openai accidentally built a very competent butler."
ChatGPT wins on versatility and volume. A real-estate and tax professional, u/Free-Writer-1123 on r/claude, pushed back on the Claude hype after using both on actual client work: "ChatGPT has been the most-versatile with higher correct rate of answer. Better at reviewing text from PDF. Better at calculating for loans... I keep reading how awesome Claude is, but I have much different user experience than most." In the same thread, a teacher (u/FATJIZZUSONABIKE) countered that Claude's lesson plans were "so detailed and inspired that I've barely had to adapt anything."
Both are right. That is the whole point: depth versus breadth.
My own week looks like this. ChatGPT earns its subscription on the general layer: quick scripts, research, everyday questions, and its scheduled automations, which are genuinely excellent and feel like Cowork on steroids. I also keep its Codex coding agent wired in as a sparring partner that reviews and stress-tests work my main tools produce. Claude earns its subscription on the deep layer: the writing, the systems, the long careful work where instruction-following is everything.
Full disclosure, since this post is about the $20 tiers: these days I pay for the top of both stacks, Claude Max and ChatGPT Pro, because AI runs my entire operation. The split logic in this post is exactly how I route work between them; the top tiers just give the same split bigger buckets. Straight from my phone:The move nobody prices out: $40 across both beats $100 on one
Here is the configuration question that keeps showing up in the forums: one $100 plan, or two $20 plans?
For most working professionals, two $20 plans win, and not just on price. The reason is the limits math. The two allowances are completely separate, so splitting your workload means you almost never hit a wall on either side. I stopped hitting limits entirely once I split my work this way: the general, high-volume load goes to ChatGPT, the deep work goes to Claude, and each subscription only carries half my day.
You also get insurance. When one tool has a bad day, and they all have bad days, the other is right there.
The $100+ tiers make sense at the point where ONE of the tools has become your primary workhorse and its half of the split is still hitting caps. That is a great problem to have, and you will know when you have it. If that fork is where you are, the within-Claude version of this decision is Claude Pro vs Claude Max.
Does the Fable 5 change move the $20-vs-$20 verdict?
Yes. It actually changes the math, and I want to be straight about that rather than quietly patching a table.
Claude's $20 no longer including the newest model makes sense from their side - Fable would eat a $20 allowance in minutes. But it means that at the same price, ChatGPT Plus still includes its frontier reasoning model and Claude Pro does not.
So if what you want is the most frontier model your $20 can buy, go compare the benchmarks yourself. If Sol at extra-hard effort competes with Opus 5, then that is a genuinely different tier of value: a better model for the same price.
There is a second thing I did not appreciate until I was paying for both. ChatGPT is straight up more generous about resetting limits. Do not be surprised if once or twice a month those limits just get reset on you. I did not experience that until I was on the bandwagon, and now I can attest to it.
None of that makes Claude the wrong pick. Everything in the "where each one wins" section above still holds - depth, instruction-following, and design are still why I keep it. It does mean the honest 2026 framing of this page is narrower than it was: at $20 versus $20, ChatGPT gives you more frontier model and more forgiveness; Claude gives you a better deep-work tool with a harder ceiling.
Verdict: pick by the person you areFirst AI subscription, general work (email, documents, planning, everyday questions): ChatGPT Plus. It is the better all-rounder and the friendlier on-ramp, and you will use it for personal life too: meal plans, budgets, all of it.
Your work is writing, analysis, or anything where the output must follow instructions exactly: Claude Pro, and accept that the weekly cap is the price of depth at $20.
AI does real work for you every single day: both, $40 total. Split the load, double the limits, route each task to its specialist.
You are already slamming into caps on a split setup: that is the upgrade signal for a $100+ tier on whichever side does your heavy lifting.The number to remember: 160 messages every 3 hours on one side, one shared weekly bucket on the other. Match that to your actual day and the choice makes itself.
Whichever plan you pick, put it to work the same day: the 15 workday AI prompts at /start run on either tool and cover the exact tasks these subscriptions are for.
If the next question is what to do with these subscriptions once you have them, start with Claude Cowork vs Claude Code for the Claude side, and my breakdown of when you need automation at all for the bigger picture.
Published July 3, 2026. Last reviewed July 31, 2026, when the Claude Pro models row was corrected: Fable 5 left Pro's included usage limits on July 19, 2026 and now runs on usage credits. Pricing and limit figures rechecked that day against claude.com/pricing, Anthropic's Fable 5 plan page, the Anthropic usage-limit support page, chatgpt.com/pricing, and OpenAI's official Plus limits help article. These numbers change often; both companies' pages are the source of truth.This post is part of Claude at Work, the hub with every plan decision, task comparison, and setup guide for using Claude at your job without code.
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.
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.
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.
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 a surface area 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.
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.
Claude Projects and Custom GPTs solve the same problem: you keep re-pasting the same background into a chat every morning. Claude Projects give you a workspace with saved instructions and reference files that every chat inside it already knows. Custom GPTs turn that same setup into a shareable assistant that other people can use too.
The short decision rule: if the assistant is just for you, use whichever tool you already pay for. If you need to hand it to other people, Custom GPTs are easier to share. And there is a decent chance you do not need either one yet. More on that below.
Quick comparisonClaude Projects
Custom GPTsWhat it is
A workspace inside Claude with saved instructions and files
A configured assistant inside ChatGPTBuilt for
Your own recurring work
Assistants you hand to other peopleSetup
Custom instructions plus project knowledge files
Instructions, knowledge files, optional actionsSharing
Inside a Claude Team or Enterprise workspace only
Direct link, workspace, or the public GPT StoreExtra powers
Skills, reusable instruction packs Claude loads when relevant
Actions, which let the GPT call other apps' APIsCost to build
Included on Claude's free plan, with limits
Requires a paid ChatGPT planCost to use
Free with limits, more on paid plans
Free users can use existing GPTsDoes Claude have an equivalent to Custom GPTs?
Yes, mostly. Claude Projects are the equivalent for personal use.
A Project holds two things: custom instructions (how Claude should behave in this context) and project knowledge (the files you would otherwise re-upload every time). Every new chat inside the project starts with all of that already loaded. Projects also support Skills now, which are reusable instruction packs Claude pulls in when a task calls for them, like a house style for documents or a specific report format.
What Claude does not have is a store. You cannot publish a Project to a public gallery or send a coworker a link to "your assistant." Sharing only works inside a Claude Team or Enterprise workspace.
So the honest version of the answer: for "an assistant configured for my own work," Claude matches Custom GPTs. For "an assistant I can hand to anyone," it does not.
What is a Claude Project, in plain English?
Think of it as a folder that remembers.
Say you are an HR manager. You create a project called "Policy Questions," upload the employee handbook and your benefits summary, and write instructions like "answer questions using only these documents, quote the relevant section, and flag anything the documents do not cover." From then on, every chat in that project answers from your actual handbook instead of generic HR advice.
A teacher might keep one project per course: syllabus, rubric, and a note about reading level. A project manager might keep one per client: status report template, stakeholder names, the tone the client expects.
The win is not that Claude gets smarter. It is that you stop spending the first five minutes of every session rebuilding context. I run my own recurring work this way, and the setup pays for itself in the first week. If you want to see what a working example looks like end to end, here is my Claude SEO workflow. Different job, same pattern: instructions once, files once, then every chat starts warm.
What is a Custom GPT, in plain English?
A Custom GPT is a pre-configured version of ChatGPT with its own name, instructions, and knowledge files. You build it once through a conversational setup screen, no code involved, and it behaves the same way every time anyone opens it.
Two things make Custom GPTs genuinely different from a Claude Project:Sharing. You can send a GPT to a coworker as a link, share it across your company workspace, or publish it in the GPT Store. If you build a "Job Description Drafter" for your HR team, the whole team gets the exact same assistant without configuring anything.
Actions. A GPT can be wired to call outside services, so it can look something up or send data somewhere instead of just chatting. In practice, setting up actions requires API details most people will never touch. That is fine. The sharing alone is the reason most teams pick Custom GPTs.One cost note: anyone can use existing GPTs for free, but building your own requires a paid ChatGPT plan.
Which one fits how you work? Three questions
You can make this decision in five minutes. Ask these in order.
1. Which subscription do you already pay for?
This settles it for most people. Do not switch from ChatGPT to Claude, or the reverse, to get this one feature. Both products have a good version of "saved context plus instructions." The tool you already use, with the history and habits you already have, wins by default.
2. Do you need to share the assistant, or just use it yourself?
Just you: Claude Projects or ChatGPT Projects, whichever side you are on. Done.
Your team needs the same assistant: Custom GPTs win clearly. A link your coworkers can open beats a setup doc you have to walk five people through. Claude can share projects too, but only if everyone is in the same paid Team workspace, which is a bigger ask than "click this link."
3. Where does your work context live?
If your context is documents you can upload, like handbooks, templates, rubrics, and past examples, both tools handle it well. If your context lives inside other systems you would need to connect, neither one solves that cleanly out of the box, and you should solve the document version first anyway.
What about ChatGPT Projects vs Claude Projects?
If you are on ChatGPT and the assistant is just for you, skip Custom GPTs entirely. ChatGPT has its own Projects feature: chats grouped in a folder, with files and instructions attached, and memory scoped to that project.
For solo use, ChatGPT Projects and Claude Projects are close to interchangeable. Both hold files. Both hold instructions. Both keep your chats organized by context instead of one endless sidebar. People argue about which model writes better, and that is a real preference, but the projects features themselves are not the deciding factor.
The clean way to remember the whole lineup:Projects (Claude or ChatGPT) = context for you
Custom GPTs = a configured assistant for other peopleDo you actually need either one?
Honestly, maybe not yet.
If you use AI a few times a week for varied tasks, a project is a filing cabinet for things you do not file. What gets you most of the value is one well-written, reusable prompt: who you are, what you need, what format you want back, saved in a doc and pasted when needed. No setup, no subscription decision, works in any AI tool.
I keep 15 reusable prompts that cover most workdays on my start page, and that is where I would point anyone who has not built the habit yet.
The graduation rule is simple: when you catch yourself pasting the same prompt plus the same two or three files more than three times a week, move it into a Project. The repetition is the signal. Before that, the prompt is enough.
When a Project stops being enough
There is a ceiling, and it is worth knowing where it is before you hit it.
A Project still requires you to show up, open the chat, paste the new input, and carry the output somewhere. If you are running the same multi-step routine on a schedule, like every Monday you collect updates, format a report, and send it to the same people, that is not a chat problem anymore. That is a workflow.
The signs you have outgrown the chat window:the input arrives on a schedule, not when you feel like it
the output always goes to the same place
you are the only step in the middleWhen that describes your task, look at the workflows I have documented to see what the next level looks like. And if you are wondering whether you need actual automation tools or are fine staying in the chat, I wrote a sibling decision page for exactly that: ChatGPT vs n8n, on whether you need automation at all. If what you actually want is Claude doing the task instead of chatting about it, the fork is Claude Cowork vs Claude Code.
Most people do not need that level. But knowing the ceiling exists keeps you from forcing a chat tool to do a scheduler's job.
FAQ
Does Claude have an equivalent to Custom GPTs?
Yes. Claude Projects are the closest equivalent: saved instructions plus uploaded reference files that every chat in the project can use. The main thing missing is public sharing. There is no Claude version of the GPT Store.
Can you share a Claude Project the way you share a Custom GPT?
Only inside a Claude Team or Enterprise workspace. There is no public link or store. If you need to hand a configured assistant to people outside your workspace, a Custom GPT is the easier path.
Should I switch from ChatGPT to Claude just to get Projects?
No. ChatGPT has its own Projects feature that covers the same solo use case: files, instructions, and chats grouped in one place. Switching subscriptions for this one feature is not worth it.
Do I need a paid plan to use Claude Projects or Custom GPTs?
Claude includes Projects on the free plan with usage limits. ChatGPT lets anyone use existing Custom GPTs for free, but building your own requires a paid plan.This post is part of Claude at Work, the hub with every plan decision, task comparison, and setup guide for using Claude at your job without code.
Most people asking this question do not need n8n.
Here is the test. If a task happens when you ask for it, and you are sitting there while it happens, a good reusable prompt covers it. n8n earns its place in exactly one situation: the same task has to run on a schedule or a trigger, without you, across two or more apps. That describes far fewer tasks than YouTube makes it sound.
I use both tools every week, so this is not tool loyalty. It is more like "do not buy a forklift to carry groceries."
What is the actual difference between ChatGPT and n8n?
They are not competitors. They do completely different jobs.
ChatGPT (or Claude) is a thinking tool. You give it something, it gives you something back. Summarize these meeting notes. Draft this awkward email. Turn 40 survey responses into the five complaints that actually matter. You are present for every exchange, and that is fine, because the task only exists when you ask for it.
n8n is plumbing. It moves data between apps when something happens. A form gets submitted, so a row lands in a spreadsheet and a Slack message goes out. Nobody is sitting there. That is the entire point of it.
The confusion comes from demo videos where n8n has an AI step in the middle, so it looks like "ChatGPT, but automated." True as far as it goes. But that AI step does the same job ChatGPT does in your browser tab. The real question is never which tool is smarter. The question is whether the task needs to happen without you.
How do you know if you need n8n? Ask 3 questions
Run any task you are thinking about through these:Does it repeat on a schedule or a predictable trigger? Every Monday morning. Every time a form comes in. Every new invoice.
Does it cross two or more apps? Form to spreadsheet to email. Inbox to tracker to Slack.
Does it need to run when you are not watching? Overnight, during meetings, while you are on leave.Three yeses: automation software is worth a look. Two or fewer: a saved prompt almost certainly covers it, and it covers it today, for free, with nothing to maintain.
Real examples:"Summarize my meeting notes into action items." You are present, one app, on demand. Prompt.
"Help me draft replies to difficult parent emails." On demand, you review every word anyway. Prompt.
"Every Friday at 4pm, pull this week's form responses, summarize the complaints, and email me the digest." Scheduled, three apps, runs alone. That is a real n8n job.
"When a new applicant submits the intake form, score them against the role requirements and add the score to my tracking sheet." Triggered, multiple apps, unattended. Also a real n8n job.Notice the pattern. The prompt tasks are about judgment and wording. The automation tasks are about moving the same data the same way, over and over, with nobody watching.
ChatGPT vs n8n: quick comparisonThe task
UseSummarize notes, docs, or transcripts on demand
ChatGPT promptDraft or rewrite emails in your voice
ChatGPT promptTurn messy feedback into clear themes
ChatGPT promptPrep for a meeting from an agenda and past notes
ChatGPT promptMove form responses into a sheet automatically
n8nSend a weekly report without touching it
n8nWatch an inbox and route requests to the right person
n8nScore or sort new entries the same way every time
n8n with an AI stepAnything you do once or twice, ever
Neither. Just do it.If your whole list lands in the top half of that table, you have your answer. Save your prompts and skip the software.
What does n8n really cost if you cannot code?
This is the part the tutorials skip, so let me be the honest friend here.
Money. n8n Cloud starts around $25 a month. The "free" self-hosted version needs a server, usually $5 to $10 a month, plus you become responsible for installing it, updating it, and backing it up. If words like Docker mean nothing to you, self-hosting is not free. It is a part-time hobby.
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.
Setup time. Your first real workflow takes an afternoon, not the 8 minutes the video showed. Most of that time is not building. It is connecting accounts: API keys, permission screens, and figuring out why Google says no. Plan 3 to 4 hours for workflow number one.
Debugging. Workflows break silently. A password-like credential expires. An app changes how it sends data. The workflow you built in March fails quietly in June, and you find out because the Friday report never showed up. Then you are staring at a red error node and a message written for engineers.
Maintenance. Every workflow you build is a small machine you now own. A few simple ones might need an hour a month. But it never goes to zero, and you are the repair person.
None of this means avoid n8n. It means n8n has to earn that overhead. A saved prompt has zero of these costs, which is why it should always be your first move.
When is a reusable prompt all you need?
If you are present when the task happens, the prompt is the automation.
The trick is writing it once, properly, and saving it, instead of improvising a new mediocre prompt every time. A reusable prompt spells out four things: who the AI should act as, what input you will paste in, the exact format you want back, and one example of a good output. That takes 15 minutes to write and pays you back every week after.
Then keep your prompts somewhere you can grab them: a doc, a notes app, whatever you will actually open. If you want a starting set, I keep 15 reusable work prompts here, built for exactly this kind of on-demand work.
The honest comparison: a prompt like this saves you 20 minutes every time you use it, costs nothing, and cannot break while you sleep. That is a high bar for automation software to clear.
When does n8n actually make sense?
Volume and absence. Those are the two things that flip the answer.
If 30 form submissions arrive every week and each one needs the same three steps, you are not doing judgment work anymore. You are being a conveyor belt. Same if the task has to fire at 6am or while you are on vacation. No prompt fixes "I was not there."
If a task passes the 3-question test, the pattern that holds up is boring: a trigger, a step that gathers the data, an AI step for any judgment call, a human approval for anything customer-facing, then route the result. I wrote up that exact pattern in the n8n AI agent workflow if you get to that point.
Also, an option nobody mentions: you do not have to build it yourself. If the task clearly qualifies but the setup sounds miserable, ask IT, or pay a freelancer for a day. A capable n8n freelancer can build a clean first workflow in a day. The building is the cheap part. The maintaining is what you are really signing up for, so decide who owns that before anything gets built.
One more fork in the road: if you or a technical coworker work in code all day, the comparison changes shape. That version of the decision is in Claude Code vs n8n.
What I would do first
Skip the software question for one week and do this instead:List every task you repeat weekly. Most people find 8 to 12.
Run each one through the 3 questions: schedule or trigger, 2+ apps, runs without you.
For everything that fails the test, write and save the prompt today. That is 15 minutes per task.
For the one or two that pass, score them with the automation priority audit before you sign up for anything. It forces the time-saved versus time-spent math that the excitement skips.When I run this with people, the usual result is nine prompt tasks and one genuine automation candidate. That ratio is normal. It is also good news: you can fix most of your repetitive work this afternoon, without buying, hosting, or maintaining anything.
The boring answer wins here. Prompts first. n8n only when a task proves it deserves a machine.
FAQ
Is n8n better than ChatGPT?
Neither is better. They do different jobs. ChatGPT answers when you ask it something. n8n moves work between apps on a schedule or trigger, without you present. Most people only need the first one.
Can ChatGPT replace n8n?
For on-demand tasks where you are present, yes. A saved prompt covers summarizing, drafting, and rewriting. ChatGPT cannot replace n8n for tasks that must run unattended across multiple apps.
Do I need to know how to code to use n8n?
You can build simple workflows without code, but it gets technical fast: API credentials, error logs, and data formats. Budget real time for setup and debugging, or pay someone to build it.
Is n8n free?
The software can be self-hosted free, but you pay for a server, plus your time for setup, updates, and fixing broken workflows. n8n Cloud starts around $25 a month and removes the server work.This post is part of the n8n AI agents hub: definitions, tutorials, workflow patterns, and the build-vs-run decision pages in one place.
Direct Answer
Package the offer as a small website project plus a monthly retainer that owns one automation. The AI coding part is delivery, not pitch.
Local owners do not buy AI. They buy more booked jobs, faster lead responses, fewer no-shows, and a site that does not embarrass them. You sell that. You deliver it with Claude Code drafting the site and n8n owning the workflow that produces the result. The offer reads: a flat-fee site, then a monthly fee for one workflow you own end to end. One scope, one outcome, one invoice.
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.
Use This When And When To Skip ItUse this
Skip thisYou can ship a small site and one working n8n workflow in a weekend
You have never deployed either and want to learn on a paying clientYou will answer the phone, drive to a meeting, and fix a broken Zap on a Saturday
You want a fully remote, faceless buyerYou want predictable monthly revenue from 3 to 8 clients
You want one $100k contract and no support loadYou like scoping in plain English and writing one-page proposals
You need a brand, a deck, and a sales team to feel readyTradeoff: this is a feet-on-the-ground offer. The reward is fast cash and a real reference. The cost is showing up.
The System
Trigger -> referral, local search, in-person ask, or a clear pain ("we miss calls")
Inputs -> one decision-maker, current website, current lead flow, one number they want to move
Decision -> site project + which single workflow gets the retainer
Claude step -> drafts site, intake form, and n8n workflow JSON inside your repo
Artifact -> deployed site, one live workflow, a 1-page operating doc the owner can read
Approval -> owner reviews the workflow output for one week before it runs unattended
Output -> monthly retainer invoice, monthly result note (what ran, what failed, what changed)
Feedback -> the one number they wanted to move, checked monthlyThe model writes the code. The workflow owns the result. You own the relationship and the gate.
Steal This Workflow
This is the shape of the offer, broken into pieces you can copy.
1. Pick one outcome per client. Not "we will do your marketing." Pick one of: faster reply to inbound leads, automated review requests after a job closes, appointment reminders that cut no-shows, or a seasonal offer that fires on a weather trigger. One outcome means one workflow.
2. Scope the entry project. A 5 to 7 page site, a contact form that posts to a webhook, and one CRM or sheet as the source of truth. Fixed price. Two-week delivery. Written scope, written exclusions.
3. Draft with Claude Code in a real repo. Open Claude Code inside the client repo, hand it the brief, and let it write the Astro or Next pages, the form handler, and the n8n workflow JSON. Read the diff. Reject the parts that drift. Do not paste from a chat tab into production.
4. Run the workflow JSON through a real audit. Community templates and AI-generated JSON both ship credentials, webhooks, and code nodes you did not write. Pass anything before it goes live through the n8n workflow JSON auditor.
5. Build and QA before you hand it over.
npm run build
npm run qa:searchThe site is the proof. A broken sitemap or missing title tag tells the owner the work is sloppy.
6. Sign the retainer on one workflow. Monthly fee. One workflow owned. The contract names the workflow, the trigger, the input source, the output, and what counts as a failure. If they want a second workflow, that is a second retainer.
7. Send a one-page monthly note. Three lines: what ran, what failed, what you changed. The note is the renewal mechanism. Most local owners never get this from a vendor.
8. Use a planner to keep scope honest. When the owner asks for a second workflow inside the same fee, open the Claude Code n8n workflow planner and show them the node map. A picture turns "one more thing" into "that is a second project."
What This Looked Like For This Page
This page started as a Reddit source signal in the weekly AEO run, not as an idea Chris had in the shower.
The run pulled 936 raw Reddit RSS entries, scored 314 candidates, generated 25 AEO briefs, and marked 9 of those as publish_now. This topic passed because:Gate
Why it passedSource language
The thread used "first real AI coding income" and "local service business" instead of abstract "AI consulting" languageArtifact
The answer maps cleanly to one project plus one workflow plus one monthly note, which a reader can copyCluster fit
It links into Claude Code, n8n, the workflow planner, and the AI stack post without forcingThe page is research-inspired by the thread, not a claim that Chris ran these specific clients.
What Most People Get Wrong
The mistake is leading with "AI" in the sales conversation.
The owner is trying to decide if their phone will ring more next month. They do not care about Claude versus GPT. They care if the new system breaks their existing scheduling. The pitch should sound like "you are losing 4 leads a week because nobody replies in under an hour, here is what I will do about it for a fixed fee" and not like a feature list.
Three more breakages that show up in the threads:Scope creep eats the retainer. Owners ask for "just one more thing" until the monthly fee becomes a part-time job. Name the workflow in the contract. Anything else is a new project.No approval week. The workflow goes live on day one, fires on the wrong record, and the owner cancels. Give it a one-week review window where every output gets manually read before it sends.The retainer has no artifact the owner can read. They cannot see what they are paying for. The monthly one-page note is the artifact.How I Would Build This In Ship Lean
The Ship Lean version uses Claude Code for the build, n8n for the running workflow, and the repo for the audit trail.
Claude Code in the client repo. Each client gets a small Astro or Next repo with the voice and brand notes as files Claude Code reads on every run. The model never re-negotiates tone, link structure, or schema.
n8n owns the running workflow. The n8n AI agent workflow pattern handles trigger, decision, and approval. The lead intake or review request runs through the same shape as the n8n AI agent tutorial. One human gate before anything customer-facing fires.
Audit anything you did not write. Community JSON and AI-generated JSON both need a pass through the n8n workflow JSON auditor before activation.
The stack stays small. Repo, Claude Code, n8n, one CRM or sheet, one site host. The longer AI stack for solo founders writeup goes deeper on what to keep and what to cut.
The SEO layer for your own offer. Use the same workflow you use for clients on yourself. The Claude SEO workflow post explains how to wire Claude as a workflow step instead of a chat tab so your own service page is not the weakest part of the funnel.
Next Step
If you are sitting on AI coding skills and no offer, do one thing this week. Pick a local business you already know, write the one-page proposal as a fixed-fee site plus a one-workflow retainer, and send it.
If you want to map the workflow before the conversation, the Claude Code n8n workflow planner sketches the trigger, intake, decision, approval, and result so you walk in with a node map instead of a vibe.
Source Signal
Research-inspired by a Reddit thread describing a builder's first real AI coding income from a local service business: a website project, a monthly growth retainer, and a larger internal automation. Treat the thread as one operator's note, not as Chris's results. Original: the r/SaaS thread, "My first real AI/coding income case."
Related AEO PagesClaude SEO workflow
Weather-triggered HVAC booking workflow
Learning AI workflows from scratch
Pre-launch social media automationFAQ
Why pitch local service businesses instead of SaaS customers?
Local owners pay for outcomes they can see this month. They are the right buyer for an operator who is still learning the sales motion.
What is the actual offer shape?
A fixed-fee site project as the entry, then a monthly retainer that owns one workflow end to end.
Where does Claude Code fit?
Claude Code drafts the site and the workflow JSON inside your repo. You read the diff and approve the deploy.
How do I price it without guessing?
Flat fee for the site, flat monthly fee for one workflow. Skip hourly until you know how long the work takes.
When should I skip this offer entirely?
Skip it if you will not answer the phone, drive to one meeting, or maintain a workflow you shipped six months ago.
Direct Answer
Use Claude as one step inside a defined workflow, not as a chatbot you re-prompt every week.
A chatbot has no memory of your site, no schema rules, no internal-link map, and no approval gate. A workflow has a trigger, inputs, a decision rule, an artifact, and a review step. Claude only sees the inputs you load. The output is the same shape every time. The system improves because you fix the workflow, not the prompt.
The smallest version: pull Search Console data on a schedule, score the query, brief the page in a file in your repo, draft in Claude Code with the repo as context, edit against a checklist, build, QA, publish. Same path every run.
Use This When And When To Skip ItUse this
Skip thisYou publish 2+ pages a month and they keep drifting in voice
You are writing one-off pages with no clusterYou have a repo with existing posts, voice notes, schema, and an internal-link map
You have fewer than five existing postsGSC is connected and showing impressions you are not converting
You have no GSC data yet. Fix that firstYou want the same shape every week without re-explaining tone
You enjoy the chat-window flow and only ship monthlyTradeoff: a workflow takes one weekend to wire. A chat window takes zero. The workflow pays back the second week.
The System
Trigger -> weekly cron or new GSC opportunity
Inputs -> GSC query, target page, internal-link map, schema rules, voice profile
Decision -> answer page, comparison, workflow, tool, or refresh?
Claude step -> draft against the brief with the repo as context
Artifact -> markdown file, frontmatter, internal links, FAQ schema
Approval -> human read for voice, claims, and receipts
Output -> commit, build, deploy, ping IndexNow
Feedback -> GSC impressions, CTR, position at 14/30/50 daysClaude owns: writing the draft, expanding the brief, drafting the FAQ, proposing internal links.
Claude does not own: deciding what to publish, approving claims, hitting publish, measuring results.
That split is the whole point. The model is one node. The workflow is the system.
Steal This Workflow
This is the actual shape that runs on this site. Copy the file paths, swap your repo.
1. Pull the data weekly.
npm run gsc:refresh
npm run reddit:aeo-scout
npm run aeo:weeklyOutput: a ranked list of real questions and queries with enough signal to become an answer page.
2. Pick the page type by query shape.Query shape
Asset"what is X"
Answer page + FAQ schema"X vs Y"
Comparison page"how to X"
Tutorial or workflow page"X calculator / template / planner"
Free tool"best X for Y"
List or stack page3. Write the brief as a file in the repo, not a chat message.
outputs/aeo-page-briefs/<run>/briefs.mdThe brief must contain the source query, the exact source language, the direct-answer angle, the artifact the page will ship, and the internal links it should hit.
4. Hand the brief to Claude with the repo as context.
claude --model opus -p "Read the brief at outputs/aeo-page-briefs/<run>/briefs.md. Read the voice profile. Read existing posts in src/content/posts/ so you do not duplicate angles. Draft the page per the AEO standard. Return markdown only."Claude reads voice, existing posts, schema rules, and the internal-link map from the repo. It does not re-negotiate tone.
5. Run the deterministic QA gate before you touch the build.
python3 /Users/chrisalarcon/Documents/Productivity/.claude/skills/ship-lean-aeo-page-factory/scripts/score_aeo_page.py path/to/draft.mdIf it returns below 8.5, revise. If any category scores 0, the page fails even at a high total.
6. Build, QA, deploy.
npm run build
npm run qa:searchCheck: title and meta unique, sitemap includes the URL, canonical correct, schema present, no broken internal links.
7. Ship and inspect.
After deploy, submit the URL to IndexNow and inspect it in GSC:
node scripts/gsc-inspect.mjs https://yourdomain.com/blog/<slug>8. Measure at 14, 30, and 50 days. Refresh the pages with impressions but weak CTR before writing new ones.
Every step has an owner, an input, an output, and a gate. The Claude step is one row in that table.
What This Looked Like For This Page
This page did not start with "write me an SEO post about Claude."
It started as a recent Reddit source signal, then moved through the same page-factory path:
npm run reddit:aeo-scout -- --run-name 2026-05-14-weekly-aeo
npm run aeo:weekly -- --run 2026-05-14-weekly-aeo --run-name 2026-05-14-weekly-aeoThat run pulled 936 raw Reddit RSS entries, scored 314 candidates, generated 25 AEO briefs, and marked 9 as publish_now.
This topic won because it had the three things a real AEO page needs:Gate
Why it passedSource language
The question was not abstract. People were talking about using Claude for SEO work, not "AI content strategy" as a vague categoryArtifact
The answer could become a workflow map with commands, repo paths, QA gates, and a skip ruleCluster fit
It naturally links into Claude Code, n8n, GSC, AEO pages, and Ship Lean's content systemThe draft then went through an Opus pass, a Codex QA pass, and this local gate:
python3 /Users/chrisalarcon/Documents/Productivity/.claude/skills/ship-lean-aeo-page-factory/scripts/score_aeo_page.py src/content/posts/how-to-use-claude-as-an-seo-workflow/index.mdThat is the part most "AI SEO" content skips. The model can write the page, but the workflow decides whether the page deserved to exist.
What Most People Get Wrong
The mistake is treating Claude like a search assistant.
Open a fresh chat. Paste a keyword. Ask for an outline. Ask for a draft. Ask it to rewrite the intro. Next week, do it again with a different keyword. The output is fine. Nothing compounds.
Three specific things break.No memory of your site. Claude does not know what you already published, what you internally link, or what your schema looks like. You end up with thin pages that compete with each other for the same query.No decision rule. Every chat is a fresh negotiation about angle, length, and tone. You re-explain your voice on Monday and again on Friday.No approval gate. A chat window encourages "looks good, ship it." A workflow forces a checklist read: direct answer up top, no invented metrics, internal links present, schema correct.The fix is not a better prompt. The fix is a workflow that uses the prompt as one step.
How I Would Build This In Ship Lean
The Ship Lean version uses Claude Code for judgment steps and n8n for routing.
Inputs live in the repo, not in chat.Voice profile and brand rules as files Claude Code reads on every run.
A list of existing posts and their primary queries so the model does not propose duplicate angles.
A schema reference for BlogPosting and FAQPage so the FAQ block is always valid.
An internal-link map of tool, workflow, and pillar pages.Claude Code as the draft step. Use the Claude Code n8n workflow planner to sketch where Claude sits in the pipeline. The model reads the brief and the repo. It writes one draft. It does not pick the topic.
n8n as the router. Use the n8n AI agent workflow pattern for triggers and routing. n8n pulls GSC data on a schedule, queues briefs, posts drafts to a review channel, pings IndexNow after deploy. The same approval pattern from the n8n AI agent tutorial keeps a human in the loop before anything goes live.
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.
Importing community workflow JSON safely. If you grab community n8n workflows for SEO tasks, run them through the n8n Workflow JSON Auditor before activating. Unknown JSON can include credentials, webhooks, and code nodes you did not write.
The stack stays small. Claude Code, n8n, GSC, the repo. That is enough. The full AI stack for solo founders post goes deeper on what to keep and what to cut.
Next Step
If you are still pasting prompts into a Claude chat for SEO work, do one thing this week. Pick the next page you plan to write. Build the brief in a file in your repo. Open Claude Code in that repo. Run the draft step there instead of in a chat tab.
If you want the same routing layer Ship Lean uses, the Claude Code n8n workflow planner maps the trigger, brief, draft, approval, and publish nodes for you. The model did not change. The workflow did.
Source Signal
Research-inspired by a Reddit thread where an operator described moving SEO work out of Claude chat and into a defined workflow. Treat the thread as one builder's note, not as proof of Chris's results. Original: the r/ClaudeCode thread, "Guys, I stopped using Claude as a chatbot for SEO work."
The pattern matches the broader Ship Lean rule: the model is one step, the workflow is the system, and the approval gate is non-negotiable.
Related AEO PagesAI coding local service offer
Weather-triggered HVAC booking workflow
Learning AI workflows from scratch
Pre-launch social media automation
Self-hosted n8n Zapier gotchasFAQ
What does it mean to use Claude as an SEO workflow?
Treat Claude as one step in a defined pipeline: GSC query in, brief in, repo context in, one draft out, human approval before publish.
Do I need Claude Code or will Claude.ai work?
Claude.ai is fine for one-off drafts. Claude Code is stronger because it reads your repo, voice profile, and internal-link map on every run.
Where does n8n fit?
n8n owns triggers and routing: pull GSC on a schedule, queue briefs, post drafts to review, ping IndexNow after deploy. Claude owns the judgment steps.
Can I automate the whole thing end to end?
No. Keep a human approval gate. Automate the boring steps. Approve the taste calls.
When should I skip this entirely?
Skip it if you publish under one page a month, have no existing cluster, or have no GSC data yet. Wire the data first.This post is part of Claude at Work, the hub with every plan decision, task comparison, and setup guide for using Claude at your job without code.
Direct Answer
Self-hosted n8n can be cheaper than Zapier when automation volume makes the bill a real business constraint, but the gotcha most tutorials skip is credentials. Zapier holds OAuth tokens you cannot export, so every workflow you migrate needs a fresh OAuth or API key, which means downtime per integration if you migrate sequentially.
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 migration order that does not break production: lowest-stakes Zaps first (internal notifications, log writes), medium-stakes second (enrichment, sheet sync), highest-stakes last (billing, customer-facing). Run the new n8n workflow in parallel with the old Zap for a week. Cut over only after the n8n version has produced the same output for seven days. The cost math is real. The time math is the part most posts skip.
Use This When And When To Skip ItUse this
Skip thisThe Zapier bill is a real line item and the workflows are stable
Low volume, no automation cost painYou have one weekend to migrate the low-stakes layer and a month for the rest
You want everything moved by MondayYou are comfortable with Docker, a managed host, or n8n Cloud
You have never deployed anythingAutomation cost is a real line item, not a complaint about the bill
The bill is small and the business is bottlenecked elsewhereTradeoff: this migration costs a weekend plus a month of parallel running. The reward is lower platform cost and code-level access to your workflows. The cost is owning the uptime.
The System
Trigger -> "Zapier is now a real line item and I want code-level access"
Inputs -> Zap inventory (export the list), task volume per Zap, integrations used
Decision -> migrate in 3 waves (low, medium, high stakes); parallel run for 7 days each
Hosting -> managed first (Hetzner, Railway, n8n Cloud); Docker only after 10+ workflows
Approval -> each Zap stays live until the n8n version has produced identical output 7 days
Output -> n8n workflows replacing Zaps in waves, with a documented credential map
Failure -> the old Zap is the rollback for 7 days; do not delete it until parity is real
Feedback -> task-run cost, error rate, time spent maintaining; reviewed monthlyThe migration is not "rebuild every workflow." It is "rebuild in waves, run in parallel, cut over after parity."
Steal This Workflow
This is the migration order and the credential map. Eight steps, three waves.
1. Export the Zap inventory. List every Zap, its trigger, its action, its task volume, and the integrations involved. A 30-Zap stack will have 8 to 12 unique integrations. The credential count, not the Zap count, is the real migration cost.
2. Pick the host before you build the first workflow. Managed: Hetzner with the n8n one-click, Railway, or n8n Cloud. Docker on your own VPS is a second project. Do not make it your first.
3. Wave 1: low-stakes Zaps. Internal Slack notifications, log writes to a sheet, daily digest emails to yourself. Migrate 3 to 5 of these in one weekend. They prove the host, the credentials, and your workflow vocabulary.
4. Build n8n workflows with a planner first. Use the Claude Code n8n workflow planner to map the trigger, decision, and action before you drag a single node. Walking into n8n with a map cuts the build time in half.
5. Audit every workflow JSON you did not type yourself. Templates from the n8n community library, AI-generated JSON, and shared workflows from forums all ship credentials, webhooks, and code nodes you did not write. Pass each through the n8n workflow JSON auditor before activation.
6. Wave 2: medium-stakes Zaps. Lead enrichment, sheet sync, CRM updates. Run each n8n workflow in parallel with the old Zap for 7 days. If outputs match, cut over. If not, find the difference.
7. Wave 3: high-stakes Zaps. Billing, customer-facing automations, anything that affects revenue or invoices. Same 7-day parallel run. Do not migrate two high-stakes Zaps in the same week.
8. Document the credential map. A single file: integration, OAuth or API key, where the credential lives, expiry date, owner. This file is what saves you in 9 months when a token rotates.
What This Looked Like For This Page
This topic came from the weekly AEO run, not from a stack Chris migrated this week.
The run pulled 936 raw Reddit RSS entries, scored 314 candidates, generated 25 AEO briefs, and marked 9 as publish_now. This one passed because:Gate
Why it passedSource language
The thread used "spent 24 hours rebuilding my Zapier stack on self-hosted n8n" and "the gotcha that nobody warned me about" in real builder voiceArtifact
The answer maps to a 3-wave migration order with a credential map a reader can copyCluster fit
It links into n8n, Claude Code, the workflow planner, and the JSON auditor without forcingThe page is research-inspired by the thread, not a claim that Chris ran this exact 24-hour migration.
What Most People Get Wrong
The mistake is treating this as a one-weekend project across the whole stack.
Three failure modes:They migrate everything in one weekend. Day three, a billing Zap fails silently, an invoice does not go out, a customer churns. The fix is the 3-wave order and the 7-day parallel run. Slow is fast here.They underestimate credentials. A 30-Zap migration is really an 8 to 12 integration migration. Each integration needs a fresh OAuth, a documented expiry, and a test run. Most teardown posts brag about workflow count and skip credential count.They self-host before they need to. Managed n8n is fine for the first 6 months. Docker on a VPS is a separate skill. Do not stack two unfamiliar things in one weekend.The cost savings are real. The time cost is also real. If you ignore the time cost, the savings are a lie.
How I Would Build This In Ship Lean
The Ship Lean version uses managed n8n first, the planner for every workflow, and the auditor on anything imported.
Start managed, move to self-hosted later. Hetzner with the n8n one-click or n8n Cloud handle the first 10 workflows. Self-managed Docker is the second project, not the first.
Plan every workflow before you build. The Claude Code n8n workflow planner sketches trigger, decision, action, and gate. Walk in with a map, walk out with a workflow.
Use the n8n agent pattern for the gated workflows. Anything customer-facing follows the n8n AI agent workflow pattern. The shape from the n8n AI agent tutorial handles trigger, judgment, approval, and action.
Audit every imported JSON. Run it through the n8n workflow JSON auditor. This step catches credentials in code nodes and webhooks pointing at hosts you do not own.
The stack stays small. One host, one n8n instance, one credential map, one log sheet. The AI stack for solo founders post goes into what to keep and what to cut.
Use the same SEO workflow on your migration writeup. A teardown post about your migration is one of the highest-converting pieces of content a builder can ship. The Claude SEO workflow post shows how to wire Claude as a workflow step instead of a chat tab.
Next Step
If you are paying Zapier more than you want and the stack has 10 or more Zaps, do one thing this weekend. Export the inventory. Pick the 3 lowest-stakes Zaps. Build them in n8n. Run them in parallel for 7 days.
The Claude Code n8n workflow planner gives you the trigger, decision, and action nodes for each migrated workflow in one map. Use it on the first three.
Source Signal
Research-inspired by a Reddit thread describing a 24-hour Zapier-to-self-hosted-n8n migration with real numbers and an unwarned gotcha. Treat the thread as one operator's note, not as proof of Chris's results. Original: the r/n8n thread, "Spent 24 hours rebuilding my Zapier stack on self-hosted n8n."
Related AEO PagesClaude SEO workflow
AI coding local service offer
Weather-triggered HVAC booking workflow
Learning AI workflows from scratchFAQ
Is self-hosted n8n actually cheaper than Zapier?
Sometimes. It depends on task volume, hosting, maintenance, and your comfort owning uptime. Add your time before deciding.
What is the gotcha most tutorials skip?
Credentials. Zapier holds OAuth tokens you cannot export. Every integration needs fresh credentials.
What is the right migration order?
Low-stakes first, medium next, high-stakes last. Parallel run each for 7 days.
Do I need Docker or can I use a managed host?
Use a managed host until 10+ workflows. Docker is a second project.
When should I skip this and stay on Zapier?
When the Zapier bill is not a real constraint, you have no DevOps comfort, or the business is bottlenecked elsewhere.This post is part of the n8n AI agents hub: definitions, tutorials, workflow patterns, and the build-vs-run decision pages in one place.
Chris Alarcon 
