- For simple, modest-volume links between popular apps, Zapier, Make or Power Automate is usually the right answer. Start there.
- All three charge by usage, so cost grows with volume and with the number of steps in each flow.
- The bill is rarely the most important warning sign. Exceptions handled by hand, failures nobody notices and flows only one person understands matter more.
- A custom connection earns its cost when records must be matched across systems, volume is high, or a failure costs real money.
- Most organizations end up with a mix: connector tools for the simple links, custom code for the few that carry the business.
Where connector tools are the right answer
Zapier, Make and Microsoft Power Automate let someone without a programming background connect two apps in an afternoon. A new form entry creates a row. A signed deal posts to a team channel. An invoice paid in one system marks the order paid in another.
For work like this, they are hard to beat. They're quick to set up, inexpensive at low volume, and come with ready-made connectors for thousands of apps. If your organization runs on Microsoft 365, some Power Automate use may already be included in licenses you pay for.
Use them, without apologizing for it, when:
- The link is between two well-known apps with ready-made connectors.
- Volume is modest: hundreds or a few thousand runs a month.
- A missed or late run is an annoyance, not a lost sale.
- The logic fits on one screen.
- Someone on the team owns it and checks on it.
If that describes your situation, you can stop reading. A custom build would cost more and give you little.
How the pricing works, and why it matters
All three tools charge by usage, but they count it differently. Zapier counts a task each time an action step succeeds. Triggers, filters and built-in formatting steps don't count. Make bills in credits: most module actions use one, and a single run can use anywhere from two to thousands. Power Automate licenses people, and can also license individual flows, with daily limits on actions for each.
The part that matters is simple. Cost grows with volume times steps. A five-step flow that runs 3,000 times a month is 15,000 billable actions. Add a lookup, a branch and a cleanup step, and the same work costs more. On paid Zapier plans you can keep running past your allowance at a higher per-task rate, up to a ceiling where usage stops. On Make, scenarios stop when credits run out until you add more.
None of this is unfair. It's a sensible way to price a shared service. It just means the bill grows with the business, which is fine until the day it isn't.
Signs you've outgrown them
The bill is the sign people notice first. It's rarely the most important one.
Volume and cost keep climbing
If you move up a tier every few months, or split flows to stay under a limit, the tool has started shaping the process instead of serving it.
The logic has grown branches
Real processes have exceptions. "If the customer is in Canada, use the other tax code, unless it's a renewal." Each exception becomes a path, a filter or a lookup. Past a point, nobody can read the whole flow, and a small change breaks something three steps away.
Failures happen quietly
Every connector tool handles errors. Zapier can replay errored runs, and paid plans can retry them automatically. Make can save a failed run as an incomplete execution so you can finish it from the step that failed. But someone has to look. If an order sync failed on Tuesday and nobody noticed until a customer called on Friday, the tool did its job and the process still failed.
The builder left
Flows belong to people. When someone is removed from a Zapier team account, their Zaps move to another user, but their app connections are only kept for a set period or until they expire. Microsoft documents the same risk for Power Automate: flows whose owner has left can fail if they use that person's connections, and an admin has to assign a new owner. That's not a flaw in either tool. It's what happens when business-critical logic lives in one person's account.
Records need matching across systems
Connector tools are good at "when this happens, do that." They're weaker at "find the same customer in three systems that spell the name differently, and decide which record wins." When matching and cleanup become the real work, a flow is a fragile place to keep it.
Security review starts asking questions
Who can see the data passing through? Which logins does each flow use? Who changed it last? Higher plans help. Zapier's Team plan adds single sign-on and an audit log, and Enterprise adds tighter admin controls. Even so, you're adding another company between your systems, and some reviewers will want fewer of those.
Two or three of these together, especially quiet failures and a departed builder, is the moment to rethink.
Side by side
| Question | Connector tool | Custom connection |
|---|---|---|
| Time to first version | Hours to days | Weeks |
| Cost shape | Low to start, grows with volume and steps | Build cost up front, then hosting and upkeep that barely move with volume |
| Exceptions and rules | Fine for a few, hard to read past a dozen | Written once, in one place, and tested |
| When a run fails | Replay and retry tools, if someone checks | Can be designed to alert the right person and queue the record for a fix |
| Ownership | Tied to a person's account and logins | Runs on accounts the organization controls |
| Matching records across systems | Possible, but fragile | A strength, with rules you can inspect |
| Security review | Another vendor in the path; stronger controls on higher plans | Fewer parties in the path, but you own the security work |
| Best fit | Simple, modest-volume, low-stakes links | The few flows that move money or customer data at volume |
What a custom connection changes
A custom connection is software written for your systems and your rules, running somewhere you control. Four things change.
Cost stops tracking steps. You pay to build it, host it and keep it current. A flow that runs a million times a month costs roughly what one that runs ten thousand times costs.
Rules live in one readable place. "The other tax code, unless it's a renewal" becomes a rule someone can read and test, not a branch buried in a visual editor.
Failures become a list someone works. A failed record can land on a screen with the reason and a retry button, and the person who can fix it gets told.
Ownership belongs to the organization. It runs on accounts the business controls, not one employee's login, and the next developer can find and read it.
What it doesn't change: someone still has to own it. Apps change their fields and limits. A custom connection with no budget for upkeep also fails quietly, just somewhere else. Our guide to connecting your systems covers the planning that comes before any build.
The middle path
This isn't all or nothing. Most organizations that outgrow connector tools keep using them.
Keep the simple links in Zapier, Make or Power Automate. Move the two or three flows that carry money or customer data into custom code. Let the connector tool keep the long tail of notifications and small conveniences that nobody would pay a developer to build.
Two made-up examples show the pattern.
A 120-person distributor runs 40 Zaps. Thirty-six are alerts and small conveniences. Four sync orders, stock levels and invoices between its online store, warehouse system and accounting. Those four drive most of the task bill and every painful incident. They move to a custom connection with a screen for failed records. The other 36 stay put.
A regional services firm uses Power Automate for approvals inside Microsoft 365, where it fits well. Its client intake, which matches new requests against existing clients in two systems, keeps creating duplicates. Only intake gets rebuilt. Approvals stay where they are.
Which flows to move, and in what order, depends on what each one costs you when it breaks. That's the question to start with, not which tool is better.
What most guides miss
Count the hours, not just the bill. The real cost of a struggling flow is the person who checks it every morning, restarts the stuck runs and retypes what didn't sync. That often costs more than the subscription.
Stakes matter more than volume. A low-volume flow that moves money deserves more care than a high-volume one that posts reminders.
The flow is often the only documentation. If the only description of how orders reach accounting is a 30-step visual flow, that's a risk whether you switch or not. Write the rules down in plain language either way.
Switching is a migration. Run old and new side by side for a short period and compare the results before turning the old one off. The differences are where the unwritten rules hide.
How we do it
We start by listing your flows and asking what each one costs when it breaks. If Zapier, Make or Power Automate is the right home for most of them, we'll say so, and we build custom connections only for the few that need them. We also stay on after launch to support and extend the system as your tools and processes change. Tell us which flows worry you and we'll tell you which ones to move.
Sources
- Zapier Help Center: What counts as a task
- Zapier: Plans and pricing
- Zapier Help Center: Replay Zap runs
- Zapier Help Center: Remove members from your Team or Company account
- Make: Pricing and credits
- Make Help Center: Manage incomplete executions
- Microsoft Learn: Types of Power Automate licenses
- Microsoft Learn: Manage orphaned flows when owner leaves organization
