When you start using n8n for the first time,

how do you build? Most people go straight to one massive workflow with all the nodes. It looks impressive, and I fell into that trap with my first client. But take a guess what happened when we ran the system. It crashed somewhere in the chain. And every time it broke, I had to repair that node and start from scratch.

What I learned is that you need to control the data from flow to flow. Here's how. Say you have leads coming in from HubSpot. To move them between flows, use a status field.

Lead enters Flow 1, gets status "new"
Flow 2 runs only on status "new", updates status to "processed" at the end
Flow 3 picks up the processed lead from Flow 2 and marks it as "done"

This is how you process data through many flows without connecting them. You control movement with different states so leads pass through each flow in order.

What are the benefits? If Flow 3 gets an error, Flows 1 and 2 keep running. You have fewer nodes to fix when something breaks. Fixing an error takes 10 minutes instead of 30.

I've attached an image of my WhatsApp lead gen system I built for a client. It has 8 flows, but you could put every node into one flow and try to make it work. But instead I have a system that runs 24/7 and processes leads as they come in.

One tip. Don't start with 8 flows. Start with 3 and make them work together as one system.

6 comments