The problem I needed to solve
When information is moved between systems by hand, the response slows down and the process depends on somebody remembering the hand-off. I wanted those steps to be visible and repeatable.
Why I chose this tool
The visual scenario builder shows the branches and conditions. I chose it when a workflow had more than one path and needed to be understood by the person maintaining it later.
How I use it
I use Make for multi-branch enquiry routing, bulk data work and workflows where a one-step connection does not give me enough control.
What it does well
- Makes branches, filters and hand-offs visible.
- Gives control when an automation needs real logic.
- Can make higher-volume automation more economical than simpler tools.
What frustrates me
- It asks more of the person building it than a basic connector.
- A poorly documented scenario can become fragile quickly.
- It should support a process, not conceal an unclear one.
Who I think it suits
Businesses with repeatable, conditional workflows and someone prepared to own the automation properly.
Who should probably avoid it
A team that needs a simple one-step integration or has no appetite to understand the flow.
Alternatives worth considering
Zapier.
Pricing context
Assess automation costs against the volume and complexity of work removed. Check current allowances and pricing with the supplier.
My current verdict
A strong option when automation has branches and meaningful volume. Its power is why it needs clear ownership.
