API integrations for systems that weren't built to talk.
When there's no native integration, or the one that exists isn't good enough, we build the connection: custom API work, webhooks and middleware that move data between your platforms reliably. It's the layer that makes the rest of your automation possible.
Fixed priceAgreed in writing before we build
Yours to keepBuilt in your accounts, with your credentials
MonitoredFailures alerted, retried and logged
A real replyIn writing, within one working day
Native integrations only go so far.
Most tools connect to a handful of others, a few fields at a time, in one direction. These are the situations where a proper integration earns its place.
There's no integration at all
The two platforms you depend on have never heard of each other, so someone copies data between them by hand.
The built-in one is too shallow
It syncs a few fields one way, can't handle your logic and breaks quietly when something changes.
A platform with no webhooks
It can't tell anything else when something happens, so we find another trigger and design around it.
Data that needs reshaping
Different IDs, formats and time zones between systems, translated reliably every time.
Two APIs, one process
A single action that has to update several systems in the right order, and recover cleanly if one fails.
Older or niche platforms
Software with limited or unusual APIs that the usual connectors don't support.
A full API build on Randox, not a plug-in.
For Modern Man Clinic we built a booking backend on Randox's clinic booking API and their ordering system, with Stripe for payment and Notion for the record. Clients book and pay for blood tests on the clinic's own website.
Choose your blood test
Choose a Randox clinic
Pick a time
Pay securely
You're booked
Advanced hormone panel
Clinic B · Tuesday 10:00
- Two APIs, one checkout. Separate systems with separate authentication, coordinated in sequence, with access tokens cached between requests.
- Payment verified on the server first. The lab order is only created once the payment is confirmed, and each payment can only ever create one booking.
- Slots held during checkout. The appointment is reserved with Randox while the client pays.
- Time zones handled. Randox works in UTC; clients see UK time, tested across BST and GMT.
The integration work we take on.
Third-party API integrations
Connecting your platforms through their published APIs, beyond what their own connectors offer.
Custom API connections
Calls built by hand for the endpoints and logic your process actually needs.
Webhooks
Receiving events the moment they happen, and sending your own to other systems.
Data synchronisation
Two systems kept in step, with deduplication and clear rules for which one wins.
REST APIs
Pagination, rate limits, retries and errors handled properly, not just the happy path.
Authentication
API keys, OAuth and token refresh, with secrets kept on the server and out of the browser.
Data transformation
Formats, IDs, units and time zones translated between systems reliably.
Custom middleware
A small backend between platforms when the logic is too much for either side.
Older and non-native platforms
Workarounds for software with limited APIs, using exports, email or neighbouring tools.
Integrations you can leave running.
Secrets stay server-side
Keys and tokens live in your accounts' secure settings, never in a web page or a shared document.
Safe to re-run
A retry or a duplicate webhook never creates two records, two orders or two emails.
Retries and rate limits
Temporary failures are retried with back-off, and calls stay inside each provider's limits.
Validated in and out
Data is checked before it's sent and after it comes back, so bad records stop at the door.
Logged and alerted
Every call can be traced, and failures alert a person instead of disappearing.
Documented
Endpoints, authentication and failure behaviour written down for whoever looks after it next.
API integration questions.
Do you need API documentation before you start?
It helps, but it isn't essential. We'll read whatever exists, test against a sandbox or a test account where there is one, and talk to the provider's support when the documentation runs out. Randox's APIs, for example, involved two separate systems with their own authentication.
What if the platform has no API?
There's usually another way in: webhooks, scheduled exports, email notifications or events from a neighbouring tool. Modern Man Clinic's coaching platform had no webhooks, so we used Stripe and Notion events as the triggers instead. If nothing can be made reliable, we'll tell you rather than build something fragile.
Where does the integration run?
In n8n wherever possible, so it sits alongside the rest of your automation. When it has to serve a web page or keep keys out of the browser, we use a small serverless backend instead, which is how the Randox booking integration works.
Who owns the code and the keys?
You do. Integrations run in your accounts with your credentials, and you get the code or workflow exports, a list of the credentials used (never the secrets themselves) and notes on how each connection behaves when something fails.
Tell us which systems need to talk.
Name the platforms and what should move between them. We'll reply in writing within one working day with how we'd connect them, and what we'd need to check first.
- You send a messageA few details and what you need. Plain English is fine.
- We reply in writingWhether it's worth automating, how we'd approach it and what we'd need to know.
- A 30-minute call, if it makes senseWe map the process with you and agree what a first build would include.
- A fixed quoteScope and price agreed before any work starts.