1. Home
  2. Services
  3. Integrations and Automation

Service

Integrations and Automation

Your accounting, billing, payroll and operations systems were never designed to talk to each other. We make them, using official APIs where they exist and careful, respectful automation where they do not.

Every system, one reconciled view

The most valuable integration project we have delivered joined four systems that could not see each other: Xero for money, a stable-management product for horses and billing, an HR platform for staff hours and leave, and a racing results database. None of them could produce per-horse profitability. The platform on top of them can, and every number reconciles back to its source with a zero residual. The client never changed how they use their own systems. Read the case study.

Integration approaches, in order of preference

  1. Official APIs. Xero through a read-only custom connection, reconciled daily by a scheduled job with a twelve-month history backfill. Google Sheets for import and export. Firebase for push notifications. Public weather observations and forecasts.
  2. Scheduled exports. Where a vendor offers CSV exports but no API on your plan, we build an importer with downloadable templates, validation, an anomaly guard that refuses a broken file, and a merge that never deletes history.
  3. Email ingestion. Many systems will email a report on a schedule. A Cloudflare Email Worker receives it, parses the attachment and loads it, with no inbox polling.
  4. Headless-browser automation. A small Raspberry Pi running Playwright on a timer can log in to a portal and download the daily report. We design these as a "light pull": only the day's changes, at a randomised time, with monitoring, so the vendor's system is not loaded. We have switched one off at a vendor's request and redesigned it before re-enabling it, and we will always respect a vendor's terms.

Collectors that tell you when they stop

An integration that fails silently is worse than none, because people keep trusting the numbers. Every collector we build has a dead-man's switch: a freshness endpoint watched by an uptime monitor, a daily health ping, a data-freshness banner in the application and a named "as of" date on every report. When a feed stops, the people reading the dashboard know within hours, not months.

Integrations we have built

  • Xero profit-and-loss by location, reconciled to Xero's own totals to the dollar, allocated to individual horses by days on site.
  • Payroll and HR headcount and hours per site, used to allocate untagged wages, with the allocation clearly labelled as an estimate.
  • Daily location and movement files merged into a platform's own history with an anomaly guard.
  • Google Sheets import of a 52-tab daily training sheet into a validated scheduling platform.
  • Live Bureau of Meteorology observations and an Open-Meteo forecast feeding a rowing conditions page with a cancel-and-notify flow.
  • Betfair, bookmaker and racing-data feeds polled on a schedule with a three-tier fallback when a source goes down.

Have something you need built?

Tell us the problem, the systems you already use and what a good outcome looks like. You will get a plain-language reply within one business day, usually with a first sketch of how we would build it.