Contents6
The quote is in a spreadsheet, the customer in the CRM, the invoice in the accounting software, and someone copies from one to the other. Connecting your business tools puts an end to that role of human cable: information entered once flows on its own to every piece of software that needs it. This article from our section on process automation and business bots explains why tools do not talk to each other, how to connect them without replacing everything, and what e-invoicing and AI change in the picture.
In short
Each department chose its own software, and nobody planned for them to talk to each other: teams make the link by hand.
The basic rule: for each piece of data, one tool is the reference, and the others read it instead of retyping it.
Three ways to connect: the software’s API, an automation tool such as n8n, and the MCP protocol to plug AI into your tools.
In France, e-invoicing, mandatory for receiving invoices since September 2026, is a good opportunity to connect invoicing to everything else.
Why don’t your tools talk to each other?
Because nobody chose them to talk to each other. Each department adopted its software as needs arose, often on subscription, and their number climbed quietly:
on average in companies of 1 to 500 employees tracked by the vendor Zylo, according to its 2025 SaaS Management Index, based on its customers’ data
of office workers spend at least a quarter of their week on manual, repetitive tasks such as collecting and entering data, according to a 2017 Smartsheet survey of around 1,000 people in the United States
Each piece of software does its job well; the time is lost between them. An order entered twice can be entered with two different amounts, a customer updated in one tool stays out of date in another, and the leadership dashboard, when there is one, is filled in by hand.
What does “enter it only once” mean?
The principle fits in one rule: for each piece of data, one tool is the reference. The customer lives in the CRM, the invoice in the invoicing software, the stock in the management tool; the other tools read or receive them, but never retype them. This is what is called a single source of truth.
On Palmora Property, a property portal we run, the Twenty CRM replaced in May 2026 the spreadsheet where the listings used to live. It became the single source for properties, contacts and deals, and the website updates itself from it, as detailed in our article Twenty beyond the CRM: the back office for your business data. Visitor enquiries follow the same principle:
A contact request, entered only once
- The form
The visitor describes their request on the website.
- The database
The request is stored before any email is sent.
- The CRM
The contact and the deal are created there, without retyping.
- The team
It is notified in its channel.
One client learned this the hard way: on Palmora Property, these requests were at first only sent by email, and a failed send went unnoticed while the website displayed a success message. Information that only lives in an inbox is stored nowhere.
How do you connect tools that don’t talk to each other?
Through their API
Most recent software has an API, an entry point designed for other programs, and can send a notification when an event happens: an order paid, a ticket opened. It is the most robust link, because it goes through the door the vendor maintains. When a piece of software has none, other doors exist, from scheduled exports to a driven browser, which our article Automating software without an API: six ways in compares.
Through an automation tool
An orchestrator such as n8n makes the link between APIs: when the order is paid, it creates the invoice, updates the CRM and notifies the team. n8n advertises over 500 ready-made integrations and a so-called “fair-code” licence, the Sustainable Use License, which allows self-hosting for internal use. Most of these links are simple rules, with no AI, as our guide Automation without AI: when a rule is enough shows. Our comparison n8n, Make or Zapier: which one for a small business? helps you choose the tool, and our page on n8n explains how we use it.
Through MCP, to plug in AI
A third route has been added for AI assistants. The Model Context Protocol, or MCP, is an open standard that lets an assistant connect to the tools where your data lives: the CRM, the calendar, the document base. In a year, it went from one vendor to the whole industry:
- November 2024
Anthropic open-sources MCP as an open standard for connecting AI assistants to the systems where data lives.
- May 2025
Microsoft announces support for it in GitHub, Copilot Studio, Dynamics 365 and Windows 11, and OpenAI opens it in its API; its documentation presents it as on its way to becoming the industry standard.
- December 2025
MCP is handed over to the Linux Foundation’s Agentic AI Foundation, which then counts over 10,000 published MCP servers, and Google Cloud opens managed MCP servers for its services.
MCP therefore no longer belongs to a single vendor. In practice, an MCP server connected to your CRM lets you ask an assistant which deals have not moved in two weeks, without exporting a single spreadsheet. Our page on MCP servers explains what they bring to a team.
E-invoicing, an opportunity to connect invoicing
In France, the e-invoicing reform gives a concrete reason to connect invoicing to everything else. Since 1 September 2026, all businesses must be able to receive electronic invoices, and large and mid-sized companies must already issue them; SMEs and micro-businesses will follow on 1 September 2027. Above 250 people, a company is no longer classed as an SME: a company of 250 to 500 people therefore usually already issues its invoices in this format.
On 9 October 2026, the French Ministry of the Economy stated that no penalties would be imposed before the end of 2026, and that as of 4 October, 75% of VAT-registered businesses had designated their receiving platform. Choosing this approved platform is a chance to ask where invoices go next: an invoice received as structured data can feed accounting, payment reconciliation and the dashboard without being retyped.
Watch out
Connecting everything to everything
Plugging each tool into every other one quickly creates a tangle nobody knows how to repair. Start from the source of truth for each piece of data, route exchanges through a central point, the automation tool, and monitor each link: a connection that breaks silently does more damage than retyping. Also give each link, like each AI assistant plugged in through MCP, only the permissions it needs; our article on the secrets vault shows how its keys stay out of sight.
Where to start?
Connecting your tools happens one link at a time, starting with the ones that cost the most retyping:
- Take inventory.
List your tools, what each one contains and who fills it in.
- Designate the sources of truth.
For each important piece of data, one tool is the reference.
- Spot the retyping.
Ask teams what they copy from one tool to another every week: that is the list of your first links.
- Connect, then monitor.
One link at a time, each with its own alert on failure, as described in our guide to monitoring your n8n workflows.
Once the tools are connected, information flows from one department to another without waiting for anyone: it is the first condition for running your company as a system, with a dashboard that fills itself in.
Our digital and AI maturity audit builds this inventory with you: the list of your tools, what each one costs you, and what connects to the others or not. Our automation offer then connects your tools one process at a time, each link delivered with a meter showing what it costs.
Frequently asked questions
What is a single source of truth?
It is the tool that is the reference for a specific piece of data: the CRM for customers, the invoicing software for invoices, the management tool for stock. Other software reads or receives this data, but never retypes it. When two tools disagree, the source of truth is right, and the other must be corrected automatically from it.
Should you replace your software with an all-in-one ERP?
Not necessarily. An ERP such as Odoo or Dolibarr brings several functions together in one piece of software, which removes some of the links to build, but the migration is a real project. When your current tools do their job well, connecting them often costs less and disrupts teams less. Our comparison Twenty, Dolibarr or Odoo helps you decide based on team size.
What do you do with software that has no API?
Work from what it produces or receives: a scheduled export, the emails it sends, the documents it generates, its database in read-only mode, or as a last resort a driven browser. The closer the door is to the data, the more robust the link. Old business software therefore does not stop you from connecting the rest of your tools, it just needs a different way in.
Does MCP replace APIs?
No, it builds on them. An MCP server translates a piece of software’s functions, often exposed through its API, into actions an AI assistant knows how to use. For a flow that must always run the same way, such as creating an invoice for each paid order, an automation tool remains simpler and more predictable. MCP is useful when a person queries or drives their tools in natural language.
Does e-invoicing force you to change software?
Not necessarily. Since 1 September 2026, every French business must be able to receive its invoices through a platform approved by the tax authorities, and SMEs will have to issue them that way from September 2027. You need to choose this platform and check that your invoicing software can exchange data with it. It is also the right time to have invoices land directly in accounting.
Sources
- Its 2025 SaaS Management Index (new tab)zylo.com
- A 2017 Smartsheet survey (new tab)smartsheet.com
- N8n website (new tab)n8n.io
- N8n documentation, Sustainable Use License (new tab)docs.n8n.io
- Open-sources MCP (new tab)anthropic.com
- Announces support for it (new tab)blogs.microsoft.com
- Its documentation presents it (new tab)developers.openai.com
- The Linux Foundation’s Agentic AI Foundation (new tab)linuxfoundation.org
- Opens managed MCP servers (new tab)cloud.google.com
- Impots.gouv.fr, e-invoicing reform timeline (new tab)impots.gouv.fr
- French Ministry of the Economy, press release of 9 October 2026 (new tab)presse.economie.gouv.fr
French Ministry of the Economy, press release of 9 October 2026
Read on presse.economie.gouv.fr(new tab)Jim · founder of Brain Plus AI
Also in automation and bots
Practical guide7 min
Automating software without an API: six ways in
Your business software has no API, or keeps it for a more expensive plan? There is usually still a door for automating it: here are the six, from the most solid to the most fragile, with what each one costs in maintenance.
Practical guide9 min
Twenty beyond the CRM: a back office for your business data
Properties, projects, equipment, case files: Twenty can hold far more than your contacts. What it takes to make it the back office for your business data, connected to your site, and where this use stops.
Understand9 min
Running your company as a system, not in reaction
Most companies move forward in reaction: a customer chases, someone searches, things get fixed. Thinking of the organisation as a system of loops shifts the effort: automations relay information, a dashboard shows where it piles up, and people keep the judgement.