Updated
I do not automate a process I do not understand
Automation is useful when a process is already understood and somebody is wasting time on the same hand-off again and again. It is a poor first response to a confusing process. If nobody can describe the current steps, automating them usually just hides the confusion behind more technology.
The workflows I use Make for tend to have more than one path. An enquiry may need routing, information may need cleaning before it goes elsewhere or a batch of data may need handling differently depending on what it contains.
Why Make fits that work
Make lets me see the filters, branches and steps in a scenario. That matters when the workflow needs to be reviewed later. A visual map makes it easier to ask what triggers it, what happens when a condition is not met and where a person still needs to step in.
I use it for multi-branch enquiry routing, bulk data work and integrations where the flow has enough detail that it needs to be understood, not simply switched on.
The bit that needs managing
The flexibility comes with a learning curve. A scenario can become fragile if it is built quickly and never documented. I would not leave one running without a named person who understands why it exists and what to check if it stops.
For a single trigger and action, a simpler tool may be the right answer. Complexity has to earn its place by removing a meaningful amount of repeat work or risk.