ceven

CommCare

Syncs mobile field data and case management records into your central database, automates user onboarding for field workers, and triggers alerts based on submitted health forms.

Try CommCare in Ceven

Ask Ceven anything
Standard

Why use Ceven?

  1. AI native CommCare integration

    • Describe the outcome and Ceven picks the right CommCare calls, fills the parameters, and checks the result.
    • Structured, agent friendly tool schemas so each call runs reliably instead of by guesswork.
    • Rich coverage for reading, writing, and querying your CommCare data, across all 6 of its actions.

  2. Managed auth

    • Built in OAuth with automatic token refresh and rotation.
    • One place to manage, scope, and revoke CommCare access.
    • Per user and per environment credentials instead of shared keys.

  3. Agent optimized design

    • Actions are tuned from real success and error rates so reliability climbs over time.
    • Full execution logs so you always know what ran in CommCare, when, and on whose behalf.
    • The agent pauses and asks when CommCare is unclear instead of plowing ahead.

  4. Enterprise grade security

    • Fine grained access so you control which agents and people can reach CommCare.
    • Least privilege by default, read scopes first and only the writes a workflow needs.
    • A full audit trail of every CommCare action to support review and sign off.

Supported tools

Every action Ceven's agents can run on CommCare, and when to use it.

Create lookup table
Use this when you need to set up reference data structures like product catalogs, price lists, or configuration tables in a domain.
Create web user invitation
Use this to invite a new user with specific roles and permissions to the web platform.
List reports
Pull a list of all available reports configured in a project to identify which data sets are available for download.
Single sign on
Validate login credentials and retrieve the full user profile including roles and permissions for a mobile worker.
Submit form
Push an XForm to CommCare using the OpenRosa standard including all required metadata like device ID and timestamps.
Submit ODK form
Submit form data using the ODK compatible endpoint to ensure compatibility with Android clients.
Get case details
Pull the current state and properties of a specific case by its unique case ID.
Update case property
Modify a specific property on an existing case to reflect a change in patient or client status.
Search cases
Query cases based on specific property values to find a cohort of patients or clients.
Delete lookup table
Remove an obsolete reference table from the domain to keep configuration clean.
Revoke user invitation
Cancel a pending web user invitation before it is accepted by the recipient.
Download report data
Pull the raw data from a specific report ID for analysis in a downstream tool.
Submit Form to CommCare
Tool to submit an XForm to CommCare following the OpenRosa standard. Use when you need to submit form data with complete XML including required metadata fields (deviceID, timeStart, timeEnd, username, userID, instanceID).
Submit Form ODK Compatible
Tool 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.

14 actions · scroll to see them all

Frequently asked questions

Ceven operates using the permissions assigned to the API key or user account connected to the platform. For instance, actions like creating lookup tables or inviting web users require the Edit Apps or Edit Web Users permissions within the CommCare domain. If the connected account lacks these specific rights, the agent will return a permission denied error. We recommend creating a dedicated service account with the minimum necessary permissions to perform your specific workflows. This ensures that the agent can perform its tasks without having full administrative control over your entire project architecture or sensitive user data.
Yes. When using the submit form actions, Ceven can include the specific username and device ID in the XML metadata. This allows the agent to simulate a submission from a specific mobile worker or to bridge data from another system into CommCare as if it came from a field device. You must ensure that the usernames used in the metadata exist within the CommCare project and have the appropriate permissions to submit that specific form, otherwise the CommCare server will reject the submission as unauthorized.
CommCare imposes strict rate limits on their API to ensure platform stability for all users. If a Ceven workflow attempts to update thousands of cases in a tight loop, you may encounter 429 too many requests errors. Ceven manages this by implementing an exponential backoff strategy, meaning the agent will automatically pause and retry the request. However, for massive data migrations, we recommend batching your updates or scheduling them during off peak hours to avoid hitting these limits and causing delays in your data synchronization pipelines.
Ceven interacts with the CommCare cloud server via API. While the CommCare mobile app handles the offline collection and local storage on the device, Ceven only sees the data once it has been synced from the device to the CommCare server. Once the data lands in the cloud, Ceven can trigger workflows based on those new submissions. If you need to trigger an action before a device syncs, that logic must reside within the CommCare app itself, as the cloud API cannot reach into a device that is currently offline.
The ODK compatible endpoint is designed specifically for clients that follow the Open Data Kit standard, which is common for many Android based data collection tools. While both endpoints eventually put data into your CommCare project, the ODK endpoint handles the XML envelope and metadata slightly differently to ensure maximum compatibility with third party mobile clients. Use the ODK action when you are pushing data from a non CommCare app and the standard OpenRosa submission is resulting in formatting errors or rejected packets.
Ceven cannot build the internal logic of your CommCare app, such as creating form fields or defining case management rules within the app builder. However, it can manage the data that those rules act upon. For example, while you build the logic in CommCare that says a patient needs a visit every thirty days, Ceven can be the tool that monitors the dates and creates a task or reminder in an external system when that window is missed. It acts as the bridge between the app logic and your operational tools.
All data transmitted between Ceven and CommCare is encrypted using TLS in transit. We use secure authentication methods as defined by Dimagi to ensure that only authorized agents can access your project data. We do not store your raw case data permanently in our own database; we treat it as transient context for the model to process the requested action. Once the workflow is complete and the data is pushed to your destination, the temporary session data is cleared according to our strict data retention and privacy policies.

Alternatives to CommCare

Other tools that solve a similar problem. Ceven supports these too, so you can switch or run more than one at once.

KoboToolbox logoKoboToolboxDHIS2 logoDHIS2ONA logoONASurveyCTO logoSurveyCTO

Try Ceven on your stack

Plug Ceven on top of the tools you already run. Connect CommCare and the rest of your stack, describe the outcome, and its agents handle the work end to end, days of it in minutes.

Get started for free