n8n vs Zapier: which would I use for lead routing?
Compare n8n and Zapier around one website enquiry. Try the failure lab, work out tasks versus executions and download the test pack.
For a straightforward managed workflow that a business team can look after, I'd start with Zapier. If I needed more involved data processing, custom API logic or control over hosting, I'd look at n8n. That choice comes with extra complexity, though, and someone needs to own it.
The comparison makes more sense once you follow an enquiry all the way through. It needs to reach the right CRM record, the right owner and a useful next step. What happens if someone submits twice, a connection expires or the notification fails after the CRM has saved the lead?
I'm using a fictional form-to-CRM-to-notification workflow here, with a browser simulation and a downloadable test pack. The simulation shows how recovery can work; it doesn't run either platform. Product facts were checked against official documentation on 10 October 2026.
n8n or Zapier? Start with the person maintaining it
| Decision | Zapier starting point | n8n starting point |
|---|---|---|
| Workflow ownership | A business operator can manage a familiar integration, with clear escalation when it breaks. | A technical owner can review transformations, APIs, execution state and recovery logic. |
| Hosting | Managed service; assess the vendor’s available controls against your needs. | Choose Cloud or investigate self-hosting. Hosting yourself adds operating responsibilities. |
| Custom logic | Check that the exact connector actions and supported code steps cover the workflow. | Investigate nodes, API requests and code when the process needs detailed transformations or branching. |
| Usage planning | Model the billable actions, special task rates and replay behaviour. | Model production workflow starts, including schedules and additional recovery workflows. |
| Failures | Define error handling and inspect how replay affects already completed actions. | Define retry behaviour, error workflows and how successful writes are reconciled. |
| Handover | Prove the intended operator can find a failed run and recover it. | Prove the owner can operate the workflow and, if applicable, the instance hosting it. |
Both tools can handle complex work, so the dividing line isn't simply whether your team is technical. A technical team can choose Zapier, and a business team can use n8n with the right support. What matters to me is who'll understand the system when a lead doesn't arrive. Ownership, duplicate handling and recovery need testing before more branches go in.
You don't have to self-host n8n; there's a Cloud option too. If you do run your own instance, its hosting documentation explains the technical knowledge involved. Infrastructure, upgrades, backups, access and monitoring all become work to look after. Cloud may fit better if the team can't take that on.
Agree the workflow before choosing the connector
The example input has a stable submission ID, timestamp, name, work email, company, postcode and enquiry type. The output is an accepted lead, an assigned owner and a notification, with delivery state recorded so failed work can be recovered. The CRM holds the lead record. The submission store tracks delivery progress.
Seeing a green workflow doesn't tell you whether the enquiry reached anyone. An API request might succeed but create a record with no owner. Checking who received the lead and what response is expected tells you more than the HTTP status alone.
The lead-routing lab
A deterministic browser simulation of a fictional form → CRM → notification flow. It does not connect to n8n, Zapier or a real CRM, and is not a platform benchmark.
Simulation result
Delivered
- Receive sample submission lead-1042.
- Validate the required fields and choose the sales route.
- Create or update the CRM record with operation key lead-1042.
- The CRM write committed, but the response was lost.
- Look up the operation key; confirm the existing write and resume.
- Send the notification and record the delivery state.
Counts are for this fixture, including duplicate deliveries. They are not billed tasks or platform execution counts.
A timeout does not prove that the write failed. Use a stable operation key and reconcile before creating again.

Eight cases worth testing in either platform
1. A normal enquiry
Before testing faults, send one known input and check every destination: fields, owner, record ID and message. That gives you a baseline to come back to. Seeing the trigger fire only proves the first step.
2. Duplicate delivery
Sometimes the browser submits twice; sometimes the sender delivers the same event again. A stable submission ID lets you track which side effects have completed. Matching contacts by email is a separate job, because the same person might send a second, valid enquiry.
In production, a read-then-write duplicate check can race if two deliveries arrive together. Use the destination's supported idempotency controls or an atomic unique key/lock in a durable store. Test simultaneous deliveries. The browser lab shows the intended result; it doesn't implement production locking.
3. A timeout after the CRM has saved the record
After a timeout, you're left with a question: did the CRM save the record before the connection failed? If you repeat a create request without checking, you may make a duplicate. Check the operation key or known record ID first, then repeat only the work you can show is incomplete.
4. A temporary rate limit
A rate limit may allow a retry. Follow the service's guidance, limit attempts and elapsed time, and keep the original payload. If you reach those limits, alert the owner and give them a controlled way to recover the delivery.
5. Expired credentials
If authentication has failed, someone needs to fix access before the workflow can continue. Retrying indefinitely won't help. The connection owner needs to know which system failed, where the saved submissions are and how to replay them once access works again.
6. A failed notification after the CRM write
If the CRM write succeeded, keep it and recover the message separately. Someone may still replay the whole run, so the workflow needs to avoid repeating writes or notifications that have already completed.
7. No matching owner
You'll get requests that don't fit the routing rules. Give those a fallback queue, name who looks after it and agree when to escalate. Otherwise, the lead can be saved correctly and still go unseen.
8. Missing or invalid fields
Send an invalid enquiry for review with its original context. Repeating the same failed validation won't help. Decide which fields routing needs and which the team can collect later.
How I'd build this in each tool
In Zapier
In Zapier, I'd choose the trigger for the way the form sends data, then map and validate the fields before the CRM action and notification. The connector needs checking carefully here. Does it support the exact search, update and ownership behaviour you need? A CRM being in the directory doesn't mean every endpoint is available.
Plan how to recover a failure and check what a replay repeats. Zapier documents task use for successful error-handler steps and repeated successful steps during a full replay. Test your flow's side effects and task usage in a controlled account.
In n8n
In n8n, the sequence stays the same: trigger, validation, routing, CRM write and notification. Nodes or API requests can handle the destinations. I'd use code where it makes the transformation easier to understand and maintain, and keep delivery state separate from the visual workflow.
n8n's error workflows and node error-handling options give you the building blocks, but you still need to check what a retry means for the receiving API. Reporting an error doesn't tell you how to recover steps that partly succeeded.
There's still work between these outlines and a production integration. Your CRM schema, credentials, data store, permissions and available endpoints decide how it needs to be built. The tests below give you checks to reuse along the way.
Tasks and executions are different units
Before comparing subscription prices, work out what each platform will count. Zapier counts successful actions as tasks, with exceptions and special rates for some steps and products. n8n prices around production workflow executions. Counting nodes won't give you an equivalent task count.
Take 500 completed enquiries, three standard one-task actions per enquiry and ten extra full replays. That simple Zapier model gives 1,530 tasks. For 500 n8n enquiry starts and 20 extra production workflow starts, the model gives 520 executions. These are example assumptions, not actual bills.
Model the units you need
Illustrative standard one-task action model: all enquiries finish successfully; each full replay repeats the same actions. No AI, extended code runtime or special-rate actions are included.
Zapier: (enquiry runs + full replays) × standard billable actions. n8n: enquiry runs + additional production workflow starts you expect.
A recovery step does not automatically start a new workflow. Count schedules, error workflows and separate reruns only when they actually start. Check each platform’s current inclusion, rate and retry rules before choosing a subscription.
Schedules, loops, error paths, special-rate actions and retries can all change those totals. During a pilot, I'd compare the model with the usage logs, then check the current Zapier pricing and n8n pricing for the plan. I've left out fixed prices because currency, billing periods, tiers and what's included can change.
The subscription is only part of what you'll spend. Someone has to build the workflow, monitor it, investigate failures and keep up with API changes. If you're self-hosting, infrastructure belongs in that calculation too. A cheaper plan can still cost more to operate.
Download the workflow test pack
The CSV sets out each input or fault, the CRM and notification results you expect, evidence to collect and the owner. The JSON gives you fictional payloads and fault descriptions, with no credentials or importable workflows. The runbook is there so the operator has steps to follow when delivery fails.
- Create a sandbox record destination and a test notification channel.
- Implement one complete normal enquiry and inspect every output.
- Run the duplicate, timeout and partial-success cases before inviting live traffic.
- Record screenshots or execution links, actual task/execution usage and the recovery steps.
- Ask the future owner to recover a failure using the runbook, then fix anything they cannot follow.
If you can't safely reproduce a fault through an API, use a controlled stub in a test environment and record the limitation. Keep destructive failure tests away from the live sales process.
When I'd consider a custom service
There are cases where I'd look beyond both tools. Durable queues, strict transaction boundaries or product-specific guarantees may be easier to reason about in a small custom service. At low volume, though, a smaller manual handoff may be enough.
The HubSpot and Chili Piper lead-flow article covers the sales journey around this automation. For help building and looking after the handoff, see my AI and automation work.
Sources and when I checked them
Checked on 10 October 2026. Plan limits, billing rules and available actions may change; confirm them during implementation.
- Zapier: how task usage is measured
- Zapier: current pricing and inclusions
- n8n: pricing and production execution units
- n8n: error handling
- n8n: self-hosting responsibilities
Frequently asked questions
Should I choose n8n or Zapier for website lead routing?
It depends on the connector actions, data transformations and who will maintain the workflow. Zapier can fit a managed handoff owned by a business team. When custom API logic or hosting control matters, I'd look at n8n, provided a technical owner can support it.
Is the failure lab a real n8n or Zapier benchmark?
No. It's a browser simulation with fixed delivery and recovery behaviour. It doesn't run either platform or measure their speed, reliability or actual bills. Use the fixtures to test your own sandbox integration.
How do I prevent duplicate leads when an automation is retried?
Keep a stable submission or operation ID and a durable record of completed side effects. Use supported idempotency controls or an atomic unique key. Check ambiguous timeouts before creating another CRM record. Test simultaneous deliveries as well as retries that happen one after another.
Are Zapier tasks equivalent to n8n executions?
No. The planner models successful billable actions for Zapier and production workflow starts for n8n. Special rates, schedules, error paths and replays can change usage. Check your workflow against current plan rules and usage logs.
Is n8n always cheaper?
No. The units, plan and workload differ, and someone's time looking after it counts too. Model a representative month, including failures and replays. Use actual plan prices rather than multiplying the number of nodes by a headline rate.
Do I need to self-host n8n?
No. There's a Cloud option. Choose self-hosting when you need its control and the team can look after the instance. Include infrastructure, upgrades, access, backups and monitoring in that decision.

.jpg)
