Integrations

Works with the systems
you already run.

Most contracting software promises integration and delivers a spreadsheet. Unibuild is built as one system, so there is less to join up. This page tells you what each connection does.

Ask about your systems in a demo → Ask for a quote

Site and office systems connected through Unibuild

The connection table

Every connection,
and what it does.

A logo wall tells you nothing. This tells you what happens, and anything you need next is built for you.

01Bookkeeping capture · In daily use: Approved supplier invoices, credit notes and travel orders are emailed to your bookkeeping capture inbox from inside the purchase order record, with the order number, supplier, project and both values already stated in the message body. Each record is flagged as sent so nothing goes twice, and the purchase order list shows a traffic light for what has gone and what is still pending. In the construction deployment, 587 of 711 supplier invoices have been forwarded this way. This is the connection that carries real volume, and the one to ask about if your question is how Unibuild reaches your bookkeeping.
02Microsoft OneDrive · In use: One action on the project record creates your standard folder tree in your own Microsoft tenant, uploads your template documents into it, handles large files, retries the ones that fail, then requests a share link and stores it on the job. The template in live use runs to 52 folders and 185 files, including the full operating and maintenance skeleton. It pushes files into OneDrive, because OneDrive is the document store and Unibuild is the record of the work. Where a firm wants it to run the other way as well, we build it.
03Transactional email · In daily use: Every message the platform sends goes through one service on one verified sending domain, and every message is written to a log with the recipient, the subject, the attachment, the exact content and the send result. 1,783 messages logged. When a client says a certificate never arrived, you open the log rather than your sent items.
04Push notifications · In daily use: Notifications to named users on registered devices, with a distinct tone per event family and a deep link that opens the approval screen itself rather than the app's home page. 5,478 sent and logged across 112 registered devices. Every one is logged with its recipients, its content and the provider's response.
05WhatsApp alerts · Outbound alerts: Outbound template messages to a list of numbers you maintain, so a near miss or an accident reaches a safety manager who may never open the app. Replies are captured against the record. The point is to stop the operational record living in WhatsApp, not to move Unibuild into it.
06QuickBooks, Xero and Sage 50 · Synced: Unibuild syncs with QuickBooks Online, Xero and Sage 50, switched on for your firm. A sales invoice posts across with the customer matched or created, and the accounting reference comes back onto the Unibuild record, after which the invoice locks so the two cannot drift apart. Any other external system your firm runs is synced on request, inside the monthly fee.
07Weather · Available to the app: A forecast lookup the field app can call, with the weather on the day recorded by the author of the site diary.
08QR generation and geocoding · In daily use: Branded codes generated and cached on the platform with a second provider as automatic fallback, so a reprint costs nothing and looks identical. Clock-in coordinates are resolved to a street address for the office view.
09Payroll and any other system · CSV, XML and JSON exports: Timesheet and payroll data, and any other data in the system, exports as CSV, XML or JSON, so the approved week reaches whatever you run without anybody retyping it. A direct sync with your payroll package, or any other system, is built on request, to the format and behaviour you want, inside the monthly fee.

Bookkeeping captureMicrosoft OneDriveAmazon SESPush notificationsWhatsApp alertsWeather lookupQR generationGeocodingQuickBooks OnlineXeroSage 50CSV, XML and JSON exportsToken authenticated APIRequest loggingEmail logsNotification logsSync logsProcessor list Bookkeeping captureMicrosoft OneDriveAmazon SESPush notificationsWhatsApp alertsWeather lookupQR generationGeocodingQuickBooks OnlineXeroSage 50CSV, XML and JSON exportsToken authenticated APIRequest loggingEmail logsNotification logsSync logsProcessor list

Why there is less to integrate

The integration you do not have to buy
is the one between your own systems.

Most contracting firms do not suffer from a lack of software. They suffer from having five pieces of it that do not speak to each other, plus the spreadsheets that exist purely to move information between them.

One database
underneath

Design

Sixty-seven of the platform's tables carry the project reference, so the estimate, the hours, the orders, the deliveries, the photographs, the certificates and the costs are genuinely attached to the same record rather than sitting alongside it.

No sync step to failLive

A proven
API

Built

Eighty-one token authenticated endpoint controllers already carry the mobile app and the client app in daily production. Bespoke connection work builds on a data layer that is proven rather than on a specification.

Not a greenfield projectLive

Everything
logged

Evidence

The email log, the notification log, the sync log with its request and response payloads, and the inbound request log with the user, device and payload. Integration disputes are settled with evidence rather than assertion.

73,351 requests loggedLive

Your systems,
built in

Bespoke

A connection you need is built for you as part of the engagement, inside the monthly fee, on the same proven data layer.

Built for youIncluded

For your data protection assessment

The list your DPO will
ask for, published
before they ask.

These are the third parties data can pass through. Nothing else leaves the platform. We will give you the same list in writing, with the contractual terms, for your record of processing activities.

Third-party processors and data protection records for Unibuild

Always

Transactional email providerPush notification providerQR code generationGeocoding for clock-in locations

Where enabled

Microsoft, for OneDrive storageYour bookkeeping capture serviceWhatsApp messaging providerWeather service

Optional

QuickBooks, Xero or Sage 50, where the sync is switched onThe AI provider, where the AI features are enabled

Never sent

Database credentialsService keysConfiguration filesAny column whose name suggests a password, token or secret

On the AI features specifically

The AI features call an external model. They can be switched off, and the platform was a working system before any of them were added. Where one is enabled, what leaves the platform is the record that feature is working on and nothing else: credentials, configuration and any field whose name suggests a password, token or secret are excluded and redacted before anything is sent, and nothing is sent at all from a module where the feature is off. If that exchange is not acceptable to you, say so and we will turn them off rather than argue about it. What the AI does inside each module is shown in the demo, and the families it runs in are on the AI page.

Stated precisely

Six connections,
stated precisely.

Integration covers everything from a full two-way sync to a file you download, so here is what the word means in each case. Anything more you need from any of them is built for you.

QuickBooks, Xero and Sage 50

Synced, and switched on for your firm. Alongside the sync, the bookkeeping capture inbox described above carries supplier paperwork every day.

Other systems

Any other external system your firm runs is synced on request. Raise it at implementation and it goes in the plan, inside the monthly fee.

Payroll

Timesheet and payroll data exports as CSV, XML or JSON. What sits behind it is approved hours per person per month, split across normal, time and a half, double time, travel and adjustment, plus a payslip style document. If you want it delivered straight into a named payroll package as well, we build that bridge on request.

SFG20

Unibuild holds your own SFG20 schedule documents against the right asset, so the schedule sits where the engineer needs it and your client can see it.

REFCOM

The platform produces a REFCOM presented record log book, with refrigerant, charge weight and CO2 equivalent held per asset.

Email delivery

A failed send is logged with the reason and shown to you, and resending is a human action. The email log records the provider's acceptance of every message, with its content and attachment.

Everything in the connection table above is running in a live business today. Anything more you need from any of the six is built for you.

Questions

The ones a finance director
asks in the first ten minutes.

Does it talk to our accounts package?

Yes. Unibuild syncs with QuickBooks, Xero and Sage 50, and any other external system is synced on request. Supplier invoices, credit notes and travel orders also reach your bookkeeping capture service by email, with the purchase order context attached. Every set of data in the system exports as CSV, XML or JSON as well.

Is this a proper OneDrive integration or just a link field?

Both are there, and the difference matters. There is a manual link field for a folder you already have. There is also a real connection to your Microsoft tenant that creates your standard project folder tree, uploads your template documents into it, handles large files and retries the ones that fail, then requests a share link and stores it on the job. It pushes files into OneDrive, because OneDrive is the document store and Unibuild is the record of the work.

We already use WhatsApp for everything. Does Unibuild replace that?

It takes over the record and leaves the conversation where it is. Unibuild sends WhatsApp alerts through approved message templates to a list of numbers you maintain, for accidents, near misses and clock-in events, and captures the replies. Keep WhatsApp for talking to each other. The point is to stop the operational record living there, because photographs, sign offs, diaries and reports need to be findable in two years. Which events trigger a message, who receives them and what the message says are all set to your firm rather than to a default, and any new message shape you want is built for you.

Our engineers will not use anything complicated. Is any of this their problem?

None of it. An engineer never sees an integration. They fill in the record, sign on the screen and move on. The certificate is produced, the notification reaches the office, the invoice paperwork reaches the bookkeeper, and every one of those steps is logged behind the scenes.

What happens to our existing folder structure?

Your folder structure becomes the template that gets replicated for every new project, so you are not adopting somebody else's filing. If you would rather Unibuild did not touch your folders at all, paste your existing project folder link onto the project record and it will hold that as the link from the job to the documents. If you are on a different platform entirely, the connector is built for you as part of the implementation.

If an integration fails, how would we know?

A failed send returns an error to the person at the time and is written to the log, and the purchase order list shows a traffic light for what has gone across and what has not. Where your volume warrants it, automatic alerting on failures is built for you before go live.

The platform