The visual canvas. When you're building an automation that crosses 5–6 apps, being able to see the whole flow at a glance is genuinely useful, it makes debugging much faster and onboarding clients way easier than pasting a wall of code or config. The flexibility is also a good point, you can do things that most no-code tools would force you to work around, custom HTTP requests, data transformation with functions, error handling per module. It's not perfect but it covers 90% of what a typical agency workflow needs. And the pricing model is fair at the start. Compared to Zapier, you get a lot more operations per euro before hitting a wall.

I would say that the best thing about Make is its user-friendliness. I can set up anything I want in a couple of minutes. At the same time, it has a lot of flexibility because of all the app modules. I know that almost any app that I work with, if not all of them actually, I can find in Make, which is super useful. It was pretty intuitive, and there's modules for basically everything. So, it's pretty easy to get going, which was great and super useful.

The interface is inviting and does a good job of guiding the user. The pricing is beginner-friendly and transparent, and the allowed usage feels generous. The number of connections a user can make is broad, which gives you plenty of flexibility. You can also debug scenarios and quickly see what needs to be done and where, and saving a scenario has become much more user-friendly. I love the community sessions that Make provides and get inspired from those. You are able to use varied LLM's and can evaluate which one to use on what task. Scenario folders are great and I should rememeber use those more. Overall Make is straightforward to use and outcome is almost always exceeding expectations.