Healthcare Operations
Cliniko, Notion and Make: keeping healthcare operations in sync
A healthcare practice running Cliniko, spreadsheets and Notion side by side doesn't have a software problem, exactly — each tool does its job. What it has is a synchronization problem: three places that need to agree, and no automatic way to make sure they do.
The real problem: three systems, one truth
The practice behind this project managed appointments and finances across Cliniko, spreadsheets and Notion, with no automatic way to keep them aligned. That's a specific kind of risk in a healthcare setting: a billing record that doesn't match an appointment record isn't just an inconvenience, it's the kind of discrepancy that takes real staff time to track down and correct after the fact.
The goal wasn't to replace any of these tools. Cliniko is a genuine clinical practice management system, Notion is where the team already organizes day to day operations, and neither needed to go away. What needed to happen was for information to move between them automatically instead of by hand.
The system: Cliniko, Google Sheets and Notion connected through Make
The automation layer connects Cliniko, Google Sheets and Notion, built around the practice's real appointment and billing workflow rather than a generic template. When something changes in Cliniko, that change is what drives the rest of the system, not a separate manual step someone has to remember to trigger.
Make is the orchestration layer here, and the reason is the same one that shows up across most of this healthcare-adjacent work: the people who need to trust this system day to day aren't developers, and a visual, linear scenario is something they can actually look at and understand, not a black box they have to take on faith.
Why this is a Make project and not an n8n one
This is a direct application of the same decision framework I use for every automation platform choice: who's maintaining it, and how linear is the logic. Appointment and billing sync is fundamentally "when X changes here, reflect it there" — genuinely linear, without much need for custom conditional branching or code. That's exactly the profile where Make's visual scenario builder is the better fit, not a consolation choice.
If this workflow needed to make judgment calls, like deciding how to handle a genuinely ambiguous billing conflict, that would be a real argument for n8n instead. It doesn't, so it isn't.
Healthcare operations work, beyond just this automation
This automation connects to a broader pattern in the healthcare operations work I do. Separately, I've also worked an ongoing virtual assistant role covering operations and clinical support for a healthcare practice — a different engagement, but the same underlying requirement: healthcare operations can't tolerate the kind of dropped handoff that's routine in less regulated businesses.
Whether the fix is an automation layer or a dependable person doing the work directly depends on what the task actually is. What doesn't change is the standard: information has to stay accurate and current, because in a healthcare setting, close enough isn't actually close enough.