Zapier, Make, n8n or custom code: choosing the connector

When a business decides to connect its website, its CRM, and its other systems, the first technical question is usually which tool to use. Zapier, Make, n8n, and custom code can all move data between applications, and each can be the correct choice. The right one depends less on features than on the shape of the work, the cost model, and who will maintain it.

We use four questions to decide. They apply equally to a single workflow and to an entire stack.

Question one: how is it measured, and what does your workflow look like?

The platforms charge in different units, and the same workflow can cost very different amounts on each. The following reflects the vendors' pages as of October 2026, and prices change.

• Zapier counts tasks. Its pricing page states that "tasks are used when a Zap successfully moves data or completes an action." Triggers do not count, failed actions do not count, and built-in tools such as filters and formatters do not count. Its Free plan includes 100 tasks per month, and the Professional plan starts at $19.99 per month.
• Make counts credits. Each action a scenario performs consumes credits; most actions consume one, and a scenario can use anywhere from two credits to thousands in a single run. Its Free plan includes 1,000 credits per month, and the Core plan starts at $12 per month with 10,000 credits.
• n8n counts executions. Its pricing page defines an execution as "a single run of your entire workflow," regardless of how many steps it contains or how much data it processes. Its cloud Starter plan is listed at $20 per month, billed annually, with 2,500 executions.

A long workflow that runs rarely and a short workflow that runs constantly will favor different platforms. Estimate both the number of runs and the number of steps before choosing.

Question two: who will maintain it?

A workflow that a business user can open, understand, and adjust is an asset. One that only its author can read is a liability. Zapier and Make are designed for builders without programming backgrounds. n8n offers visual building with more flexibility for those comfortable with technical detail. Custom code offers the most control and requires a developer to change it.

Be realistic about who will be available in a year. The best technical choice is not always the best choice for the people who will own it.

Question three: what happens when it fails?

Every integration eventually fails, because a field changes, a service is unavailable, or a credential expires. The questions to ask are whether the failure is detected, who is notified, whether the data is retried, and whether the original submission can be recovered.

Webflow's webhooks illustrate what good design looks like at the source. Requests are signed, and a request older than five minutes may indicate a replay attack. Webflow retries failed deliveries up to three more times at ten-minute intervals before it considers them failed. A workflow that receives these requests should confirm the signature, respond correctly, and alert someone when a delivery is ultimately lost. When that level of control is required, custom code is often the right choice, since it lets you specify each behavior.

Question four: where does the data go, and who is allowed to run it?

Each option places customer data in a different environment. Hosted platforms process data on the vendor's infrastructure, and a business should review the vendor's terms before sending personal information through them. n8n also offers a self-hosted Community Edition, which allows a business to run the software itself.

A note on licensing. n8n's Sustainable Use License permits use "only for your own internal business purposes or for non-commercial or personal use," and permits distribution only free of charge for non-commercial purposes. A business automating its own processes is within that description. Still, a business that intends to build a commercial service on top of it should read the license and obtain advice.

Putting the answers together

• Few steps, modest volume, a business owner can maintain it: Zapier or Make is usually the quickest route.
• Many steps per run, or a need to self-host: n8n deserves consideration, with the licensing point above in mind.
• High consequence, strict validation, or unusual logic: custom code, with proper monitoring, is the safer approach.
• A mix: many businesses use an automation platform for routine tasks and custom code for the one or two flows that matter most.

Webflow itself points in this direction. When it retired Webflow Logic on June 27, 2025, it recommended moving to third-party tools, naming Zapier and Make.

The short version

Choose by how the platform measures usage, who will maintain the workflow, how failure is handled, and where the data may go. No platform is best in the abstract. If you would like our team to recommend an approach for a specific workflow, reach out to us — we will transparently assess the options before any commitment.