TL;DR: Zapier is genuinely good for simple connections and genuinely wrong for business logic your revenue depends on. The dividing line is not volume, it is what happens when step four of seven fails at 2am. Build routing on Make or n8n, put a real enrichment layer in front of it, and design the failure path before the happy path.
Most CRM automation stories go the same way. Someone builds it in Zapier over a weekend and it works. Volume doubles. Something breaks quietly. A day disappears into working out why four hundred leads got the wrong email, and nobody can reconstruct the order things ran in.
This is not an anti-Zapier piece. I use it. The failure is not the tool, it is putting business logic somewhere that was designed for connections.
The real dividing line
It is not lead volume and it is not step count. It is this question: when a step fails halfway through, does anything notice, and can you tell what already happened before it stopped?
If the answer is that a person notices eventually, you are fine on a simple connector and should not overbuild. If the answer needs to be that the system notices, retries the recoverable part, and does not redo the part that already succeeded, you are past what a connector is for, whichever brand is on it.
Being fair about Zapier
It has error notifications and it can replay failed runs, so the flat claim that it has no error handling is wrong and you will find it repeated all over the internet. What it does not give you is the thing that matters at scale: branching failure paths, retry with backoff on the one flaky API, and idempotency so a replay does not send the same person a second email. You end up assembling those out of code steps, and at that point you are maintaining code inside a no-code tool, which is the worst of both.
And about cost
Zapier bills per task, meaning per action step that runs, so a seven-step Zap firing a thousand times a month is around 7,000 tasks. As of September 2026 the ladder is Free at 100 tasks, Professional from $19.99/month, Team from $69/month, with the price rising along a usage slider. The old Starter tier that half the comparison articles still quote does not exist. Make starts at $9/month for 10,000 credits. The gap is real but it is the second reason to move, not the first.
What a stack you can trust looks like
Which of those two fits you is its own question, worked through in our three-way comparison. For work the business depends on we build on Make or n8n with a model doing the judgment calls. Here is a lead qualification and routing system, concretely.
The path a lead takes:
A webhook fires when a lead lands in the CRM, and the lead ID is recorded before anything else happens
Enrichment fills in what the form did not capture: industry, company size, intent signals from what they typed
Routing assigns to the right person by territory, segment or account size, using the enriched fields rather than the raw ones
A first-touch reply is generated against your criteria and sent within minutes
No response in five days and a follow-up task appears on the owner's list
The CRM record is updated with the enrichment, the routing decision, and what was sent
The first bullet is the one people skip and the one that matters. Recording the lead ID before any work happens is what makes a retry safe: on a second delivery the system sees the ID, knows what already completed, and does not send a duplicate. Webhooks are delivered at least once, not exactly once, and any system that assumes otherwise will eventually double-email someone you wanted to impress.
When a step fails, it retries with backoff. Errors are logged with enough context to reconstruct the run, and a notification goes to a channel someone actually reads. One of these has been running for a client for eight months without intervention. The uptime is not the interesting part; the interesting part is that nobody has had to ask what happened.
The enrichment layer, which is where routing actually lives or dies
Raw CRM data is incomplete in a specific way: you get a job title and no company size, a company name and no industry. Routing rules written against fields that are empty half the time do not fail loudly, they just route badly, and that looks like a sales problem rather than a data problem for about a quarter.
So enrichment runs before routing, not after: contact and company data from a provider, and a model classifying intent from whatever the person actually wrote in the form. The output is a record with industry, a size estimate, and an intent score. Now routing is reliable, because it is reading fields that are populated.
Two rules we hold to. Enrichment must be allowed to say it does not know, and a record it could not enrich goes to a human rather than down a default branch, because a confident wrong classification is worse than an empty field. And whatever you enrich with has data-protection consequences in the EU and under the Australian Privacy Principles, so decide that deliberately rather than discovering it later.
Reporting, without the Monday ritual
The other thing that breaks in every CRM setup: someone pulls the numbers each Monday, pastes them into a sheet, rebuilds the same chart. Then does it again.
Replace it with a scheduled job. At eight on Monday, pull the pipeline from the CRM API, compute stage conversion, average deal size and movement against last week, have a model write a short summary of what changed, and put it in the channel before anyone sits down. The value is not the saved hour. It is that the number is computed the same way every week, so a change in it means something changed in the business rather than in who built the sheet.
When not to build any of this
If your lead volume is genuinely low and one person reads every enquiry, a connector doing two steps is the correct answer and this article is over-engineering for you. The cost of building a resilient pipeline is only worth paying when the cost of a silent failure is real: a lead lost, a customer emailed twice, a number in a board deck that was wrong for three weeks.
The signal that you have crossed over is usually not volume. It is the first time somebody asks whether the report is right and nobody can answer quickly.
Want to know whether your setup is past that line? The audit at 2pizza.team/audit takes two minutes, no call, and if the honest answer is that your current Zaps are fine, it will say so.
Originally published at 2pizza.team. We build AI and automation systems for small teams - fixed price, two to six weeks. See the work.
Top comments (0)