Make, n8n, or custom code: picking an automation backbone
Choose the workflow before you choose the tool. The platform should serve the process, not the other way around.
Automation projects go sideways when the tool is picked first. Map the workflow on paper — triggers, steps, the points where a human decides something — and the right backbone usually picks itself.
Make is excellent for visual, app-to-app flows: when something happens in one SaaS tool, do something in another. It’s fast to build and easy to read months later.
n8n is our default for anything we want to own. It’s self-hostable, handles real logic and branching, and doesn’t bill per operation — which matters once a workflow runs thousands of times a day.
Custom code is for the core: the step that is genuinely your business, where reliability and edge cases matter more than convenience. You don’t want that living inside someone else’s drag-and-drop canvas.
Most real systems are a mix. A visual tool for the glue, a self-hosted engine for the volume, and a small amount of code for the part that actually has to be right.