How to build in n8n without feeling stuck

Here's what I've noticed after my calls teaching people n8n. The main thing that keeps coming up is, how should I build?

Well, let's say you want to build an automation that takes in a receipt, parses the data and posts it to Google Sheets.

Instead of looking at it as this massive project, break it down like this:

Where does the data actually come from? Gmail How do I get the data?

I can use an HTTP node or Gmail node

What do I want to do with the data?

I want to parse the receipt data

Where do I want to save the data?

I want to save it in Google Sheets

Do you see how easy it is once you've broken it down like this? Because now when you go ahead and build, you know what you need to do every single step along the way.

But what about which nodes to use? In 90% of cases I use the same nodes in all my builds:

The main nodes to get data

HTTP Node Webhook Node

Process data nodes

Code Node Set/Edit Node Loop Node

End nodes to push the data somewhere

HTTP Node

This is the way to build without getting stuck. Because you cut all the noise and focus on the most basic pillars of n8n. And nodes like AI agents go under process data nodes, which is why it's in the middle.

11 comments