CommCare Integrations Overview
Need to connect CommCare to another system but not sure where to start? This page helps you pick the right approach, from a simple spreadsheet download to a live two-way sync, and links you to the setup guide for each.
Choose by what you want to do
Find the row that matches your goal, then open its guide. Direction shows whether data moves into CommCare, out of CommCare, or both ways.
Method | What it’s for | Direction | Speed and scale | Who sets it up |
|---|---|---|---|---|
Submit forms or create and update cases from another system | ← In | On demand or automated | Developer | |
Download form or case data as a spreadsheet (Excel or CSV) | Out → | On demand, one-off | Anyone, no code | |
Live dashboards in Power BI, Tableau, or Excel | Auto-refreshed | Low-code | ||
Load data into a reporting database or data warehouse | Scheduled, large datasets | Technical or developer | ||
Automatically send new or changed forms and cases to another system | On change, near real time | Technical or developer | ||
Connect apps through a no-code platform (OpenFn, Power Automate, Zapier) | ← Both → | Near real time | Low-code | |
Build a custom, two-way integration in code | Flexible | Developer | ||
Open another app on the device (scanner, dialer, maps) and return a result, works offline | On device | Real time | Configured in the form |
Quick picks
I want a report or dashboard. One-off: Standard Export. Live and refreshed: OData Feeds.
I need large or scheduled loads into a database. Use the Data Export Tool (DET).
I want to push each new record out automatically. Use Data Forwarding.
I want to bring data into CommCare from another app. No code: a Third-Party Tool. In code: the Form Submission API.
Two systems must stay in sync. No code: a Third-Party Tool. Custom: CommCare APIs with a developer.
A form needs to open another app on the phone. Use an Android App Callout.
Before you build: a few things to decide
Direction. Into CommCare, out of CommCare, or both. Two-way integrations also need rules for matching records, resolving conflicts, and deciding the source of truth.
Speed and scale. Downloaded on demand, refreshed on a schedule, pushed when a record changes, or exchanged in near real time. The right option depends on data volume and how quickly people need updates.
Who owns it. Can your team configure and support it, or will you need a developer? For lower-code options, look at Power Automate, OpenFn, or Zapier. For advanced workflows (custom API calls, authentication, retries, monitoring, data transformation), plan for a developer using API Access and Data Forwarding.
Looking for hands-on support?