I built a support bot last week without opening n8n once.

Described what I needed out loud to Claude Code. It pulled the n8n docs, checked the Asana task where the client described requirements, built the workflow through n8n-mcp.com, and deployed it.

Then I said: test it.

It tested. I left one node disabled so responses wouldn't go live, and let executions accumulate for two days. Then I said: review the executions.

It analyzed hundreds of runs and came back with: "We missed several queries. Someone asked 'where is my invoice' instead of 'where is my order' and we didn't handle that."

I said: update the workflow.

It updated it.

Two years ago I was spending 95% of my time dragging blocks in the n8n UI. Today the ratio is almost inverted. I work in Claude Code, talk to my computer, and barely touch the canvas.

n8n didn't become less important. It stopped being the place where I build automation and became the place where I run it. The building moved to the conversation layer.

Hundreds of workflows built this way so far. Most of them voice-to-deploy.

Curious where other builders draw the line — what's the part of workflow building you still want to do by hand?