- Home
- Resources
- Integrations
- myEZcare
myEZcare Zapier integrationAutomate myEZcare with Zapier.
myEZcare Zapier integration: 0 triggers, 1 action, 0 searches. myEZcare cannot start a Zap on its own, so another app does that part. Then Create Patient adds the person to your myEZcare account, as long as the five required fields arrive filled.
Verified Trustpilot reviews · AI, automation & growth agency
What the myEZcare Zapier integration actually does
It is a one-way bridge into myEZcare. myEZcare is software for businesses providing senior care, such as home health care, adult daycare and residential assisted living. On Zapier it offers a single step, Create Patient, which writes a new patient record from details another app hands over. Nothing goes the other way.
Three things you can get out of it, all through that one action. First, an intake form that fills itself into myEZcare: someone completes your form, and the patient exists in your account without anybody copying names across. Second, a spreadsheet that stops being a waiting room: each new row with a name, gender and date of birth turns into a patient record. Third, a contact list in another tool that feeds myEZcare directly, so the same person is not typed twice in two systems.
Now the limits, because they shape every Zap you build. myEZcare has no trigger on Zapier, so nothing that happens inside myEZcare can start a Zap: no new patient, no change, no alert. It has no search either, so a Zap cannot look up whether a patient is already there before creating one. And there is no action to update or remove a record. What you get is creation, and only creation.
That makes the choice of the first app the real decision. If you are still weighing tools, see our n8n vs Zapier comparison before you commit.
The Zapier words you need, in one minute
Eight terms come back on every Zapier screen. Here they are in plain English, so the rest of the page reads without a dictionary.
- Zap
- The automation you build on Zapier: one trigger, then one or more actions that run each time the trigger event happens.
- Trigger
- The event in an app that starts the Zap. Once the Zap is on, Zapier waits for it. With myEZcare, it always comes from another app.
- Action
- What the Zap does once started: the step that writes, sends or moves something for you. Create Patient is myEZcare's only one.
- Task
- The unit Zapier bills: one action your Zap completes successfully. The number on your plan is a count of those.
- Polling vs instant
- A polling trigger is checked on a timer for new items. An instant trigger is reported by the app itself the moment the event happens.
- Filter
- A step that lets the Zap go on only when what arrived meets the condition you set, and stops it otherwise.
- Connection
- Your account of an app linked to Zapier once, then reused by every step that uses that app.
- Multi-step Zap
- Any Zap beyond one trigger and one action. A second action or a filter makes it one, and it then needs a paid plan.
What a myEZcare Zap really costs
myEZcare is not a premium app, so it works from the free plan. The bill is counted in tasks, and only Create Patient can produce one here.
- Premium appNo, works on the free plan
- Tasks on the free plan100 per month
- Steps per Zap on the free plan2 (one trigger, one action)
- Cost of the trigger0 tasks
The trigger never costs a task, and neither does Zapier checking for new data. Each patient created successfully counts as one task; a run that fails is not counted. The free plan gives 100 tasks a month and unlimited Zaps, but each Zap stops at two steps: one trigger, one action. Add a filter or a second action and it becomes multi-step, which needs a paid plan. The interval grid below concerns the trigger of the other app, and only if that trigger is a polling one.
Connect myEZcare to Zapier in three steps
- 01
Open the Apps page
In your Zapier account, go to Apps and click + Add connection. A connection is made once, then every Zap that uses myEZcare reuses it, whatever app starts that Zap.
- 02
Find myEZcare and add it
Type myEZcare in the search box of the dialog, pick it from the results, then click Add connection. A new tab then opens so you can sign in to your myEZcare account.
- 03
Sign in and grant access
Sign in to myEZcare in that tab and grant Zapier access to the account. You need an account on the app, plus read or write access on anything you do not own yourself and want the Zap to touch.
Your first Zap: an intake form that becomes a patient
GoalEach new entry on your intake form creates the patient in myEZcare. Two steps only, so this Zap runs on the free plan.
- 01
Pick the trigger
Create a Zap and choose your form tool as the app that starts it, with its new-entry event. Connect the form account if it is not linked yet.
- 02
Test the trigger
Run the test. Zapier brings back the three most recent entries of the connected account, so you build the rest on a real one, not on a blank.
- 03
Add Create Patient
Choose myEZcare and Create Patient, then map the form answers into First Name, Last Name, Gender, Date of Birth and Source. All five are required.
- 04
Test, then publish
Test the action once and open myEZcare to read what came back. If the patient looks right, click Publish to switch the Zap on.
The myEZcare action
myEZcare gives you 1 action. For each one: what it does for you, when to reach for it, and what to watch out for.
Operations index
Create Patient
ActionIn Zapier“Creates a Patient”
Adds a new patient to your myEZcare account from details another app sends, so nobody retypes them by hand.
When a myEZcare Zap breaks
myEZcare has no help article of its own on Zapier, so the cases below are the general limits that apply to every Zap, seen through this one action.
Each of these cases has a clear fix once you know where to look. For a step-by-step method, see our Zapier troubleshooting guide.
Old records are not sent
A Zap only reacts to what happens after you switch it on. Patients already waiting in your form or sheet stay there; moving that backlog is a separate job.A Zap that sets itself off
A Zap that writes into the very place its own trigger watches can start again and again and burn through tasks. Keep the trigger and the destination apart.A big batch held back
When a trigger suddenly returns a huge batch, after a bulk import or a migration, Zapier's flood protection can hold it back.The same item, not twice
On a polling trigger, Zapier keeps track of what it has already seen, so the same item does not start the Zap twice.
Need help automating myEZcare with Zapier?
A person reads every message.



