Comes in from the ERP
- Customers
- Addresses
- Assets
Integration
GMAO CLOUD and Libra
Spanish ERP widely deployed in the agri-food sector and distribution.
What travels, and in which direction
Goes out to the ERP
This connector doesn't send data back from GMAO Cloud to the ERP.
What makes Libra different
This connector stands out for something almost no other one does: besides customers and addresses, it imports assets. In an operation where the equipment and facilities master already lives in the ERP, that saves the heaviest part of a rollout, which is building the inventory. In exchange, it doesn't send work orders back, so the path to billing is handled separately.
The first step isn't technical
Before connecting anything, you need to decide which system is authoritative for each piece of data. The ERP is usually authoritative for customers, addresses, items, and price lists; the CMMS is authoritative for assets, interventions, and consumption. Once that's clear, the integration is a matter of configuration; when it isn't, it becomes a permanent source of duplicates and manual fixes on both sides. It's the best-spent half hour of the whole project.
Shall we look at it with your way of working?
Leave your details and we will get in touch to see whether we fit. No commitment, no lock-in period.
And if your case doesn't fit
This connector covers a specific scope, and not every operation fits within it. For everything else there's a separately documented public REST API, plus SOAP, direct database connection, and CSV and FTP exchange. In practice, a good share of new integrations get solved via API with a small amount of development on the other end, and what takes the most time isn't the connection itself: it's mapping the master data so the two systems recognize each other. The API documentation is at developers.gmao.cloud.
Frequently asked questions
What data travels between GMAO CLOUD and Libra?
From Libra: customers, addresses, assets. And it does not send data back to Libra: that direction gets scoped separately if needed.
Does the integration run in real time?
It depends on the connector’s mechanism and what the other system allows. Connectors that work against an API or a database can run immediately; ones that exchange files run on cycles. This gets decided in the demo based on how you operate.
What if my data isn’t clean?
That’s the normal case, and it’s worth knowing upfront: the real work of an integration isn’t the connection, it’s mapping the master records so both systems recognize each other. Duplicate customers or items with two different codes need to be resolved first.
Does GMAO CLOUD replace Libra?
No, and it shouldn’t. Libra manages its own scope and GMAO CLOUD manages maintenance. They’re complementary systems, which is why the connector exists instead of a replacement.
Is it included in the price?
The public API and email-based integration are included in every plan. Connecting to a specific ERP is quoted separately, because the effort depends on what data needs to travel and the state of the other system.
Tell us what you work with
In the demo we'll look at your Libra setup, what data needs to travel, and in which direction.