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 am on the webinar now and Liam's feed just cut out. I cannot see his slides nor can I hear what he is saying. Will there be another webinar? I have other priorities I need to take care of. Please let me know if the webinar has been postponed again.

This is a community public service announcement. If you are interested in Vibe Coding, I found a free Vibe Coding Hackathon Community on Skool. The hackathon prize is $6k. No coding experience required. The AI Hackathon is Mar 6th-8th. Here's the link for the free Community: https://www.skool.com/hackathon/about

I woke up this morning, checked the messages and information on my phone, and discovered that a business owner contacted me wanting to know if I still had any more openings for AI audits and consulting. I have the appointment down and I am excited to meet with the business owner. I like doing the build work but I am also trying to do consulting because I want to be able to do both consulting and build work. If anyone has any tips they would like to give me about consulting work, please leave it in the comments below.

This workflow is built for those who struggle with the problems of paper receipts(including my mom). The problem: Receipts collect in pockets, wallets, envelopes, and drawers. You have to find the receipts. None of the receipts are stored digitally in a centralized database. The ink on the paper receipts fades and manually typing in the information into a spreadsheet takes time and is painfully boring. You spend hours tracking down your financial records and typing in information when you could be doing more meaningful work. The solution: Scan receipt using the Google Drive app on your phone and this n8n workflow handles the rest. The Teck stack: Google Drive storage Mistral Vision Read receipt n8n Orchestration Google Sheets as a database If you are using n8n you spend one less than 1 cent per receipt with this workflow. Please comment and share your thoughts. If this workflow is something that interests you, feel free to comment. If you would like help building something like this, let me know.