n8n, Power Automate, Zapier or custom code for a clinic?
Which of Zapier, Power Automate, n8n or custom code suits patient data, who offers a BAA (vendor contract), how each is billed, and when to code.

Maulik Joshi
Full-Stack Developer
Written for clinic owners and managers who want to automate jobs like appointment reminders and are unsure which tool to pick. Some of these tools will not sign a contract about protecting patient information, so the easiest option may not be one you can use. When you finish, you will be able to sort each job by how much patient information it touches and shortlist the tool, or custom code, that fits.
Pick by what the workflow touches. If it carries patient information, your choice narrows to a vendor that will sign a Business Associate Agreement (BAA), which is a contract where the vendor agrees to protect that information for you, or to a server you control. Zapier says patient health data is not supported on its platform and that it does not sign a BAA, so it suits flows with no patient information. Power Automate suits a clinic already on Microsoft, whose BAA covers the service. n8n, an automation tool you can run on your own server, suits a team with someone technical to run it; it states no BAA, so self-hosting moves the responsibility to you. Custom code, meaning software written for your clinic, wins when a flow writes to a record, moves money or needs an audit trail (a record of what ran, on which input and who approved it) that you must keep.
I build custom healthcare software, so I have a stake in that last answer, and I have tried to say where it loses. This guide rests on each vendor's own documentation, checked on November 22, 2026, and not on a head-to-head build (the same flow built in each tool), so it reports no benchmarks. It compares these four options only, so other tools such as Make are not covered. It is not legal advice, and whether a workflow may handle patient information is a decision for your compliance adviser.
#Sort the workflow by what it touches
Before comparing tools, list the flows you want and put each in one of three groups. The first group carries no patient information: supplier invoices, staff rota changes, an alert that a website form arrived. The second links a named patient to a visit: reminders, confirmations, intake links. The third carries clinical content or moves money: results, referrals, claims, payments.
The first group can go on almost any tool. I would treat the second as patient data until your compliance adviser says otherwise, which limits the choice to a vendor that will put its terms in writing or a server you control. For the third, I would plan on custom code, or a tightly reviewed build, from the start. The vendor statements further down are the reason.
#What a clinic workflow needs
A workflow that works in a demo can still fail in a clinic. Five things separate the two, and each is a question to put to any tool or any developer.
- A trigger you can trust. Where does the event come from (a form, a mailbox, a webhook from the booking system), and what happens when the same event arrives twice? Retries are normal, so any step that creates something has to survive running twice.
- Data handling. Which steps see patient details, where those details sit while the workflow runs, and who can open the run history.
- A failure alert. When a step fails at 2 a.m., who is told, and does the patient still get the reminder? A flow that fails silently is worse than no flow.
- An approval step. Anything a person must check before it goes out or gets written to a record needs a pause, a named approver and a time limit.
- An audit trail. What ran, on which input, who approved it and when, kept for as long as your adviser says you need it, which may be longer than the tool keeps it.
#The four options side by side
The table draws on each vendor's own documentation and pricing pages as of November 22, 2026. Plans and prices change, so confirm on the vendor's page before you budget.
| Question | Zapier | Power Automate | n8n | Custom code |
|---|---|---|---|---|
| Where the data runs | Zapier's cloud | Microsoft's cloud | n8n Cloud (hosted data is stored in Frankfurt, Germany, per the pricing page) or a server you run | Wherever you host it |
| Business associate agreement (BAA) | Zapier says it does not offer one | Microsoft offers a HIPAA BAA that lists the Power Automate cloud service in scope | Not stated on n8n's pricing or trust pages; a forum reply says none is offered | Your agreement is with the hosting provider, for example AWS |
| What you pay for | Tasks per month, by plan tier | A per-user license, or capacity assigned to a flow | Executions per month on Cloud; the Community edition is free to self-host | Build, hosting and upkeep |
| Run history kept by default | 29 to 69 days | 30 days | Self-hosted default: pruned after 14 days or above 10,000 executions | Whatever you design |
| Approval step | Human in the Loop, a paid premium app; reviewers need Zapier accounts | Start and wait for an approval action; needs a Dataverse database | Wait node that resumes on a form submission or a webhook call | You build it, including who may approve |
Two rows deserve a closer look. The BAA row is where comparison pages go stale fastest, so get the agreement in writing before patient data goes anywhere. The run history row matters because history is often the closest thing a no-code tool gives you to an audit trail, and it is shorter than most clinics expect.
#What each vendor says about patient data
These are the vendors' statements as of November 22, 2026, and a reading of them. A BAA is a contract between you and the vendor. Whether a vendor's terms are enough for your clinic is a question for a qualified compliance professional.
#Zapier
Zapier's Enterprise Agreement FAQ, dated July 1, 2024, answers directly: "Zapier hasn't undergone the HIPAA certification process, and we therefore don't offer a BAA." Its data privacy page says use of regulated healthcare data, including protected health information (PHI) under HIPAA, "isn't supported on Zapier", and its own blog answers "No, Zapier isn't HIPAA compliant." That settles it for anything linked to a patient. Zapier remains a fair choice for the first group of flows, the ones with no patient information.
#Power Automate
Microsoft's HIPAA page lists the Power Automate cloud service as in scope for its Business Associate Agreement, whether bought alone or included in an Office 365 or Dynamics 365 plan. It says the agreement is available through the Online Services Data Protection Addendum by default to customers that are covered entities or business associates. The same page states the limit: "using Microsoft services doesn't on its own achieve HIPAA compliance." The agreement covers Microsoft's service. A flow that passes data to a connector for a non-Microsoft service sends it to a vendor with its own terms, so each of those needs its own answer. Microsoft last updated the page on September 11, 2026.
#n8n and self-hosting
n8n's pricing page and trust center carry no HIPAA statement or BAA; the trust center names SOC 2 Type 2, SOC 3 and GDPR. A reply on n8n's community forum dated January 19, 2026 says: "Currently, n8n does not offer a Business Associate Agreement (BAA) for HIPAA compliance." I would treat that as the working answer and ask n8n in writing if your plan depends on it.
The alternative is to self-host. The data then sits on infrastructure you choose, and the agreement that matters is with your host. AWS, for example, presents a Business Associate Addendum in AWS Artifact and says PHI should only be processed, stored and transmitted in its HIPAA-eligible services. Everything above the host becomes your job: patching, access control, TLS, backups and logs. n8n's security documentation lists some of the switches, such as disabling the public API, rotating the encryption key and redacting execution input and output data. Its pricing page lists audit logging and execution data redaction under the Enterprise plan.
#Custom code
Custom code has no vendor BAA question of its own. It has the same hosting question and the same duties as self-hosted n8n. What changes is how much sits between your patient data and the outside world: you decide what is logged, how long it is kept and who can read it.
#Can a consultant build and run n8n flows for you?
n8n is free to self-host under its Sustainable Use License, which allows use "only for your own internal business purposes or for non-commercial or personal use." n8n's license FAQ spells out what that means for a clinic and for whoever builds the flows. A clinic running its own instance for its own workflows is inside it. A consultant may build, run and maintain workflows on their own instance for a client, as long as the client cannot create or edit them. Hosting n8n as a service in which clients build workflows, or white-labelling it, is not allowed.
If a developer offers to run your flows on their n8n server, ask whose instance it is and where the patient data will sit before any of it moves.
#How each one is billed
Each tool counts something different, and the difference shows once volume grows. Take a reminder flow with three counted steps (look up the appointment, send the message, write the reply back) that runs for 400 appointments a month. The figures below are arithmetic on the vendors' published rules, not a measurement.
- Zapier counts tasks. A standard step uses one task, while triggers and failed actions do not count, so this flow uses about 1,200 tasks a month. The Professional tier that starts at 750 tasks is $19.99 a month billed annually ($29.99 billed monthly), and the 2,000-task tier is $49.00 billed annually ($73.50 monthly).
- n8n Cloud counts executions, and an execution is one run of the whole workflow however many steps it has, so 400 appointments make 400 executions. Starter is 20 euros a month billed annually for 2,500 executions. The self-hosted Business plan is 667 euros a month billed annually for 40,000 executions.
- Power Automate sells licenses. Premium is $15.00 per user a month paid yearly. Cloud flows also have a daily action limit tied to the license, 40,000 requests per Premium user per 24 hours, and successful actions, failed actions and retries all count toward it. About 1,200 actions a month is far below that, so the license matters more than the count.
The free self-hosted Community edition of n8n has "almost the complete feature set", in n8n's words, but single sign-on, external secrets, log streaming, environments and Git version control need the self-hosted Business or Enterprise plans.
#What an appointment reminder flow looks like, step by step
I have not built this flow four ways, so there is no timing or cost result here. This is the structure and the places where each option makes it awkward.
- Trigger: an appointment arrives from the booking system by webhook, or a scheduled run asks for tomorrow's visits.
- Check: skip anything cancelled, already reminded or opted out. This step stops duplicates, so key it on the appointment ID.
- Send: a template message with the time and a way to confirm or cancel, and no clinical detail.
- Wait: pause for a reply, with a time limit.
- Write back: update the calendar and record the event in a store you control.
- Failure path: a failed step alerts a named person. In n8n that is an error workflow, started by the Error Trigger node, which runs only for automatic executions, so you test it by making a real run fail.
If the message goes out on WhatsApp, my guide to WhatsApp for clinics covers what Meta's terms say about health information and what belongs in a message. The pause for a person is where the tools differ most. In Zapier it is Human in the Loop, which needs a paid plan, needs reviewers to have Zapier accounts, and cannot sit inside or after a Looping step. In Power Automate, approvals are stored in Dataverse and an approver can answer from Outlook, Teams or the action center. In n8n the Wait node resumes on a form submission or a webhook call, so the approver's screen is something you build. In custom code you build all of it, including who is allowed to approve.
#When to stop using a no-code tool and write code
No-code is the right start for most clinic flows. These are the signals I would use to stop.
- The flow writes to the patient record or moves money. A duplicated or half-finished write costs more here than anywhere else. You want idempotent writes and a defined state for "half done".
- The audit trail has to outlast the tool. Run history lasts 29 to 69 days in Zapier, 30 days in Power Automate and 14 days by default on self-hosted n8n. If your adviser says records must outlive that, the trail has to be written to your own store anyway, and the tool is then only moving data.
- Approvals need real roles. Who may approve what, with a time limit and a record of the decision, is a permission model, and it belongs beside your user table and not in a shared flow editor.
- Changes need review. On the free n8n Community edition there is no built-in Git version control, so a clinic edits live flows with no review step.
- The bill follows steps. Per-task pricing grows with every step someone adds, so a flow that is cheap today gets a bigger bill when it gets longer.
A common outcome is a split: no-code for the first group of flows, custom code for the ones that touch records, money or patient messages. My healthcare workflow automation service covers the custom side.
#What I would not do
- Send patient-linked data through Zapier.
- Call self-hosted n8n compliant because it is self-hosted.
- Use default run history as the audit trail.
- Let a consultant run patient workflows on their own instance without a written agreement on where the data lives and who signs what.
- Choose a tool from a comparison page's BAA column without asking the vendor.
#Questions clinics ask
#Next step
If you are choosing between these for a specific flow, send the flow, the systems it touches and the countries you work in with an estimate request or through the contact page, and I will tell you what is feasible and what it is likely to cost. The HIPAA-aware development page and the clinics solutions page describe the wider software these flows sit inside. The approval gate demo in the AI Lab shows, with invented data, a send that is blocked until the exact text has been approved.
Last checked against each vendor's pages on November 22, 2026. Prices, plans and terms change; verify on the vendor's page before you decide.
#Sources
- Zapier, Enterprise Agreement FAQ (dated July 1, 2024), zapier.com/legal/enterprise-agreement-faq
- Zapier, Data Privacy Overview, zapier.com/help/data-privacy; Zapier blog, Is Zapier HIPAA compliant?, zapier.com/blog/is-zapier-hipaa-compliant
- Zapier, Pricing, zapier.com/pricing; help article, Customize data retention in Zapier; Human in the Loop help articles
- Microsoft Learn, HIPAA and HITECH Act offering (page updated September 11, 2026), learn.microsoft.com/compliance/regulatory/offering-hipaa-hitech
- Microsoft Learn, Requests limits and allocations and Limits of automated, scheduled, and instant flows (both dated November 10, 2026); Get started with Power Automate approvals; Power Automate pricing page
- n8n, Pricing, n8n.io/pricing; trust.n8n.io; community forum thread BAA Agreement for N8N cloud (reply of January 19, 2026)
- n8n docs: license FAQ, Community edition features, execution data pruning, securing n8n, error handling and the Wait node
- n8n, Sustainable Use License, github.com/n8n-io/n8n (LICENSE.md)
- AWS, HIPAA compliance page, aws.amazon.com/compliance/hipaa-compliance
Stay updated with new posts
Get notified when I publish new articles about web development, system design, and AI. No spam, unsubscribe anytime.
Related Articles
Can clinics use WhatsApp for appointments and reminders?
Yes for bookings and reminders, no for medical details. What clinics can and cannot do on WhatsApp, how patient consent works, and what it costs in 2026.
WhatsApp 24-hour window, templates and opt-in for clinics
When a clinic can message patients on WhatsApp: the 24-hour window, approved templates, recording consent and handling STOP. Meta's rules as of Nov 2026.