One Open-Source Repo Turned Claude Code Into an n8n Architect — And n8n Has Never Been More Useful

Last Tuesday at 11 PM I watched Claude Code erase 140 product variants from a production e-commerce store.Not maliciously. Not even incorrectly, technically. The workflow I'd asked it to fix was se...

By · · 1 min read
One Open-Source Repo Turned Claude Code Into an n8n Architect — And n8n Has Never Been More Useful

Source: DEV Community

Last Tuesday at 11 PM I watched Claude Code erase 140 product variants from a production e-commerce store.Not maliciously. Not even incorrectly, technically. The workflow I'd asked it to fix was sending a PUT request to PrestaShop's XML API with only 4 fields. PrestaShop interpreted that as "set everything else to empty." References gone. Barcodes gone. 140 combinations silently wiped while I was comparing execution logs in another terminal tab. TL;DR: n8n isn't dying. Manual workflow building is dying. One open-source repo (czlonkowski/n8n-mcp) turned Claude Code into an n8n architect. I've used it on a real 55-node production pipeline, and separately disabled my own AI agent because it burned tokens for nothing. Below: what actually works, what breaks, and a framework for when to use which tool. When your logo is more reliable than your AI agent. Fifteen minutes later, Claude Code had also diagnosed the root cause, built the fix (a GET-before-PUT pattern across 4 new nodes), deployed