What's your take on Make/Zapier/N8N vs Code?
Hey guys,
I’ve been seeing a trend lately.
More and more people are moving away from tools like Make, Zapier, and N8N and switching to code.
But I wouldn't do that so fast... And it's because of two reasons:
  1. My clients aren't technical, and they never will be.
If their business grows, they hire developers.
But if things slow down, those developers are gone.
And when it slows done, they’re stuck.
Their entire system depends on code they don’t understand and cannot change.
So I actually think not using code is in the best interest of my client.
And I rather build something they could manage (if they invest the time to learn) if shit hits the fan.
(This also builds trust with clients btw, so they know you think in their best interest)
2. Make/Zapier/n8n is way faster to fix
When something breaks… Make, Zapier, or N8N is way faster to fix.
You can fix it fast.
With code, it’s different.
You need to dig into the code, make changes, test it, deploy it again.
That takes time.
So for me, it’s simple.
I optimize for:
  • Simplicity
  • Speed
  • Control for the client
Curious what you think 👇
What do you prefer and why?
Make/Zapier/N8N
Code
Hybrid
Other
6 votes
3
5 comments
Joren Wouters
3
What's your take on Make/Zapier/N8N vs Code?
AI Automation Society
skool.com/ai-automation-society
A community built to master no-code AI automations. Join to learn, discuss, and build the systems that will shape the future of work.
Leaderboard (30-day)
Powered by