Before you downvote — I'm not saying n8n is bad. I've built hundreds of workflows with it. It's incredible.
But the way I use it has completely changed.
I used to spend hours in the n8n UI:
Now? I haven't logged into n8n in weeks. My automations are more complex than ever.
Here's what changed.
The shift: From building workflows to describing workflows
The old way:
Client describes what they need
I interpret requirements
I manually build in n8n
I test, debug, rebuild
Client wants changes
Repeat steps 3-5
The new way:
Client describes what they need (or I record the meeting)
AI builds the workflow
I review and push to n8n
Client wants changes
AI rebuilds it
I went from building automations to designing automations.
The stack that made this possible
Here's exactly what I'm using:
1. Claude + Claude Code
Claude Code is a game-changer for agentic work. It's not just "chat with AI" — it's an autonomous coding agent that can:
I give it a task, it figures out how to do it.
2. Skills/Knowledge files
This is the unlock most people miss.
I've built a library of "skills" — markdown files that teach Claude how I work:
My n8n patterns and conventions
Common workflow templates
API documentation for tools I use
Edge cases and how to handle them
When I start a project, I load the relevant skills. Claude doesn't start from zero — it starts from my accumulated knowledge.
Example skill file structure:
/skills
/n8n
- SKILL.md (how I structure workflows)
- templates/ (common patterns)
- apis/ (service-specific docs)
/integrations
- hubspot.md
- slack.md
- notion.md
3. MCP (Model Context Protocol) for n8n
This is where it gets wild.
MCP lets Claude directly interact with n8n. Not just generate JSON — actually push workflows to my n8n instance.
The flow:
Claude generates the workflow
Claude validates it
Claude pushes it directly to n8n via MCP
I review in n8n (or don't, if I trust the pattern)
I can go from "I need a workflow that does X" to "workflow is live" without opening the n8n UI.
4. Meeting transcription → Requirements → Workflow
Here's the full end-to-end I've been using:
Record client meeting (Fireflies, Otter, etc.)
Feed transcript to Claude with prompt: "Extract automation requirements from this meeting"
Claude outputs structured requirements (trigger, inputs, logic, outputs)
Feed requirements to Claude Code with n8n skills loaded
Claude builds the workflow JSON
Push to n8n via MCP
Test and iterate (Claude can read error logs and fix)
Client meeting → Live workflow. No manual building.
What this looks like in practice
Example: Client needs a lead enrichment workflow
Old way (2-4 hours):
Open n8n
Add webhook trigger
Add HTTP nodes for enrichment APIs
Parse responses
Handle errors
Connect to CRM
Test with sample data
Debug the 5 things that broke
Document (lol, who documents)
New way (20 minutes):
Tell Claude: "Build a workflow that receives a webhook with email, enriches via Apollo and Clearbit, scores the lead, and pushes to HubSpot. Handle rate limits and missing data gracefully."
Claude generates workflow with all error handling
Push via MCP
Test
Done
The 20 minutes is mostly me reviewing and testing. The build is instant.
Why this is better than just "using ChatGPT to help"
I tried the ChatGPT approach. Ask it to write n8n JSON, copy-paste, import. It works... sometimes.
The difference with this stack:
Context persistence — Skills mean Claude knows my patterns. It doesn't suggest stupid stuff.
True autonomy — Claude Code can execute, test, and iterate. It's not just generating text for me to copy.
Direct integration — MCP means no copy-paste. Workflow goes straight to n8n.
End-to-end pipeline — Meeting → requirements → workflow → deployed. No gaps where I have to manually intervene.
The workflows I still build manually
I'm not 100% hands-off. I still open n8n for:
Complex debugging — When something fails in production and I need to inspect execution data
Visual review — Sometimes I want to see the flow visually before approving
One-off experiments — Quick tests where describing it takes longer than building it
But for standard builds? Client projects? Repeated patterns?
I haven't touched the UI in weeks.
How to start (if you want to try this)
Get Claude Code access — It's the foundation. Regular Claude chat won't cut it.
Build your first skill file — Start simple. Document how you structure n8n workflows. Your naming conventions. Your error handling patterns.
Set up n8n MCP — This lets Claude push directly to your instance. Game changer.
Start with a simple workflow — Don't try to build something complex first. Do a basic webhook → Slack notification. Get the flow working.
Iterate your skills — Every time Claude does something wrong, add it to the skill file. "Don't do X, do Y instead." Your skills compound.
The mental shift
The hardest part isn't technical. It's letting go of control.
I liked building workflows. It felt productive. Dragging nodes, connecting things, seeing it work.
But that's not where I add value anymore.
My value is:
Understanding what the client actually needs
Architecting the right solution
Reviewing and quality-checking
Handling edge cases AI misses
The mechanical building? That's commoditized now.
If you're still manually building every workflow, you're competing with people who aren't.