Automating data flows between tools without Zapier

Zapier and Make have done businesses a real service: connecting a form to a CRM, or an invoice to a spreadsheet, in a few clicks. But over the years, automations pile up, the bill grows with volume, and nobody knows exactly what is running anymore. Here is how to tell whether it is time to move to custom-built connectors, and what that costs.

What Zapier and Make actually do

These tools connect applications using the principle “when this happens, do that.” They are billed by usage:

• Zapier counts “tasks”: each successful action in an automation counts as one task, and triggers do not count. The free plan includes 100 tasks per month; paid plans are listed “starting from” $19.99 per month (Professional) and $69 per month (Team), entry prices with annual billing, and go up with the task volume you choose (Zapier pricing, checked in October 2026).
• Make counts “credits,” with a free plan of 1,000 credits per month and paid plans priced by volume (Make pricing, checked in October 2026).

For a handful of low-volume flows, that is hard to beat: no development, set up in an hour.

Signs it is time to go custom

I recommend considering a custom connector when at least two of these apply:

1. The automation is critical. If it stops, orders are not processed or invoices do not go out.
2. Volume is growing. Each order triggers five or ten actions, so task consumption tracks your revenue.
3. The logic is complex. Nested conditions, loops, edge cases: the scenario becomes unreadable and only its author can change it.
4. Sensitive data is involved. Customer data, pricing, health or HR information passes through one more third-party platform.
5. Failures are silent. An API changes, the automation fails, and nobody notices for a week.

Comparing the three options

An illustrative example, with made-up amounts to replace with your own: if your automations cost €300 a month, or €10,800 over 3 years, two custom connectors at $4,500 (€4,000)excl. VAT plus €1,000 a year in maintenance come to €7,000 over the same period. At €50 a month, on the other hand, custom work does not pay for itself on cost alone: you need another reason, such as reliability or security.

What a custom connector includes

A serious connector is not just “send A to B.” I plan for:

• error recovery: if the destination tool does not respond, the exchange is retried, then flagged;
• a log of every exchange, searchable, so you know what went through and when;
• an alert sent to the right person when something is stuck;
• minimal access to the connected tools;
• documentation of what each flow does, so another provider could take over.

The connector can live inside a business app that also serves as a monitoring screen, or run on its own on lightweight hosting. The options are covered in extending existing software without replacing it.

What it costs

In the estimator, the “connection to other tools” module is priced at $2,300 (€2,000)excl. VAT. It covers a standard connection between your app and a tool with a documented API.

The amount goes up when:

• the tool to connect has no proper API, or a limited one;
• flows run both ways, with conflict handling;
• several tools are chained in the same process.

For an existing set of automations, I start with an inventory during an audit (express audit at $660 (€589)excl. VAT): which flows, what volume, what risks, and which ones are worth replacing.

When to keep Zapier or Make

To be clear: for many uses, these tools remain the right choice.

• Convenience automations that are not critical: a chat notification, a copy into a spreadsheet.
• Low volume, a few hundred actions a month.
• Temporary needs, or testing a process before making it permanent.
• Self-sufficient teams that change their scenarios often without a provider.

The right model is often a mix: critical flows as custom connectors, everything else on an automation platform.

Where to start

1. Export the list of your active automations, with their monthly usage.
2. Flag the critical ones and those that have already broken.
3. During the discovery call, we identify the two or three flows to replace first.
4. During scoping, each connector is described and priced, then built and tested alongside the existing automation before cutover.

The old automation is switched off only after the connector has been verified over several days of real traffic.