Move clinician onboarding into CommCare access
Make one onboarding record the cue for the next access step, so invites do not depend on someone remembering later.
Trigger
New Page
Triggers when a new page is added to a Notion database.
Action
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.
Why this helps
A new clinician's onboarding can be complete while their CommCare invitation is still waiting in someone's mental queue.
- Reduce onboarding follow-up and repeated status checks.
- Make approval and access requirements explicit in one instruction.
- Keep onboarding progress easier to track from the Notion record.
Setup
Build it in a few focused steps.
- 1Connect Notion and CommCare to Notis once through the portal.
- 2Create an automation or ask Notis to invite approved clinicians from new onboarding records.
- 3Describe the readiness and invitation requirements in one plain-language instruction.
- 4Choose the Notion New Page trigger for the onboarding database and select a channel for run reports.
- 5Test with one approved onboarding record and verify the CommCare invitation.
Questions about this workflow
Can it decide which role to invite?
Describe the role and permission intent in the prompt; CommCare invitation permissions still apply.
Does a new page always cause an invite?
The prompt should tell Notis to create an invitation only when the onboarding record meets the specified readiness criteria.
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.