Make is what the automation category looks like when it stops apologising for complexity: processes drawn as maps, logic visible, data reshaped mid-flow without ceremony. Firms meet it on the day a workflow outgrows a linear trigger-action shape, and many never leave.
The canvas is the argument
A Make scenario is a diagram that runs: modules connected on a canvas, branches where decisions happen, iterators where lists get walked, error routes drawn rather than implied. For anyone who has tried to audit a complex workflow as a list of steps, the difference is immediate: the map is the documentation, and handing a process to a colleague means showing them a picture. Real transformations, dates, text, arrays, arrive without leaving the flow, which is where linear editors start improvising.
Choose Make when:
- Workflows carry real branching, loops or data reshaping
- Volume is high enough that operation pricing beats task pricing
- Someone will read these flows in a year, and the canvas is the documentation
- EU processing options simplify your data paperwork
The economics
Operation-based pricing counts module executions, and at meaningful volume it is routinely the cheaper platform for the same work, one reason the advice-firm comparison sends volume-heavy processes here. The countervailing cost is time-to-first-workflow: budget a real learning day, or buy the build and keep the running. EU processing options sit more comfortably in a DPIA than the category default, worth noting for client-data flows.
Where it fits in a stack
The natural home for the middle tier: workflows too logical for the simplest tools, not custom enough to justify software proper. It pairs happily with Zapier kept for long-tail connectors, and with n8n where self-hosting or code-level control matters more than the canvas.
Where I fit in
Platform choice is the smallest half of the decision; the build discipline is the rest: scoped workflows, error paths handled, credentials kept properly, documentation your team can run. That is what a Kick-starter delivers on whichever platform fits, and an Automation Audit tells you which that is against your actual stack rather than a feature grid.