Move completed case follow-ups into CommCare
Let a clear status update signal that the case follow-up is ready for the next operational step.
Trigger
Page Properties Updated
Triggers when properties of a Notion page are updated. Customer optionally scopes with at most one of: - data_source_id: any row in this data source - page_id: this specific page - parent_page_id: any page whose immediate parent is this page With none set, fires for any property change in the workspace the integration has access to. Adding a column to a data source fires this trigger once per existing row. Customers can branch on `data.updated_properties` (array of property IDs) to filter downstream.
Action
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).
Why this helps
A completed follow-up can remain in a planning database while a separate CommCare submission is still waiting to happen.
- Reduce the mental load of remembering a second submission step.
- Make the handoff depend on the team's documented readiness status.
- Create a consistent path from follow-up work to CommCare.
Setup
Build it in a few focused steps.
- 1Connect Notion and CommCare to Notis once through the portal.
- 2Create an automation in the portal or ask Notis to submit completed case follow-ups to CommCare.
- 3Write a single plain-language instruction that defines a completed follow-up and the intended form submission.
- 4Choose the Notion Page Properties Updated trigger for the follow-up data source and select a report channel.
- 5Test with one completed follow-up and confirm the resulting form in CommCare.
Questions about this workflow
Can the workflow handle an incomplete follow-up?
The prompt should direct Notis to wait until the record meets your defined completion condition.
Does this update a CommCare case directly?
The listed action submits a form to CommCare; it does not provide a direct case-update action.
When this happens · Trigger
Do this · Action
Supported Triggers and Actions
Notis builds workflows that link Notion to CommCare. A trigger fires from one place; an action lands in another.
Notion triggers
CommCare actions
Recurring trigger
Notis starts this workflow on a schedule, such as daily, weekly, or during business hours.
Create Lookup Table
Tool 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.
Webhook trigger
Notis starts this workflow when an external tool or custom backend sends an HTTP request.
Create Web User Invitation
Tool 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.
All Page Events
Triggers when any Notion page is created or updated across the workspace.
List Reports
Tool 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.
Comment Created
Triggers when a new comment is created in Notion. Optional `page_id` filter scopes to comments on a specific page. When omitted, fires for any new comment in the workspace the integration has access to. Requires the 'Read comments' capability on the Notion integration. If a connection was authorized before that capability was enabled, the user must re-authorize the connection for comment events to flow.
Single Sign On
Tool 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.
New Comment
Triggers when a new comment is added to a specified Notion block or page.
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).
Database Created
Triggers when a new Notion database (the container) is created. A database is the post-2025-09-03 container that holds one or more data sources. This trigger fires for the container's creation event (`database.created`), distinct from `NOTION_DATASOURCE_CREATED` which fires when a new data source is added to an existing database. Most customers calling Notion's `POST /v1/databases` (the legacy API) or creating a database via the Notion UI will see this event. Adding a new data source to an existing database fires `data_source.created` instead — use `NOTION_DATASOURCE_CREATED` for that. Notion's payload puts `entity.type: "block"` (the container is a `child_database` block in the content tree) and `entity.id` is the database id.
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.
Data Source Created
Triggers when a new Notion data source is created. Fires workspace-wide. The payload's `data.parent` carries the data source's tree parent (typically the teamspace) for downstream filtering. A single template-based database creation can fire multiple `data_source.created` events at once — one per data source the template instantiates.
Data Source Schema Updated
Triggers when a Notion data source's schema is updated. Fires on column add / remove / rename. Payload includes `data.updated_properties: [{id, name, action}]` so consumers can discriminate the kind of change downstream. Optional `data_source_id` filter scopes to schema changes on a single data source. When omitted, fires for any schema change in the workspace the integration has access to. Note: adding a column also fires `page.properties_updated` once per existing row in the data source. Customers wanting a single structural-change signal should use this trigger.
Connect any two apps with Notis in the middle.
Notion and CommCare, or any other combination from 1,000+ integrations.
When this happens · Trigger
Do this · Action
Save your first hour today.
7-day trial of any paid plan, with 20$ of usage included.
No card. Works with personal or business CommCare.