Connect Box to CommCare

When something happens in Box, Notis takes the next step in CommCare. Describe what you want in plain English, or start from one of the examples below.

When this happens · Trigger

Do this · Action

Build an automation Browse examples

Examples

Ways Notis can move work from Box to CommCare

View example

Turn Box intake files into CommCare cases

When a new intake file lands in Box, prepare and submit a CommCare form using its contents and your provided form template.

View example

Submit CommCare updates from revised Box protocols

Use a new Box file version to prepare a CommCare form that records a protocol update, following your supplied form and review rules.

View example

Turn Box review comments into CommCare follow-ups

When a comment is added to a monitored Box file, use its contents to submit a CommCare follow-up form when it meets your stated criteria.

View example

Record completed Box sign requests in CommCare

When a Box Sign request changes status, submit a CommCare form for completed consent documents using your specified completion rules and XForm.

View example

Build CommCare lookup tables from Box reference files

When a new reference item appears in Box, use its content to create a CommCare lookup table when the data structure and domain rules are provided.

View example

Invite CommCare web users from Box onboarding rosters

When a roster file is added to Box, create CommCare web user invitations for eligible people when their email, role, and permissions are supplied and approved.

View example

Invite approved Box collaborators to CommCare

When a new collaboration is created on a monitored Box folder, create a CommCare web user invitation only when your supplied rules identify an eligible person and access level.

View example

Find available CommCare reports when Box requests arrive

When a monitored Box file changes, check its request details and list available CommCare reports for the reporting task it describes.

Supported Triggers and Actions

Notis builds workflows that link Box to CommCare. A trigger fires from one place; an action lands in another.

Box triggers

CommCare actions

Recurring trigger

Notis starts this workflow on a schedule, such as daily, weekly, or during business hours.

TriggerScheduled

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.

ActionInstant

Webhook trigger

Notis starts this workflow when an external tool or custom backend sends an HTTP request.

TriggerInstant

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.

ActionInstant

Collaboration Details Changed

Triggers when a collaboration's details change (e.g., role, status, expiration). This trigger monitors a specific collaboration and detects when any meaningful field changes, such as role, status, expiration date, access type, or acknowledgment status.

TriggerPolling

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.

ActionInstant

Comment Changed

Triggers when a comment's content or details change in Box. This trigger monitors a specific Box comment and detects when any meaningful field changes, such as message text edits, tagged message changes, or modification timestamp updates.

TriggerPolling

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.

ActionInstant

New File Comment Added

Triggers when a new comment is added to a file in Box. This trigger monitors a specific Box file and fires when new comments are detected.

TriggerPolling

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).

ActionInstant

File Metadata Changed

Triggers when a file's metadata or properties change in Box. This trigger monitors a specific Box file and fires when changes are detected in key fields like name, description, size, modification time, parent folder, or status.

TriggerPolling

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.

ActionInstant

File Shared Link Changed

Triggers when a file's shared link settings change in Box. This trigger monitors a specific Box file's shared link and fires when changes are detected in the shared link configuration, such as access level, permissions, password protection, expiration date, or vanity URL.

TriggerPolling

New File Version Uploaded

Triggers when a new file version is uploaded to a file in Box. This trigger monitors a specific Box file and fires when new versions are detected.

TriggerPolling

Trigger Types

Four ways to start an automation.

A trigger is the event that kicks a workflow off. Notis supports four kinds: an event in a connected app, an inbound webhook, a recurring schedule, and soon, your own database.

Integration triggers

Fire when something happens inside a connected app. New Notion page, Stripe charge, Linear issue: any of 1,000+ apps can start a workflow.

New Notion pageStripe chargeCalendar event

Webhook triggers

A unique URL per workflow. Anything that can send an HTTP POST can start an automation, including no-code tools that speak webhooks.

Any HTTP POSTCustom backendIoT event

Works with

ZapierPipedream

Most used

Recurring triggers

Cron-style schedules run a workflow on the clock. Daily standups, hourly syncs, business-hours-only digests: the workhorse of Notis.

Daily · 8:00HourlyWeekdays only

Coming soon

Database triggers

Watch a row, query, or threshold in your own database and fire the moment the data changes. Row inserted, value crosses a limit, query starts matching.

Row insertedValue > limitQuery match

Why AI automation

Classic automation breaks. AI adapts.

Same triggers and actions, smarter middle. AI handles the fuzziness that breaks traditional Zapier-style workflows the moment a field gets renamed.

Classic automationAI automation

Cost

$ · pay per run

$$ · AI models per run

Reliability

Breaks on schema change

Adapts to format changes

Setup

Click 8 dropdowns

Describe it in English

Handles fuzzy

Hard-coded fields only

Reads intent, summarises

Human in loop

Bolted on

Built in · approval inbox

Maintenance

You own every break

Self-heals · we own it

Ease of use

Describe it. Notis builds it.

Skip the visual builder. Tell Notis what you want, in plain English. It writes the workflow, you review and deploy.

You · in the Notis Builder

NEW

“When a row gets added to the Q4 OKRs Notion database and the status is Blocked, send a Telegram message to the owner with a summary of what's blocking, and ping me if there's no reply within 24 hours.”

Notis built this automation:

TriggerRow added to "Q4 OKRs"

Condition✦Status = "Blocked"

AI step✦Summarise the blocker in plain English

ActionDM the row owner with summary

Timeout✦No reply in 24h → ping you

Observability

Watch every run.

Notis Desktop is Mission Control for your AI automations. See every run, replay, edit, or rewind. Set approval gates so Notis pauses before destructive actions.