If you have compared automation tools for more than five minutes, you have met Make. It used to be called Integromat, and it is best known for one thing: a visual builder that looks like a real diagram, with little circles connected by lines that show your data moving from one app to the next. For a lot of people, that picture is the moment automation finally clicks.
This guide is the honest version. What Make is, what it does better than almost anyone, what it costs, and where it starts to pinch for a growing small business.
What Make actually is
Make is a workflow automation tool, in the same family as Zapier and n8n. You build a scenario: a trigger that starts it, then modules (the steps) that do the work, all laid out on a visual canvas. Read a row, send an email, call an API, filter the junk. It is the same trigger-steps-workflow model I broke down in what is n8n, just with Make's own names on it.
What Make is genuinely great at
Make earns its fans, and not just on looks. Where it really shines:
- Visual flow control. Routers split one input down several paths, iterators loop over a list, and aggregators bundle the results back together, all drawn on the canvas instead of buried in settings. For branching logic without code, nothing else is this clear.
- Built-in error handling. This is the underrated one. You can attach error handlers to a module and choose what happens when a step fails: retry, skip, roll back, or stop cleanly. A failed run does not silently lose your data, which matters the moment a real business process depends on it.
- Data stores. Make has a small built-in database, so a scenario can remember things between runs: a list of processed orders, a counter, a lookup table. That kind of memory usually means bolting on a spreadsheet elsewhere.
- 3,000+ apps plus a generic HTTP module for anything with an API, and it is usually cheaper than Zapier on multi-step work because its billing unit stretches further per step.
What Make costs
Make bills with credits (the term that replaced "operations"). For non-AI apps, one operation is one credit, and most steps in a scenario use one credit each time they run. Paid plans start around $9/month, with a free tier to start on.
The thing to watch is how credits add up. A scenario with several modules spends a credit per module, per run. At low volume this is comfortable and cheap. As volume climbs, or as scenarios get longer, the credit count grows with every step you add. It is predictable, but it does scale with complexity. I put real numbers next to Zapier and n8n in Zapier vs Make vs n8n pricing.
Where Make can pinch
A few honest caveats. First, the learning curve is a little steeper than Zapier. The same power that makes the canvas great also means there is more to understand before your first scenario runs. Second, because credits are spent per module per run, a heavy, many-step automation running thousands of times a month can get more expensive than you expected, and you cannot host it yourself to escape the meter.
Third, watch your scheduled triggers. A scenario that polls for new data runs on a timer whether or not anything is waiting, so one set to check every 15 minutes wakes up around 2,880 times a month. Exactly how those empty checks are billed has shifted as Make moved from operations to credits, so confirm the current rules for your plan in Make's docs. Either way the safe habit is the same: use instant (webhook) triggers where the app supports them, and do not poll more often than you actually need.
None of these is a dealbreaker. They are just the trade-offs to know before you commit a core business process to it.
What you can automate with Make
Theory is dull, so here is what Make actually does for a small team. Each of these is a real scenario you can build:
- Catch and follow up on new leads before they go cold, pulling them from forms, email, and chat into one place. See small business automation in the Philippines.
- Route one input down several paths at once, which is where Make's visual canvas earns its keep: send a new order to your CRM, your accounting sheet, and a Slack channel in a single scenario.
- Turn a free Google Form into a real intake pipeline, so submissions are logged, tagged, and acted on automatically. See the free Google Forms automation, no Zapier needed.
- Replace manual copy-paste between the tools you already pay for, so nobody moves data by hand all day.
None of these need a developer on staff. They need a clear process and a tool that can run it. Before you commit, it is worth knowing what the same workflow would cost on each platform, which I broke down in how much it costs to automate lead follow-up.
Is Make right for your business?
For a lot of small businesses, yes. Make is an excellent fit when your automations have real branching logic, when you want to actually see the workflow as a diagram, and when you are price-sensitive on multi-step scenarios where Zapier would charge more. If you like the visual approach and your volume is moderate, Make is a genuinely good home.
It is the wrong fit when the deciding factor is ownership or heavy volume. Make is a hosted service only, so you cannot run it on your own server to keep data fully in-house or to remove the usage meter. If a workflow needs to run a very large number of times a month, or a client needs the data to stay private, that is the point where I usually move people to n8n: same visual idea, but it prices by full workflow runs and can be self-hosted. There is also one thing no hosted SaaS can match yet, which I cover in the pricing comparison: with n8n you can hand the building itself to an AI assistant that works directly inside your own instance.
Where to learn Make
Make has the best learning resource of the three big tools, and it is their own: Make Academy. It is free, self-paced, runs from Foundation to Advanced, and you earn real Credly badges you can put on LinkedIn. Plan on roughly 15 hours for the full path. If you only do one tool's training properly, make it this one, and build the examples in your own account as you go rather than just watching. That is the difference between having seen it and being able to do it.
Where to start
Pick the most annoying repetitive task in your week and describe it in one sentence: when X happens, do Y, then tell me. Build that single scenario on the free plan and let it run for a week. Keep the first one small; a scenario that reliably saves ten minutes a day teaches you more than an ambitious one that breaks on its first edge case. Once it is running, the next handful of tasks become obvious. If you would rather have the first few built properly, with error handling so they do not fail silently, that is what I do.
Sources
Not sure which tool fits?
Tell me the most repetitive task in your week. I can map a simple workflow for it and tell you honestly whether to build it on Make, Zapier, or n8n, and what it will cost to run.
Get the map