What I learned from building N8N workflows with Claude Code.

Recently, I moved from building N8N workflows manually to using Claude Code to build the workflows. Here are five lessons I've learned from building in N8N workflows with Claude Code.

Lesson 1. Be Specific. Be specific with your goal and your desired outcome. A good way to make sure Claude knows specifically what you want to achieve is to write up a technical document or project report containing some brief detailed information about what your building, who you're building it for, the problem you're trying to solve, along with other project specifications you think might be important. The document you feed Claude doesn't have to be long, nor does it have to contain all the information about the architecture of the workflow, the different nodes you would use, or any other technical information that a builder would normally need to know. Treat Claude like a developer. Just give Claude a brief report telling it what you want and any specific details you have that you can provide and let Claude do the thinking and designing.

Lesson 2. Don't just jump in to building the workflow with. Put Claude in planning mode and make sure Claude asks you specific questions about what you are trying to achieve. I've noticed that sometimes Claude will think of things that I didn't think of. Get Claude to ask you questions about your project so it knows more about what it needs to do to create the most satisfactory outcome.

Lesson 3. If your project is a complex project that requires multiple workflows, ask Claude to spin up some agents that can work in parallel and build multiple workflows at once. The workflows won't be production-ready immediately. They will need to be tested, and you'll have to test each of them one by one. Having Claude's spin-up agents that work in parallel will save you time. Just make sure that Claude has a solid understanding of your project before asking Claude to spin up multiple agents to build each of the workflows.

Lesson 4. Create backups and periodically save your progress. Use GitHub and JSON files to save your progress and back up your workflows and projects. By creating a GitHub repository, you can download your projects and the workflows from GitHub to your laptop when you're not using your desktop. Once you're done working on your project on your laptop, you can ask Claude to push the changes to GitHub and then download the changes from GitHub to your desktop and proceed from there. GitHub is a free cloud service you can use to save your project.

I've been using Claude, coupled with the N8N MCP server. I always ask Claude to make .json file copies of the workflow it builds AND ask Claude to periodically update these .json files as I continue to develop the workflow with Claude. The .json files can be stored locally on my computer. Claude will build the workflows in the N8N Cloud instance directly using the MCP server. The best practice is to have .json files of those workflows backed up on your computer. Make sure Claude changes the .json files to match the workflows in the N8N Cloud instance. The .json files on your computer can be stored in a Claude project that can be uploaded to GitHub and downloaded to any desktop and laptop you use.

If you ask Claude to remember to periodically update the N8N .json files as it works in the cloud instance, it will. It will save that information to its memory. Every time you use Claude to build an N8N workflow, Claude will remember to update the .json file to match the workflow in the N8N cloud instance.

Lesson 5. Ask Claude to battle test your workflows to make sure they're production ready. Prompt Claude to think of any edge cases or problems that might arise and then have Claude test and independently verify that the workflow is production ready. Claude will find errors that will prevent your workflow from being production-ready and any potential problems that will break your workflow. After 15 minutes of back-and-forth with Claude, your workflow can be production-ready. You will have to do some of the work but Claude will help you and assist every step of the way. Getting Claude to test and verify that your workflow is production-ready will save you headaches in the long run.

Out of all the lessons, asking Claude to battle test my workflows is one of the most important lessons if not the most important lesson.

12 comments