The Make.com Modules I Actually Use Every Week (And The Ones I Killed)
The article discusses the author's experience with Make.com and the modules he finds essential for his weekly tasks. After auditing his setup, he identified which modules were beneficial and which were unnecessary complexities. He emphasizes the importance of simplicity and functionality in his automation processes.
- ▪The author uses Make.com for various projects, including client work and personal experiments.
- ▪He conducted a thorough audit of his Make scenarios to determine which modules were truly useful.
- ▪Modules that automate recurring tasks, provide actionable information quickly, and are easy to debug were prioritized.
Opening excerpt (first ~120 words) tap to expand
try { if(localStorage) { let currentUser = localStorage.getItem('current_user'); if (currentUser) { currentUser = JSON.parse(currentUser); if (currentUser.id === 3798270) { document.getElementById('article-show-container').classList.add('current-user-is-article-author'); } } } } catch (e) { console.error(e); } Richard Lemon Posted on May 23 • Originally published at richardlemon.com The Make.com Modules I Actually Use Every Week (And The Ones I Killed) #nocode #automation #tooling #productivity 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.
…
Excerpt limited to ~120 words for fair-use compliance. The full article is at DEV.to (Top).
Discussion
0 commentsMore from DEV.to (Top)
