Unlike most people, I tried n8n before trying Make. Trying Make after n8n was super confusing and disappointing as I tried various things that seemed common sense and didn't work. Building a workflow in n8n feels like ultimate freedom and there are so many different ways to do the same thing. Plus, the drag and drop canvas with arrows that you can connect or disconnect at will is so intuitive. With Make, I felt like I needed to find that one workaround to accomplish what I wanted. Building with routers and iterators wasn't at all intuitive, and I found myself just wanting to run some Javascript rather than find the "no-code" way to do it. I think one thing n8n could make easier is paginating through an API as a loop-there is some complexity in how IF nodes limit what data can be accessed further down the line, and it's not always clear when one should use SplitInBatches vs. another approach to looping. It usually takes me an hour or two of fiddling to finish a workflow if it includes paginating through an API as a result, even though I've done it dozens of times now. That said, I never tried to paginate through an API in Make and I bet it would be even harder 🤣 Lastly, the cost is not even close. Whether you use n8n cloud or self-host, you'll be paying so very little to automate some crazy stuff. I'm running dozens of automations on a $5/mo DigitalOcean droplet.
Odd interview tbh. Make has a way to create custom apps as well. You can create custom IML functions in make using the app sdk. I wonder if you’ve explored that feature before deciding to move.
![Build AI Telegram Chatbot with beautiful image generation using low-code tool n8n 🚀 [Part 1 and 2]](http://i.ytimg.com/vi/etIqVOcqEWI/mqdefault.jpg)
![Build AI Telegram Chatbot with beautiful image generation using low-code tool n8n 🚀 [Part 1 and 2]](/img/tr.png)
![AI Sprint Wrap Up + What's Next [Update #11]](http://i.ytimg.com/vi/iLRS79EWsos/mqdefault.jpg)
Unlike most people, I tried n8n before trying Make. Trying Make after n8n was super confusing and disappointing as I tried various things that seemed common sense and didn't work. Building a workflow in n8n feels like ultimate freedom and there are so many different ways to do the same thing. Plus, the drag and drop canvas with arrows that you can connect or disconnect at will is so intuitive. With Make, I felt like I needed to find that one workaround to accomplish what I wanted. Building with routers and iterators wasn't at all intuitive, and I found myself just wanting to run some Javascript rather than find the "no-code" way to do it.
I think one thing n8n could make easier is paginating through an API as a loop-there is some complexity in how IF nodes limit what data can be accessed further down the line, and it's not always clear when one should use SplitInBatches vs. another approach to looping. It usually takes me an hour or two of fiddling to finish a workflow if it includes paginating through an API as a result, even though I've done it dozens of times now.
That said, I never tried to paginate through an API in Make and I bet it would be even harder 🤣
Lastly, the cost is not even close. Whether you use n8n cloud or self-host, you'll be paying so very little to automate some crazy stuff. I'm running dozens of automations on a $5/mo DigitalOcean droplet.
Wow! You hit the nail on the head! I'm in the middle of doing this too!
Odd interview tbh. Make has a way to create custom apps as well. You can create custom IML functions in make using the app sdk.
I wonder if you’ve explored that feature before deciding to move.
🌈 "PromoSM"!