You stop copying data between tools the moment two systems talk to each other directly. Three ways exist: a built-in integration inside the tool, an automation tool such as n8n, Make or Zapier in between, or custom code on the API. Which fits depends on frequency, whether data changes on the way, and who maintains it.
This article is about that choice. Not about which tool is best (see n8n vs Zapier for that), but about which kind of integration belongs to which situation.
Why does manual copying always break eventually?
Because it is work nobody counts as work. A lead arrives through the form, someone adds it to the CRM. The deal is won, someone creates the client in accounting and in the project tool. The invoice goes out, someone sets the CRM status to “invoiced”. Each step takes a minute. Together they add up to hours a week, spread across people who were supposed to be doing something else.
The failure is not in the minute; it is in the gap. Between “arrived” and “copied” there is a delay in which the lead is not followed up, the client does not exist, and the status is wrong. And every manual step is a chance for a number, a name or a date to be typed slightly differently from the source. An integration removes both the delay and the variation: the data is in both places at the same moment, in the same shape.
What are the three kinds of integration?
1. Built-in. Many tools come with their own integrations: your CRM talks to your email, your accounting to your bank, your form to your newsletter tool. Switch it on, log in, done. Cheap and maintenance-free, but you cannot change anything: the tool decides which fields travel and when.
2. Automation tool. n8n, Make or Zapier sits as a middle layer between your systems. A workflow starts on an event (new row, new form, new deal) or on a schedule; n8n’s Schedule Trigger, for instance, can run per minute, hour, day, week or month [S-005]. On the way you can transform, combine, filter and route data to several systems at once. This is the middle road: flexible without programming.
3. Custom code on the API. A developer writes code that talks directly to your systems’ programming interfaces. Anything is possible, including what the tools above do not support. But every change is new development work, and you depend on whoever built it.
Which one should you choose? The decision table
This is the check WeAdapt runs on every integration. Go down the rows; the column you land in most often is your answer.
| Criterion | Built-in | Automation tool | Custom API |
|---|---|---|---|
| How often | every event, no exceptions | every event, with rules or exceptions | high volume, every second |
| Changes on the way | none | yes: rename, combine, filter, enrich fields | complex: own logic, calculations |
| Number of systems | exactly two | two to ten | many, or systems without a standard connector |
| Does the flow change regularly | no | yes, by the team itself | no, stable after delivery |
| Who maintains it | nobody has to | the team, inside the tool | the developer |
| Data must stay in-house | depends on the tool | yes: n8n self-hosted [S-006] | yes |
Two rules of thumb. If an integration starts as “built-in” and grows into “I actually want a rule here”, you have outgrown it and need the automation tool. And never start with custom code if an automation tool can do the job: the difference in maintainability is bigger than the difference in capability.
Which integrations come first?
The one that happens most often and fails most visibly. In small businesses it is almost always these four, in this order:
- Form to CRM. Every lead that arrives is in the CRM immediately, with the right owner. No delay, no forgotten lead.
- CRM to accounting. A won deal becomes a client and a draft invoice. For how that looks with HubSpot, read HubSpot + AI: how to make your CRM work for you.
- Accounting to CRM. Paid, outstanding, overdue: the account manager sees it without opening the books.
- Everything into one overview. The numbers from the three systems above in a single weekly report. That is a reporting workflow rather than an integration, but it only exists once the integrations do.
Marketing tasks such as social scheduling and newsletters come after that; they are covered in 5 marketing tasks you can automate today.
What do you need if you have no developer?
Three things, none of them technical.
- Access. Admin rights on the systems you want to connect, or someone who can grant them. Most integrations run on an API key or a login; without access nobody can build anything.
- A plain-language description of the flow. “When a form comes in, create a contact in HubSpot, assign it to the account manager for that region, and post a Slack message.” If you can write that down, you can have the integration built. If you cannot, you are not ready to integrate yet.
- Somewhere for the workflow to run. For n8n: the cloud version with no installation, or self-hosted if you want to manage the deployment yourself [S-006]. For Make and Zapier: their own cloud.
What you do not need: knowledge of APIs, code, or the differences between tools. That is the part an agency or an experienced colleague handles in an afternoon. To understand when an AI step belongs inside such an integration and when it does not, read automation versus AI automation.
Who maintains the integrations afterwards?
The team. An integration inside an automation tool is a workflow that someone on the team can open, read and adjust: an extra field, an extra recipient, a stricter filter. WeAdapt delivers every integration that way, with documentation and a short training session, so day-to-day maintenance does not depend on WeAdapt.
What does remain: someone has to own it. One person who knows which integrations exist, where they run and what happens when a system changes. Without an owner, an integration ages quietly until someone notices the leads have not reached the CRM for three weeks.
Frequently asked questions
Can a CRM be integrated with existing business software? Almost always. The question is not whether, but through which of the three kinds. If your accounting package has a standard connector in n8n, Make or Zapier, it is an automation-tool integration; if not, it is custom code on the API or an export-import workflow.
What is an API integration? A connection in which two programs talk directly through their programming interfaces, with no person in between. An automation tool uses APIs under the hood as well; the difference from custom code is that you do not have to program it yourself.
Do I need to hire a developer? For most small-business integrations, no. Custom code becomes the better route only when a system has no standard connector, the volume is very high, or the logic gets complex.
What if a tool has no integration at all? There is almost always a workaround: a scheduled export, an email attachment that gets parsed, or a webhook. Less elegant, but it stops the copying.
Sources
- n8n documentation, Schedule Trigger [S-005]
- n8n documentation, Cloud or self-hosted [S-006]
WeAdapt builds integrations between systems as workflow automation: one process rebuilt end to end in n8n, Make or Zapier. Where no off-the-shelf package fits, it becomes a custom AI tool.
Want to know which integration would remove the most manual copying in your business? Book a call. Thirty minutes, no preparation needed.