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 just finished building 3 automation templates that are absolute game-changers if you're trying to start an automation agency. A sales agent, proposal generation agent, and client onboarding agent. These are the exact workflows agencies charge thousands to set up, and I'm giving them to you for free. But here's the catch: I'm not just handing you the templates and walking away. I'm running a free challenge where we'll walk you through building each one step-by-step so you actually understand how they work. By the end, you'll have 3 polished automations you can use to run your own agency or show to potential clients. Click here to get all the details on the challenge See you inside. Cheers, Nate

Here’s how it works: Over two weeks, we'll work together to build your first AI agents. No fluff. No theory. Just hands-on building with me and the AI Automation Society team. By the end, you'll have working AI agents in your portfolio and the confidence that comes from actually doing it. You also have the foundation you need to begin charging businesses for developing custom AI agents. And the best part? The whole class is FREE (with a small catch). If you're ready to stop sitting on the sidelines, click below to grab your spot. ANNOUNCING: An automation accelerator for beginners (it's free) Talk soon, Nate PS: Some of my students are making $10,000 + from creating automations like these. If you want to start your own AI automation agency one day, this is the perfect first step.