Normalise the pricing before you compare anything
This category prices in four incompatible units: Zapier charges per task, Make per operation, n8n per workflow execution, Pipedream per credit. A single automation that reads a form, checks a CRM, branches and sends an email is one execution in n8n, four operations in Make and up to four tasks in Zapier. Take one real workflow, count how each vendor would bill it, multiply by your monthly volume, and compare those numbers. Sticker prices are close to meaningless here.
Check app coverage before falling in love with a builder
Make and n8n are better builders than Zapier. It does not matter if the app you need is missing. Before choosing, list every system your automation must touch — including the obscure internal one — and confirm each has a real integration rather than a generic HTTP request you will have to build and maintain. This single check reverses more decisions than any feature comparison.
Error handling is what you will actually live with
Every tool builds a happy path easily. The difference appears at 3am when an API returns a 500 and one platform retries with backoff and alerts you, while another silently drops the record. Ask specifically about retries, error branches, run history retention and whether a failed step can be replayed. Teams that skip this discover the answer during an incident.
Self-hosting changes the economics above a certain volume
Cloud automation priced per operation gets expensive at scale in a way that surprises people. n8n's self-hosted community edition removes per-execution cost entirely in exchange for running it yourself. Somewhere between one and five million operations a month, that trade usually starts paying — earlier if you already run Kubernetes, later if you have no platform team.