Custom integration
No two construction businesses run the same stack. Rather than shipping a fixed list of connectors, we build the integrations your project actually needs — mapped to your data, your workflow and your approval rules.
Our approach
Fortis Sync is designed to sit at the centre of your project information — which only works if it talks to everything around it. Integration is part of the engagement, not an add-on you chase later.
ERP, finance, planning, document management, BIM, identity — if it holds project data and exposes an interface, we can connect it. We map the fields, agree the direction of travel and build the connector as part of your implementation.
Records can flow in both directions with conflict rules you define, so the register in Fortis Sync and the system of record on the other side never drift apart.
A lot of the systems that matter on a project were built in-house or bought a decade ago. Flat file drops, scheduled imports, database views and SFTP feeds are all fair game.
Anything an integration writes is subject to the same access control and logged the same way as a user action. Nothing enters the record without leaving a trace.
Moving off an existing system is an integration problem too. We migrate historical registers, numbering conventions and document metadata so the project history comes with you.
Integration scoping happens in onboarding. You get a defined set of connectors, a test window on your own data, and support for them as part of the platform.
How it works
Every integration follows the same four steps, so you know what is happening and when it lands.
Open by design
Every custom connector we build sits on the same public API your own developers can use. If it is in a register, it is available through the API — push records in, pull them out, or fire a webhook when a status changes, with the same permissions and audit logging as the interface.
Bring us the systems on your project and we will scope the integration with you.