ODK Zapier integrationAutomate ODK with Zapier.
The ODK Zapier integration gives you 1 trigger and 0 actions. Each new submission collected with your ODK forms can start a Zap that copies it to a sheet, a database or a team channel. Here is how that trigger works, what it costs and what to set before you go live.
Verified Trustpilot reviews · AI, automation & growth agency
What the ODK Zapier integration actually does
ODK is a form tool built for collecting data wherever the people filling the forms happen to be, including in the field. Connecting it to Zapier means each new submission stored in ODK Central can leave it automatically and reach the tools your team reads every day, without anyone downloading an export.
Everything starts from New Submission, and the value depends on where the record goes next. Three results are typical. A live sheet for the office: each submission becomes a row, and the project coordinator follows the survey without logging in to ODK. An alert when a form comes in: the team channel gets a message per submission, useful when a field visit needs a quick follow-up. A copy in your own database or CRM: the record is written where your reporting already lives, so nobody retypes it.
Now the limits. The trigger works by polling, so nothing is instant: Zapier checks ODK on a timer that depends on your plan. Each check downloads a set number of records, a setting you choose, and the choice matters (see the note below). There are no actions, so a Zap cannot create a form or edit a submission in ODK, and there is no search to look one up. The flow always runs one way, out of ODK.
Comparing platforms first? The n8n vs Zapier and Make vs Zapier comparisons set out the criteria (pricing model, hosting, step limits) without picking a winner for you.
Zapier vocabulary in one minute
Seven words are enough for the rest of this page. Each is explained here once, then used as is.
- Zap
- The automation you build: one trigger, then one or more actions that run every time that trigger event happens.
- Trigger
- The event that starts the Zap, here a new ODK submission. Once the Zap is on, Zapier keeps watching for it.
- Action
- What the Zap does after it starts: the step that writes, sends or moves something for you in another app.
- Task
- The unit Zapier bills. One task is one action that completes successfully; plan quotas are counted in tasks.
- Polling vs instant
- Polling means Zapier checks an app on a timer for new items. Instant means the app calls Zapier itself when something happens.
- Filter
- A step that lets the Zap carry on only when the incoming data meets the condition you set, and stops it otherwise.
- Search step
- A step that finds something already stored in an app so later steps can use it. ODK offers none on Zapier.
What it really costs in tasks
ODK is not a premium app, so it works on the free Zapier plan. You pay in tasks, and the ODK trigger never uses one.
- Free plan100 tasks per month
- Steps per Zap on Free2: one trigger, one action
- Premium appNo
- ODK trigger typePolling
Neither the trigger nor the checks Zapier runs to find new submissions cost anything, however often they happen. Only the action that follows counts, one task per success; a failed action is not counted. A Zap with three actions uses three times what a one-action Zap uses. The free plan gives you 100 tasks a month and unlimited Zaps, but two steps per Zap, and it checks ODK every 15 minutes. A filter (only submissions from one district, say) or a second action makes the Zap multi-step, which needs a paid plan. Paid plans also check more often, as the grid shows.
Connect your ODK account
- 01
Open your connections
In Zapier, go to the Apps page of your account and click + Add connection. A connection is your ODK account linked once, then reused by every Zap step that touches ODK.
- 02
Pick ODK
Search for ODK in the dialog, select it and click Add connection. A tab opens on the ODK side. You need an ODK account that can see the project and form whose submissions you want.
- 03
Sign in and grant access
Log in to ODK in that tab and let Zapier reach your account. When the tab closes, the connection shows in your list and the ODK trigger in any Zap can use it.
Your first Zap: copy each ODK submission to a sheet
GoalEvery new ODK submission becomes a row in a shared spreadsheet the office can follow.
- 01
Create the Zap
In the Zapier editor, start a brand new Zap. Pick ODK as the app and New Submission as the event that sets everything else off.
- 02
Set the trigger
Choose your connection, then the project, the form and the data table. Leave the number of records per run at 100, the default the ODK team recommends.
- 03
Test the trigger
Run the test. Zapier brings back the three most recent submissions of that form, so the mapping in the next steps is done on a real record.
- 04
Filter, then add the row
Optionally keep one area with a filter (a text rule for a text answer). Then add the sheet's row action and map each answer. The filter makes the Zap multi-step.
- 05
Test, then publish
Run each step once and read what came back. When the row looks right, click Publish to switch the Zap on. Only submissions made after that go through.
The ODK trigger
1 event starts a Zap when something happens in ODK. Zapier checks for them at the interval your plan allows.
New Submission
Polling triggerIn Zapier“Triggers when a new submission is created.”
Starts your Zap when a new record appears in the data table of an ODK form you pick. Every form has a Submissions table; if the form has repeat groups, you can point the trigger at the table of one of those repeats instead.
When the ODK Zap breaks
Zapier links no help article to ODK, and no rate limit is documented for it. Besides the records-per-run setting, what goes wrong is general Zapier behaviour applied to form data.
Four general Zapier behaviours apply to a setup like this one. Read them before you publish, and open the Zapier troubleshooting guide when something still fails.
Old submissions never come through
A Zap only reacts to records that arrive after it is switched on. Submissions already in ODK Central stay there; moving them is a separate, one-off job.A big sync gets held back
When a field team syncs many devices at once, or after a bulk upload, a sudden batch of records can be slowed by Zapier's flood protection.A record will not run twice
Zapier only processes records it has not downloaded before. A submission that already went through will not start the Zap again on the next check.The second step needs a paid plan
On the free plan a Zap holds one trigger and one action. A filter, a second action or a search makes it multi-step, and the editor asks for a paid plan.
Need help automating ODK with Zapier?
A person reads every message.
