u/Mobile_Horror8760

Quick share for anyone still on the fence.

Before this, my workflow was the usual dance. I’d go on claude.ai, describe what I wanted to build, copy the JSON, paste it into n8n, watch it fail, go back to Claude to debug, paste the error, get a fix, try again. It worked but it was slow and I was the bottleneck.
Then I installed n8n-MCP (the one from czlonkowski on GitHub, pretty well known in the community now) and plugged it into Claude Code. Honestly it changed how I work.

Now I just write a clear prompt. Claude reads the MCP, picks the right nodes, builds the workflow, deploys it, checks if it ran, sees where it failed, fixes itself and iterates until the thing actually works. I just sit there, test the output, tell it what to tweak, what I prefer, and move on. I’m basically a reviewer now. A guy who checks if it works and gives directions.

Productivity is roughly 5x for me. Workflows I would have given up on a few months ago I now ship in an afternoon. Stuff with weird branching, custom code nodes, error handling, all of it.

That said, there’s a thing that bugs me a bit. I miss the craft. Before, I was building these workflows by hand, breaking them, fixing them, and there was a real satisfaction when it finally clicked. Now it’s faster and more reliable but that feeling is mostly gone. And honestly I’m a little scared of losing my hands-on skills. I still keep the logic in my head, I still know why a workflow is structured a certain way, but the muscle memory of actually building it node by node, that’s fading.

Now here’s the thing I really want to say, especially to people just getting into automation.

I’m genuinely glad I learned n8n the hard way. Manually, iterating, failing, rebuilding, getting actual results at the end. Because that’s what makes the AI agent useful in the first place. If you already did the craft, if you already wrote workflows by hand, broke them, tested them, fixed them, then when you switch to Claude Code or any coding agent your productivity goes through the roof and you make way fewer mistakes than someone who never built anything themselves. You can actually dictate what you want because you know what’s possible.

Think about someone who spent three hours on n8n and jumps straight into an agent. What are they going to tell it? Nothing useful. They don’t know the field of possibilities. They don’t know what n8n can or can’t do, so they can’t ask for the right thing.
Same logic for code. If you want to vibe code, fine, but at least master one programming language first. Do it the hard way. Build stuff manually. Break it. Get frustrated. Because in the end you’ll have a real mental map of what’s possible, you’ll spot bugs faster, and you’ll get way more out of the agent.
The combo is craft first, agent second. Not the other way around.

Curious if anyone else feels the same tension between speed and craft. And if you’re using n8n-MCP too, drop your setup, always interested in how other people prompt this thing.