CommCare Zapier integrationAutomate CommCare with Zapier.
The CommCare Zapier integration listens to your field data and hands it to other tools. It offers 4 triggers, 0 actions and 0 searches: every trigger is instant, so a new case or a submitted form starts the Zap at once, even on the free plan.
Verified Trustpilot reviews · AI, automation & growth agency
What the CommCare Zapier integration really does
Connecting CommCare to Zapier means one thing: something that happens in CommCare becomes the starting signal for work in another app. A form comes back from the field, a case is opened, a case changes. Zapier picks that up and passes the details to the tool your office team already lives in.
Three results come up again and again. First, a live register: New Form Submission feeds every completed form into a spreadsheet, so a program manager reads the latest visits without exporting anything. Second, an alert for new people in your caseload: New Case tells a team channel or an inbox that someone was just registered. Third, a follow-up trail: Updated Case or New or Updated Case pushes each change on a case into a log, a CRM or a task list.
Now the honest part. This integration only reads. CommCare has no action in Zapier, so a Zap cannot create a case, edit one or submit a form for you. Data flows out of CommCare, never back in. If the plan was to send records from a website form into CommCare, Zapier will not do it with this app (and there is no search step either, so a Zap cannot look up an existing case).
The good news sits in the trigger type. All 4 triggers are instant, which matters a lot on a small budget: even on the free plan a new case or a submitted form reaches Zapier straight away. If you are weighing tools, the CommCare Make integration page covers the same app on another platform, and the Make vs Zapier comparison lays out the general differences.
Zapier vocabulary in one minute
Seven words do most of the work on this page. Each one is explained once, here, in plain terms.
- Zap
- The automation you build on Zapier: one trigger, then one or more actions that run each time that trigger event happens.
- Trigger
- The event that starts a Zap. With CommCare it is always a case or a form; once the Zap is on, Zapier waits for it.
- Action
- What the Zap does after it starts: write a row, send a message, create a record. CommCare offers none, so actions come from other apps.
- Task
- The unit Zapier bills: one action that completes successfully. Your plan's allowance is a count of those, nothing else.
- Polling vs instant trigger
- A polling trigger is checked on a timer. An instant trigger is reported by the app itself the moment the event happens. CommCare's are all instant.
- Filter
- A step placed after a CommCare trigger that lets the Zap go on only when a value meets your condition, and halts it otherwise.
- Connection
- Your CommCare account linked to Zapier once, then reused by every Zap and every step that needs CommCare.
What it actually costs
CommCare is not a premium app, so it works from the free plan. The trigger itself never costs a task, however many forms arrive.
- Premium appNo, available on the free plan
- Free plan100 tasks a month, two-step Zaps only
- Trigger cost0 tasks
- Trigger type4 instant, 0 polling
Only the actions after it count, and only when they succeed: a failed action is not billed. A Zap with three actions uses three tasks per form. The free plan gives 100 tasks a month and unlimited Zaps, but only two-step Zaps, one trigger and one action. Add a filter or a second action and it becomes a multi-step Zap, which needs a paid plan. Watching CommCare for new cases or forms costs nothing, however busy the field team gets.
Connect CommCare to Zapier in 3 steps
- 01
Open your connections
In Zapier, go to the Apps page of your account and click + Add connection. You need a CommCare account first, with access to the project data you want the Zap to watch.
- 02
Pick CommCare
Type CommCare into the search box of the dialog, select it, then click Add connection. A new tab then opens on the CommCare side so you can sign in there.
- 03
Sign in and allow access
Log in with your CommCare credentials and grant Zapier access to the account. The connection now appears in your list, ready for any Zap that starts from CommCare.
Your first Zap: field visits into a team sheet
GoalEach time a household visit form is submitted, add a row to a monitoring sheet, but only for visits where the question your form uses to flag a follow-up is answered yes.
- 01
Create the Zap
Start a new Zap and choose CommCare as the app that starts it. Pick New Form Submission as the event, then select your CommCare connection.
- 02
Point it at the right form
Fill the three required boxes: the Domain, the Application and the Form. Choose the household visit form itself, since the trigger watches the one form you pick.
- 03
Test the trigger
Run the test. Zapier brings back the three most recent submissions of that form, so you map fields on a real visit rather than a guess. Spot the answer that marks a follow-up.
- 04
Add the filter
From the plus icon, add a Filter step. Set the field you spotted in the test, the rule, and the value to compare. This makes the Zap multi-step, so it needs a paid plan.
- 05
Add the sheet action
Add Google Sheets with Create Spreadsheet Row and map each column to a value from the CommCare test. Test this step too and check the row really landed.
- 06
Publish
Click Publish to switch the Zap on. From now on, each matching submission adds a row the moment it reaches CommCare, and each row costs one task.
CommCare triggers in Zapier
4 events start a Zap when something happens in CommCare, and 4 of them are instant: the app calls Zapier straight away, whatever your plan.
New or Updated Case
Instant triggerIn Zapier“Triggers when a new case is created or an existing case is modified.”
This one catches both moments in a case's life: when it is first registered and every time someone changes it afterwards. One Zap, one stream covering the whole caseload.
New Case
Instant triggerIn Zapier“Triggers when a new case is created.”
Fires once per case, at creation, and ignores everything that happens to it later. A clean signal for "someone new just entered the program".
New Form Submission
Instant triggerIn Zapier“Triggers when a new form is submitted.”
Starts the Zap each time a chosen form is submitted, which makes it the most direct line from a mobile worker's screen to the office.
Updated Case
Instant triggerIn Zapier“Triggers when an existing case is modified.”
Reacts only when an existing case is modified. Brand-new cases? They do not set it off, which keeps the noise down when progress matters more to you than intake.
When it breaks
Zapier attaches no help article to CommCare and documents no limit of its own for this app. What can go wrong comes from how Zapier works in general.
Four situations explain most of the surprises. None of them is a bug; each one is a rule worth knowing before the first big sync.
Old cases are never picked up
A Zap reacts only to what happens after it is switched on. Cases and forms that existed before publishing stay where they are; moving that backlog is a separate job.A big sync gets held back
When a trigger suddenly returns a huge batch, after a bulk import or a migration, Zapier's flood protection can hold those items back instead of running them all.The filter step is refused
On the free plan a Zap has two steps only. Adding a filter between CommCare and the next app turns it into a multi-step Zap, and that needs a paid plan.Tasks run out faster than planned
Each successful action counts on its own. A Zap with three actions after New Form Submission uses three tasks per form, and the free plan stops at 100 a month.
Need help automating CommCare with Zapier?
A person reads every message.
