Two hundred integrations, and counting.
Nearly twenty years of making systems that were never meant to talk to each other talk to each other. If it has an API we have probably already written against it - and when it has not, we have built the connector anyway.
A representative list.
Not exhaustive - most of the two hundred were written for one client and one system, and never got a logo.
Mapping & location
- Google Maps
- what3words
- Ordnance Survey
- OpenWeather
- Postcode lookup
- Route optimisation
Accounting & finance
- Sage
- Xero
- QuickBooks
- Spreadsheets
- Nominal ledger exports
- Credit control feeds
Payments & wallets
- Stripe
- PayPal
- GoCardless
- Apple Pay
- Google Pay
- Apple Wallet
- Google Wallet
- Card terminals
Messaging & comms
- Mailgun
- Twilio
- SendGrid
- Slack
- SMTP relays
- Push notifications
Identity, signing & KYC
- Azure AD
- Active Directory
- LDAP
- DocuSign
- reCAPTCHA
- SSO / SAML
- Custom KYC
- Custom AML screening
Trade & logistics
- EDI Tradacoms
- EDIFACT
- Royal Mail
- GS1 barcodes
- Zebra label printers
- Courier manifests
Health & telephony
- EMIS
- Mitel
- Active Directory
- HSC directory services
- HL7-style record feeds
Data & cloud
- Power BI
- Microsoft 365
- AWS S3
- Dropbox
- Firebase
- Scheduled data warehouse loads
There is always a way in.
Half the systems a business depends on were written before anybody thought about integration. That has never been a reason to say no.
SFTP and file drops
A watched folder, a fixed layout and a parser that does not fall over when the supplier changes a column.
Straight at the database
Read-only views, change tracking or a staging table, where the vendor will allow it and the licence permits.
Custom middleware
A small service that sits between two systems that will never speak the same language, and translates.
Queues and webhooks
So a slow third party cannot take your own system down with it when it has a bad afternoon.
The bits that stop it breaking at 3am.
- Every call is idempotent - retrying it does not double an order or an invoice.
- Failures queue and retry with backoff instead of vanishing into a log nobody reads.
- Every request and response is logged, so a dispute can be settled with evidence.
- Credentials live in a vault, not in a config file in source control.
- We build against the sandbox first, then switch endpoints - never test in your live ledger.
- Alerting when a feed goes quiet, because the dangerous failure is the silent one.