Almost every small business ends up needing its tools to talk to each other: the website form to the CRM, the store to accounting, WhatsApp to the inbox. There are three ways to do it, and choosing well saves money and future headaches.
The three routes
| Native integration | Automation platform | Custom code | |
|---|---|---|---|
| What it is | A connection built by one of the vendors (for example, your store’s app for your accounting tool) | A tool like n8n, Make or Zapier that moves data between apps using pre-built connectors | Software written for you that calls each tool’s API |
| Set-up | Minutes to hours | Hours to days | Days to weeks |
| Running cost | Often included, or a small app fee | Platform subscription, priced by tasks, credits or executions | Hosting plus developer time for changes |
| Flexibility | What the vendor built, nothing more | High: rules, branches, many apps | Unlimited |
| Who maintains it | The vendor | You (or whoever built it) | You (or your developer) |
| Breaks when | Vendor changes or drops it (rare) | An app changes its API, a credential expires, data looks unexpected | Same, plus no one remembers how it works |
Start native, fill gaps with automation
A simple rule that works for most small businesses:
- Check for a native integration first, in both tools’ app marketplaces. Read what it actually syncs: contacts only, or orders, events and updates too?
- If the native integration covers 80% of what you need, use it, and consider whether the remaining 20% matters.
- Use an automation platform for the gaps: extra rules (create a deal only for B2B orders), tools without a native connection, or a flow across three or more apps.
- Consider custom code only when the points below apply.
When an automation platform is the right choice
- You need conditions: route leads by area, alert only for high-value orders.
- You need several steps: form → CRM → WhatsApp alert → spreadsheet log.
- One of your tools has no native integration with the other.
- You want to change the logic yourself without a developer.
n8n, Make and Zapier each have hundreds of app connectors, plus generic HTTP and webhook steps for anything else. See n8n vs Make vs Zapier for choosing between them and what automations really cost for the running costs.
When custom code is worth it
- High volume: tens of thousands of events a day, where per-task pricing becomes expensive and performance matters.
- Complex logic that’s hard to read in a visual workflow (heavy data transformation, many edge cases).
- It’s part of your product: customer-facing features, a portal, an app.
- Strict requirements: specific hosting, security or audit needs.
Even then, a self-hosted automation platform with some code steps can be a middle ground. n8n, for example, lets you add JavaScript or Python steps inside a visual workflow.
Questions to ask about any integration
| Question | Why |
|---|---|
| What exactly does it sync, and in which direction? | “Integrates with” can mean contacts only, one way |
| What happens to records that already exist? | Duplicates are the most common problem |
| How often does it run: instantly or every few minutes? | Polling delays matter for lead alerts |
| What happens when it fails? Who gets told? | Silent failures lose leads and orders |
| Who owns the account it runs under? | See who owns your accounts |
| Is it documented? | So someone else can fix it |
Keep a register
Whichever routes you use, keep one list of every integration: what it connects, how, who owns it, what it costs, and where its documentation is. The decision sheet includes a register. Review it alongside your software subscription audit.
For automations you build, apply basic production habits: retries, an error alert, and a short runbook. See error handling in n8n and how to document automations.
Frequently asked questions
Is an automation platform “less reliable” than native?
Not inherently. A well-built automation with retries and alerts can be very reliable. Problems come from automations built quickly with no error handling and no owner.
Can we start with Zapier and move later?
Yes. Many businesses start with Zapier or Make for speed and move busy workflows to n8n or code once volumes grow. Document the logic so moving is a rebuild, not a rediscovery.
What about iPaaS or “unified API” products?
They’re aimed at software companies building many integrations into their own product. Most small businesses don’t need them.
If you’d like help choosing and building the right connections, that’s part of our tech stack service.
Free download · Excel worksheet
Integration decision sheet
List each connection you need, answer six questions, and get a suggested route (native, automation platform or custom), plus a register of integrations with owners.
Download itNo sign-up. Opens in Excel, Google Sheets or Numbers.
Rather have it done?
This is the kind of work our tech stack service covers. Tell us where you are today and we’ll reply with a plan and a fixed price.
Let’s talk