Integration
Connecting your ERP, CRM and business tools: automation or custom API integration?
Native connector, Zapier, Make, n8n or a custom-built API integration: how to choose based on your data flows, with CUB3’s pricing and what to prepare.
The short answer
The right choice depends on the data flow, not the tool. A native connector or an automation platform is often enough for simple exchanges between widely used software. A custom API integration is justified when the data needs precise rules, errors must be kept under control or no connector exists. At CUB3, it starts at €3,000 excluding VAT for one tool.
- Describe the flow first: which data, in which direction, how often, and which tool is the source of truth.
- For simple exchanges between widely used software, a native connector or an automation platform is often enough.
- At CUB3, a custom API integration starts at €3,000 excluding VAT for one tool, with a documented API and test access.
- WebAccess through a browser
- PWAAn installable application
- MobilePhone-based usage
Start with the flow, not the tool
When two systems do not talk to each other, your team makes up for it: re-entering orders, exporting files or checking by hand that a payment was actually recorded. Before choosing a technical approach, describe what needs to move between them. A customer, a booking or an invoice does not necessarily have the same structure, or the same fields, in your ERP, your CRM and your invoicing tool.
For each exchange, one question settles a great deal: which tool is the source of truth? If a customer address is changed in two systems, the integration must know which version to keep. Without this rule, a connection creates duplicates and discrepancies faster than manual re-entry does.
- The data exchanged is listed, with its format in each tool.
- The direction of each exchange is defined: from one tool to the other, or both ways.
- The frequency is known: real time, several times a day or at the end of the day.
- A reference tool is designated for each piece of data.
- The expected behaviour in case of an error or duplicate is described.
Native connector, automation or custom integration
Three solutions cover most needs. They are not mutually exclusive: the same company can use a native connector for its messaging, an automation for its notifications and a custom integration for its order flow. The choice is made flow by flow, based on volume, criticality and the rules to apply.
| Solution | Suitable when | Limits to expect |
|---|---|---|
| Vendor’s native connector | Both tools are widely used and the connector covers exactly your data. | You depend on what the vendor has provided: fields, frequency and rules can rarely be adapted. |
| Automation platform (Zapier, Make, n8n) | The flow is simple, volume is moderate and an occasional error can be fixed by hand. | Cost usually scales with execution volume, and scenarios become hard to follow as they multiply. |
| Custom API integration | Mapping rules are precise, volume or criticality is high, or no connector exists. | Development to scope, test and maintain when one of the APIs changes. |
When a custom integration is justified
No-code automation reaches its limits when the exchange concerns the core of the business. A payment recorded twice, a lost booking or an invoice linked to the wrong record costs more than development. Custom work also becomes necessary when the tool to connect offers only a legacy API, SOAP for example, or incomplete documentation.
For Promo.dev, for example, CUB3 integrated Booking.com and Stripe to coordinate hotel booking, cancellation and virtual cards within the business tools. Each step of the journey depends on the previous one: this kind of sequence requires checks that a generic scenario does not provide for.
Precise mapping rules
Data must be transformed, grouped or checked before entering the other tool.
Errors to keep under control
Rejected data must be detected, reported and resent without creating duplicates.
High volume or criticality
Payments, bookings or orders: a silent failure has a direct cost for the business.
No connector available
Industry-specific software, a SOAP API or partial documentation: the connection has to be built and its context pieced together.
No Paper Solution: hotel connectors despite partial documentation
No Paper Solution is an Andorran company that digitises hotel operations internationally. Its in-house team of two developers could not quickly handle every integration its clients requested. A CUB3 engineer works on demand on SOAP and REST connectors to PMS, the property management systems hotels use, notably around OFIS, a component of Oracle Hospitality OPERA Cloud.
Each request starts with understanding the PMS, the client’s flow and the information actually accessible. Documentation may be missing and third-party vendors are sometimes hard to reach, so risks and dependencies are made explicit before any change. After delivery, CUB3 provides support and adjustments, which keeps the in-house team from being pulled away from its other priorities for long.
What an API integration costs
At CUB3, integrating one tool with your application starts at €3,000 excluding VAT, depending on the flows, and the budget is confirmed after scoping. This price assumes a documented API and that test access is provided. It covers scoping the exchanges, authentication, data mapping, connector development, testing and documentation.
It does not cover all your tools: each additional connection needs its own scope. Licences, bulk migration of historical data and redesigning a tool are priced separately, as are hosting and third-party usage charges. A live integration also needs ongoing support, because APIs change: CUB3 application maintenance starts at €300 excluding VAT per month.
| Item | Coverage |
|---|---|
| Scoping the exchanges, authentication and data mapping | Included, from €3,000 for one tool |
| Connector development, testing and documentation | Included |
| Connecting an additional tool | Tailored scope and quote |
| Licences, bulk data migration, tool redesign | Priced separately |
| Hosting and third-party services | At your expense, based on usage |
| Support and adjustments after delivery | Application maintenance, from €300 per month |
What to prepare before requesting a quote
The better the existing systems are understood, the more reliable an integration quote will be. Gather the API documentation, ask the vendor for test access and prepare a few real data examples, anonymised if necessary. These let you check early on what the API really allows, rather than discovering it during development.
If the application to be connected is itself poorly understood, have it examined first: a technical audit clarifies what can be connected safely. If several tools need to exchange data with each other, start with the flow that costs your team the most re-entry, then expand.
- Documentation for each API involved.
- Test access, separate from production.
- Examples of real data, anonymised if needed.
- The list of expected exchanges, with their frequency and reference tool.
- A contact who can approve the business rules.
In the field
A real project
SOAP and REST connectors to hotel PMS, built despite partial documentation and supported after delivery.
The No Paper Solution case