Some tools click the moment you see them. n8n was one of those for me.

In my last post, I mentioned that I attended two workshops in one week, and immediately knew I could build the job monitoring system I’d been wanting for months.

I’ve been doing systems engineering since the early 90s. Started with Perl. Spent decades thinking about how data moves: inputs, transformations, outputs. Pipelines. Error handling. Edge cases. What happens when something fails at 3am and nobody’s watching.

n8n’s visual workflow model maps directly to that mental model. Each node is a function, with inputs and an output. Each connection is a data flow. The whole canvas is a system diagram that actually runs.

If you’ve ever architected integrations, designed ETL pipelines, or spent time thinking about how systems talk to each other, n8n will feel familiar. Not easy, necessarily. But familiar.

That’s the thing about tools: complexity isn’t the biggest barrier. Unfamiliarity is. When the mental model matches, you skip the part where you’re fighting the tool and go straight to fighting the problem.

I knew what I wanted to build. I knew the shape of the solution. What I didn’t know yet was how messy the actual building would be. Because here’s the truth: pattern recognition gets you started. It doesn’t get you finished.

Next up: the iteration grind — what "building with AI" actually looks like when nothing works the first time.