Make vs Zapier: Which One in 2026?

Medical practices do not buy Make or Zapier to replace an EHR. They buy a way to move an appointment, a refill, or a follow-up out of a spreadsheet without waiting on the EHR vendor's next interface ticket. Both products will connect a calendar to a message and a form to a row. They differ on branching, how an operations budget is consumed, where PHI is allowed to land, and who is awake when a scenario fails at 7 a.m. Neither Make nor Zapier publishes a list price we can print, so this page compares the jobs, the criteria, and the cutover, then tells you which quote packet to request.

TL;DR: Choose Make when the clinic job has routers, aggregators, and more than a couple of paths (refill that splits by payer, recall that splits by chronic condition, intake that loops until the packet is complete). Choose Zapier when the job is a short, linear trigger-to-action chain that a front-desk lead can keep alive without a scenario map. Ask both vendors, in writing, whether the quoted tier includes a business associate agreement, which apps are allowed to touch PHI, how failed runs are retried, and what happens to history if you leave. Treat any number that is not on that quote as not published.

How we evaluated

The method is criteria first, because a "vs" page that starts with a mascot is not a decision a partner can defend. We scored Make and Zapier on six clinic-owned jobs: appointment reminders, incomplete-intake chase, chronic-care follow-up, refill windows, eligibility or claim-status pings, and after-visit reputation or survey sends. For each job we asked whether the product can branch, whether it can loop, whether a non-engineer can read the run log, and whether a BAA is even on the quote.

Price is a fail for both names. Make and Zapier are not in the vendor store we can print from, so every price cell on this page is quote only or not published. "Around," "typically," and "starts at" are prices; they are not used here. What usually drives the number you will be quoted is operations or tasks, the number of seats who can edit scenarios, premium app connectors, and whether a HIPAA / BAA path is in the same packet.

The industry numbers we do print are the reason the connector exists. Clinic volume is not a hobby project: according to CDC, 85.2% of U.S. adults had a visit with a doctor or other health professional in 2024, and according to CMS, physician and clinical services spending reached $1,109.7 billion in 2024 inside a $5.3 trillion national health bill. A connector that drops 2% of reminder runs is not a small miss against that volume.

Physician time is the other constraint. according to American Medical Association, 43.2% of physicians reported at least one burnout symptom in 2024, and 45.1% reported a great deal of job stress, with more than one-third still pointing at EHR in-basket and after-hours documentation. A Make or Zapier build that creates a second inbox for the physician fails the evaluation even if the zap is "working."

The six criteria that actually change a Make vs Zapier call

These six lines are the meeting agenda. If a demo cannot answer them, you do not have a comparison.

Product-scope cells are positioning, not prices. BAA and list price are quote only for both names.

Specialty mix changes which of those criteria bite. according to American Medical Association, family medicine still reported 46.4% burnout in 2024 and emergency medicine 52.2%, which is why a primary-care inbox cannot absorb a connector that dumps exceptions onto the physician.

Source: AMA, Which physician specialties are seeing a drop in burnout? and AMA, U.S. physician burnout hits lowest rate since COVID-19.

43.2% of physicians reported burnout in 2024. Family medicine burnout sat at 46.4%. National health spending hit $5.3 trillion. Those three figures are why a connector is a workflow purchase, not a hobby zap.

Who Make is for in a medical practice

Make is for the operations lead who can draw the clinic job as a map: a refill request that splits by payer, a recall that splits by chronic condition, an intake form that must loop until ID, insurance, and consent are present. The visual scenario, the router, and the aggregator are the product. If your jobs look like that, Make is the closer fit even if the front desk finds Zapier friendlier on day one.

Who it is not for: a practice whose only live job is "new appointment, send one SMS," with no branching and no one who will own a scenario map when the builder leaves. That team will silently turn Make off and go back to the spreadsheet.

Pricing is not published. Ask for a quote that states operations volume, how many people can edit scenarios, whether the HIPAA / BAA path is in the same packet, which data stores are allowed for PHI, and how long run history is retained if you leave. Operations, not a public sticker, is what will move the number.

The refill window is the Make-shaped job. A prescription that is due, not filled, and then reversed by the payer is three different paths. Prescription Refill Automation Automation: 80% Refills 2026 is the clinic playbook; Make is the connector that can hold those branches without three separate zaps that drift. US Tech Automations can watch the fill event and reopen the refill task if the claim reverses, which is the step a linear zap usually drops.

Who Zapier is for in a medical practice

Zapier is for the practice that has ten short, linear jobs and a front-desk lead who will keep them alive: appointment booked, send reminder; visit complete, send survey; form submitted, create a row. The native app directory is the reason teams shortlist it. If your EHR, SMS vendor, and sheet already have first-class Zapier apps, the first three jobs will go live faster than a Make scenario a contractor has to draw.

Who it is not for: a practice whose jobs are long-running, looping, or heavily branched, or whose PHI cannot sit in the apps the zap would touch. A linear zap that fans a chronic-care roster into 400 one-off messages without aggregation will burn the operations budget and the staff who have to read the error pile.

Pricing is not published. Ask for a quote that states task volume, whether multi-step zaps and premium apps are in the same line, whether a BAA is available on that tier, which apps are in the HIPAA boundary, and how failed tasks retry. Seats who can edit zaps, and whether you need a dedicated environment for PHI, are the other levers.

The reminder job is the Zapier-shaped job. Cut Patient No-Shows: 5-Step Reminder Automation [Guide] is a short chain: slot booked, reminder at T-48 and T-2, confirm or cancel, put the slot back. Zapier will do that if the calendar and SMS apps are in the directory. US Tech Automations can fan the same schedule object into SMS and portal without a second zap when the EHR already emits the appointment event.

Connector shape, BAA, and operations compared

The comparison is not "which logo has more apps." It is which shape matches the clinic job, and whether PHI is even allowed on the quoted tier.

Administrative minutes are why these jobs exist at all. according to CAQH, the 2024 Index tracks $90 billion of medical and dental administrative-transaction spend against a $20 billion savings opportunity, and a manual prior authorization still takes 24 minutes while a manual eligibility check still takes 16 minutes.

Source: 2024 CAQH Index Report.

A Make or Zapier scenario that pings eligibility is buying back some of those 16 minutes. It is not an EHR, and it is not a clearinghouse. If the clinic's certified chart already does the 270/271, do not rebuild it in a connector; according to ONC, 91% of office-based physicians already used a certified EHR in 2024, so the connector should subscribe to that chart, not impersonate it.

Sources: CMS NHE Fact Sheet; CDC FastStats; ONC EHR adoption; AMA Organizational Biopsy; 2024 CAQH Index.

Strengths and limits of each connector

Make

Pros:

• Routers, aggregators, and iterators match refill, recall, and incomplete-intake jobs that are not one path.

• HTTP modules cover EHR or SMS gaps when a native app is missing.

• Scenario maps are reviewable in a partner meeting in a way a pile of one-step zaps is not.

Cons:

• Quote only; operations volume, editors, and the BAA path drive the number, and none of it is printed.

• A front-desk lead who will not own a scenario map will not keep Make alive after the contractor leaves.

• Easy to over-build: a 40-module scenario that one person understands is a staffing risk.

Zapier

Pros:

• Native app directory and linear zaps get the first three clinic jobs live without a map.

• Zap history is readable by a non-engineer if the zap is short.

• Staff who already use Zapier in another business will not need a new mental model.

Cons:

• Quote only; tasks, premium apps, seats, and the BAA path are negotiated, not listed here.

• Long-running loops and heavy branching turn into many zaps that drift.

• PHI scope is easy to get wrong if someone connects a personal Gmail or an unsanctioned sheet.

What swapping a connector platform actually costs

The cost of leaving Make for Zapier, or the reverse, is not a license line we can print. It is the rebuild of every scenario, the re-authorization of every app, the re-test of every PHI path, and the week the front desk runs both.

Data. There is no full "patient chart" to migrate. There are run histories, stored files, data stores, and the mapping of external IDs (EHR appointment IDs, SMS thread IDs). Export what you need for audit before you cancel the tenant. If PHI lived in a Make data store or a Zapier table, that store has to be emptied under the BAA, not screenshotted into a shared drive.

Retraining. Make users think in scenarios and routers. Zapier users think in zaps and steps. Budget a week for the person who owns the live jobs to rebuild the three highest-volume paths, not a lunch-and-learn. Write down which login is allowed to hold PHI.

The month. Dual-run the reminder and the refill jobs until a full clinic week has passed without a missed send. Keep the old platform read-only for history. Do not cut over on a Monday that also has a payer file due.

Failed runs. Decide who gets the 7 a.m. error: operations, front desk, or a queue US Tech Automations can sit on. A connector with no owner for failures is not cheaper; it is silent.

Verdict: which connector for which clinic job

If the jobs you can list on a whiteboard are branched, looping, or need aggregation, Make is the closer fit; request a quote that names operations, editors, BAA, and PHI-allowed apps. If the jobs are short, linear, and already sit in Zapier's app directory, Zapier is the closer fit; request a quote that names tasks, premium apps, BAA, and retry behavior. They are close on the first reminder zap and far apart on a refill-by-payer map. A verdict that says "either is fine" is not a verdict a partner can take into a meeting.

Get the quote in writing. If you want a second set of eyes on the three live jobs before you pick a connector, US Tech Automations publishes workflow pricing at https://ustechautomations.com/pricing.

FAQs

Does Make or Zapier replace our EHR?

No. Both are connectors. The 91% certified-EHR figure in the tables above is the reason the connector should subscribe to that chart, not try to be it.

Can we run PHI through either product?

Only if the quoted tier includes a business associate agreement and the apps in the scenario are inside that boundary. Ask for that in the same packet as the quote. A personal Gmail step is a no.

Which one is cheaper?

Not published. Neither vendor is in the store we can print from. Compare operations or tasks, editors, premium connectors, and the BAA line on two written quotes. The first vendor that will not fill those four lines is not cheaper.

What should we automate first?

The reminder chain if no-shows are the pain, the refill window if pharmacy reversals are the pain, and incomplete intake if packets arrive empty. Do not start with a 40-step scenario. Start with one job that has an owner for failures.

How long does a swap between Make and Zapier take?

Plan a dual-run through one full clinic week for the three highest-volume jobs, plus time to re-authorize apps and empty any PHI store. History does not magically appear in the new tenant.

Who should own failed runs?

Name a person before go-live. Front desk can own reminder failures. Billing can own eligibility pings. Physicians should not own the error inbox; the AMA burnout figures above are the reason.

Key Takeaways

• Make is the closer fit for branched, looping clinic jobs; Zapier is the closer fit for short linear zaps with native apps.

• Neither publishes a list price; quote only, and put BAA, PHI-allowed apps, and retry behavior on the same page as volume.

• 43.2% of physicians reported burnout in 2024, so do not dump connector exceptions onto the physician in-basket.

• Manual eligibility still takes 16 minutes and prior authorization 24 minutes in the 2024 CAQH Index; ping those systems, do not rebuild them.

• Dual-run a clinic week, export run history, and name the human who gets the 7 a.m. failure.

• If the remaining gap is the queue between the connector and the chart, US Tech Automations is the workflow map, not a third connector logo.