> For the complete documentation index, see [llms.txt](https://docs.coupler.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.coupler.io/sources/category/other/commcare.md).

# Commcare

CommCare is a mobile data collection platform used by NGOs, public health programs, and field teams to gather data via mobile forms and track cases over time. It's widely used in low-connectivity environments for community health, agriculture, and humanitarian programs.

Connecting CommCare to Coupler.io lets you move your field data into analytics tools automatically — no manual exports, no CSV uploads.

**Why connect CommCare to Coupler.io?**

* Pull form submissions and case records into Google Sheets, Excel, BigQuery, or Looker Studio for reporting
* Send field data to AI tools like ChatGPT, Claude, or Gemini for summarization or pattern detection
* Combine forms and cases using Join or Append transformations to build unified program datasets
* Set up scheduled refreshes so your dashboards always reflect the latest field activity

## Prerequisites

Before connecting, make sure you have:

* A CommCare HQ account with access to the project space you want to export
* Your CommCare **API key** (available in your CommCare HQ account settings)
* The **Project Space name** for the project you want to connect

{% hint style="info" %}
You need at least a Standard plan on CommCare HQ to access the API. The free Community plan does not include API access.
{% endhint %}

## Quick start

{% hint style="success" %}
Start with the **Cases** entity if you want a current view of people or program participants. Use **Forms** if you need the raw submission history or survey responses.
{% endhint %}

{% stepper %}
{% step %}
**Create a new data flow in Coupler.io.** Log in to Coupler.io, go to the Data Flows section, and click **Add data flow**. Search for CommCare and select it as your source.
{% endstep %}

{% step %}
**Enter your CommCare credentials.** You'll be asked for your CommCare username (email), API key, and Project Space name. To find your API key, log in to CommCare HQ, go to your profile settings, and look under **API Key**.
{% endstep %}

{% step %}
**Select an entity.** Choose either **Forms** or **Cases** depending on what data you need. You can add more entities in the same data flow later.
{% endstep %}

{% step %}
**Set a start date.** Use the date picker to set the earliest date for records you want to export. Only records created or modified after this date will be included.
{% endstep %}

{% step %}
**Choose a destination.** Select where you want your data to go — Google Sheets, Excel, BigQuery, Looker Studio, or an AI destination like ChatGPT or Claude.
{% endstep %}

{% step %}
**Run the data flow.** Click **Run** to execute your first manual sync. Check the preview to confirm your data looks correct.
{% endstep %}
{% endstepper %}

## Available entities

| Entity | Description                                                                                            |
| ------ | ------------------------------------------------------------------------------------------------------ |
| Forms  | Individual form submissions from mobile workers, including all field responses and submission metadata |
| Cases  | Tracked records for people, places, or things — with current status, properties, and history           |


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.coupler.io/sources/category/other/commcare.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.