The problem with my Make.com setup
I use Make.com a lot. Client work, my own projects, experiments, tracking weird biohacking data, even baseball stuff. It started simple. Then, like every tool I enjoy, it turned into a zoo.
Too many scenarios. Too many modules. Too many runs where I had to ask: “Why did this even fire?”
A few months ago I did a hard audit of all my Make scenarios. Not a theoretical one. I looked at what ran weekly, what broke, what I ignored, and what quietly ate time and operations without giving anything back.
This is the result. The Make modules that actually earn their place in my stack every week. And the ones I stopped using because they were just clever complexity.
This post is for paying subscribers only
Subscribe to continue reading