Integrations: the systems Mirage agents read and write
Your systems stay in place. Mirage connects to each one through the interface its vendor provides, and where there is none, our engineers build the connector during the deployment. More than 200 systems connected so far.
Works with the software you already run
Dynamics
Mirage holds no partnership, certified connector or marketplace listing with these vendors. Each integration is built for your own instance.
ERP and accounting
Orders, invoices and entries written into the ERP your finance and operations teams already use.
- SAP Business One
- Orders created directly in the ERP. In production at Biodéal: a median of 48 seconds from the email arriving to the order being ready in SAP Business One, with about 7% of orders flagged for a person.See the Biodéal case studySee SAP order automation
- Microsoft Dynamics 365
- Supply Chain Management: sales order headers and lines created through Microsoft's data entities over OData, under a Microsoft Entra application registered in Dynamics. On Business Central, evaluate Microsoft's own Sales Order Agent first.See Dynamics 365 order automation
- SAP, Oracle, Sage, Salesforce
- Through the system's API or a file exchange, set up on your instance.
Freight and transport
Shipments, bookings and declarations entered in the TMS, through the mechanism each vendor documents.
- CargoWise
- Through eAdaptor, CargoWise's integration interface, configured against your own setup.See the CargoWise integration
- Logitude World
- Through the Logitude World API. In production at OFRET Groupe, with the automation built inside the TMS its teams already used.See the OFRET case study
- Magaya
- Through Magaya's XML web service API.See TMS data entry automation
- Descartes
- Through Descartes messaging, or the API of the Descartes product you run.See TMS data entry automation
Construction
Drawings and documents read where the project lives, quantities returned where your estimators work.
- Procore
- Through Procore's documented API and webhooks, within the permissions your administrator grants.See the Procore integration guide
- Autodesk Construction Cloud
- The connection is built during the deployment.
- Oracle Aconex, Primavera P6
- Both publish an API, and Mirage connects to it.
- Drawings and models
- PDF and DWG sheets, scanned or vector, and IFC where a model exists. Quantities go out to Excel or to the import format of your estimating software.See construction
Field and operations systems
The operational data behind assets, trips and stock, for control rooms and fleet systems.
- Telematics and positioning
- Vehicle positions, trips, cycles and idle time.
- SCADA and equipment telemetry
- Through the approved interfaces available in the operating environment.
- Weighbridges
- Weighing tickets checked against orders and trucks.
- Maintenance and terminal systems
- Work orders, berth plans and appointments, linked to the events they explain.See the control room
Documents, email and files
What the operation actually runs on, read as it arrives.
- Email inboxes
- Orders, quotes, invoices and notices read as they arrive.
- PDF, scans and spreadsheets
- Native and scanned PDF, scanned forms, Excel and CSV, and the text of the email itself.
- EDI and flat files
- Read where your customers and partners already send them.
When a system has no API
Mirage builds the connector as part of the deployment, or uses an import file where the system takes one. Nothing is migrated and no system is replaced.
Frequently asked questions
SAP (Business One included), Oracle, Microsoft Dynamics, Sage, Salesforce, CargoWise, Logitude World, Magaya, Descartes, Procore, Autodesk Construction Cloud, Oracle Aconex and Primavera P6, plus telematics, maintenance, weighbridge and SCADA systems. More than 200 systems connected so far.
Mirage builds the connector during the deployment, or uses an import file where the system takes one.
No. Your systems stay in place and nothing is migrated: the agents read from them and write into them.
No. Mirage holds no partnership, certified connector or marketplace listing with any software vendor. Each integration is built for your own instance, through the interface the vendor documents.
What an agent may write on its own, and what waits for a named person on your team, is set for each workflow. Every action is recorded with its inputs, its sources and its result.
It is built as part of the first workflow, which reaches production in 4 to 6 weeks. A proof of concept on your own data comes one week after the first meeting.
Bring us the operation you need to improve.
Mirage will map the workflow, identify what can be automated and define the fastest path to production.
Start with a written plan
Tell us where your team loses time. We send back which workflows are worth automating, what a deployment involves on your systems and the shortest path to production. No commitment.