CommCare is a mobile data collection and case management platform for health and social programs
CommCare is a mobile data collection and case management platform for health and social programs On Nagent, CommCare is exposed as a fully-configurable forms & surveys integration that any agent can call — 6 actions, and API key authentication. No code is required to wire CommCare into your workflow — connect it once via the External Integrations panel and reuse it across every agent you build.
Agent builders use CommCare to automate the kinds of tasks forms & surveys teams previously handled manually. Concrete examples — each one is a single agent step in Nagent — include:
Every action and trigger is paired with a structured input/output schema (visible in the sections below), so when you wire CommCare into Helix — our agentic agent builder — the editor knows exactly what each step expects and produces. Configure once, deploy anywhere across your Nagent agents.
Every operation an agent can call against CommCare, with input parameters and output schema. Drop these into any step of an agent built in Helix.
COMMCARE_CREATE_LOOKUP_TABLETool to create a new lookup table in a CommCare domain. Use when you need to set up reference data structures like product catalogs, price lists, or configuration tables. Requires 'Edit Apps' permission.
Input parameters
The name/identifier of the lookup table. This is used to reference the table in applications.
The CommCare domain/project identifier where the lookup table will be created.
Array of field definitions for the lookup table. Each field must have a field_name and optional properties array.
Indicates whether the lookup table is accessible to all users in the domain. Defaults to false if not specified.
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
COMMCARE_CREATE_WEB_USER_INVITATIONTool to create an invitation for a new web user in CommCare. Use when you need to invite a user with specific role and permissions. Requires 'Edit Web Users & Edit Access API' permissions.
Input parameters
Role designation for the user (e.g., 'App Editor', 'Admin')
Email address of the user to invite
CommCare domain name where the invitation will be created
Profile to assign to the user
Custom data fields associated with the user
Tableau role (Explorer, ExplorerCanPublish, SiteAdministratorExplorer, Viewer, Unlicensed)
List of Tableau groups for user assignment
Location ID for primary assignment (must be in assigned locations)
List of location IDs the web user will access
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
COMMCARE_LIST_REPORTSTool to retrieve available reports configured in a CommCare project. Use when you need to discover what reports exist before downloading report data via the Download Report Data API.
Input parameters
The CommCare project identifier. This is the project space name where reports are configured.
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
COMMCARE_SINGLE_SIGN_ONTool to validate login credentials and retrieve user profile for a mobile worker or web user. Use when you need to authenticate a user and obtain their profile information including roles, permissions, locations, and configuration details.
Input parameters
The CommCare domain/project identifier where the user account exists.
The user's authentication password for login validation.
The user's login identifier (mobile worker or web user username).
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
COMMCARE_SUBMIT_FORM_ODK_COMPATIBLETool to submit form data using ODK-compatible endpoint for Android client compatibility. Use when submitting XForm data to CommCare. Requires properly formatted XML with metadata including unique instanceID.
Input parameters
The CommCare project domain name where the form will be submitted.
Complete XForm XML data as a string. Must include root <data> element with xmlns, name, and version attributes. Must contain an n1:meta node with required fields: deviceID, timeStart (ISO 8601), timeEnd (ISO 8601), username, userID (UUID), and instanceID (UUID4, must be unique).
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
COMMCARE_SUBMIT_FORM_TO_APPTool to submit an XForm to a specific CommCare application. Use when you need to submit form data and tag it with a specific application ID. The form is submitted as XML following the OpenRosa standard with required metadata fields.
Input parameters
The CommCare project domain/space where the form will be submitted.
Complete XForm XML content following OpenRosa standard. Must include root <data> element with xmlns, name, and version attributes. Must contain a <meta> section with required fields: deviceID, timeStart (ISO 8601 format), timeEnd (ISO 8601 format), username, userID, and instanceID (must be a unique UUID4 in format 'uuid:...' or just the UUID).
Application ID to tag the form submission with. This associates the submission with a specific CommCare application.
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
No publicly available marketplace agent is found using this tool yet. There are 49 agents privately built on Nagent that already use CommCare.
Build on Nagent
Connect CommCare to any Nagent agent in minutes — no API key management, no boilerplate. Just configure and deploy.
The five questions agent builders ask before adopting a new integration.
Open the External Integrations panel inside Nagent (app.nagent.ai/externalIntegration), find CommCare, and click "Connect Now." You'll authenticate with an API key — Nagent handles credential storage and refresh automatically. Once connected, CommCare is available to any agent in your workspace.
No. Nagent provides no-code integration for every tool. Once CommCare is connected, you configure its 6 actions directly in the agent builder UI — no API calls, no boilerplate, no schema management.
Helix — Nagent's agentic agent builder — lets you drop CommCare steps into any workflow visually. Pick an action (e.g., one of those listed above), fill in the inputs (Helix knows the required vs. optional schema for each parameter), and connect it to upstream/downstream steps. Triggers run as the entry point of an agent, so when a CommCare event fires, the agent kicks off automatically.
Every CommCare action and trigger ships with a fully-typed schema — input parameters with name, type, required flag, and description, plus the output payload shape. The schemas are documented in the sections above. Helix uses these schemas to validate your configuration at build time and to type-check the data flowing between steps.
Yes. While CommCare ships with 6 pre-built forms & surveys actions, you can layer custom logic around them inside Helix — pre/post-processing steps, conditional branches, retries, or stitching CommCare together with other connected tools. For deeper customization, talk to our team about Nagent's Agentic AI Lab — forward-deployed engineers who build CommCare-based workflows tailored to your business.