API & Business Integrations
Custom integrations for what off the shelf automation can't cover
n8n, Make and Zapier cover most cases. Some don't have a prebuilt connector, need to turn unstructured documents into usable data, or need a small purpose-built application instead of another automation subscription — that's where custom API work comes in.
Is this the right fit?
This is the right fit when two systems need to talk and no existing connector does it, when documents or scraped content need to become structured data, or when the actual need is a small custom tool rather than a workflow.
Problems this solves
- Two systems need to talk to each other and no prebuilt connector exists
- Documents or unstructured content need to become structured, usable data
- The business needs a small custom application, not another automation platform subscription
- Appointment and finance data live in separate systems with no automatic way to keep them aligned
What I build
- Connected automation between Cliniko, Notion and Make keeping healthcare appointment and finance data aligned
- A Python scraper feeding an n8n workflow that structures lead data automatically
- A purpose built integration between two internal or third party systems via their APIs
- REST API, webhook and OAuth integration work where a platform's own connector doesn't cover the case
Tools
Real proof, not a promise
Cliniko Healthcare Workflow Automation
Connected automation between Cliniko, Notion and Make keeping appointment and finance data aligned.
Read the case studyLead workflow automationLead Generation Web Scraping System
A Python and n8n system that scrapes and structures lead data automatically.
Read the case studyHow this works
Every engagement starts with how the process actually runs today, then moves through design, build, and testing against real data before handover. See the full five step process for the details.
Frequently asked
What counts as a 'custom' integration versus a normal automation?
If n8n, Make or Zapier already has a reliable connector for both systems, that's normal automation work. Custom integration means writing directly against a platform's API or webhooks — usually because no connector exists, or because the case needs logic a pre-built connector can't express.
Can you build a small internal tool instead of another automation?
Yes — sometimes the right answer genuinely is a small purpose built application rather than another automation platform subscription, and that's part of what a custom integration engagement can cover.
Do you work with healthcare or other regulated data?
The Cliniko healthcare workflow automation project connects appointment and billing data across systems the practice already uses, moving data that's already legitimately accessible rather than introducing new access.
Have a process like this to automate?
Tell me what's slow or manual right now. I'll tell you what it takes to fix it.