Keep meeting follow-ups beside the document
Bring a useful decision from updated Notion meeting notes to the Box document it affects, where the next person can act on it.
Trigger
Page Content Updated
Triggers when the body content of a Notion page is 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 page content edit in the workspace the integration has access to. Notion aggregates content edits within a short window (~60s typical).
Action
Create comment
Adds a comment by the user to a specific file, or as a reply to an other comment.
Why this helps
Meeting decisions can be easy to miss when they are stored far from the document that needs the follow-up.
- Keep document-specific decisions beside the file.
- Reduce context switching after meetings.
- Make it easier to resume work from the document itself.
Setup
Build it in a few focused steps.
- 1Connect Notion and Box to Notis once through the portal.
- 2Create an automation in the portal or tell Notis what you want in plain language.
- 3Ask Notis to add a document-specific meeting follow-up from the updated notes as a comment on the related Box file.
- 4Choose the Notion Page Content Updated trigger and a channel for run reports.
- 5Test with one updated meeting note that identifies its related Box file.
Questions about this workflow
Can this run only for one meeting notes page?
Yes. The Page Content Updated trigger supports a page scope.
Should every edit create a comment?
Describe which document-specific follow-ups warrant a Box comment in the plain-language instruction.
When this happens · Trigger
Do this · Action
Supported Triggers and Actions
Notis builds workflows that link Notion to Box. A trigger fires from one place; an action lands in another.
Notion triggers
Box actions
Recurring trigger
Notis starts this workflow on a schedule, such as daily, weekly, or during business hours.
Add classification to file
Adds a classification to a file by specifying the label of the classification to add. this api can also be called by including the enterprise id in the url explicitly, for example `/files/:id//enterprise 12345/securityclassification-6vmvochwuwo`.
Webhook trigger
Notis starts this workflow when an external tool or custom backend sends an HTTP request.
Add classification to folder
Adds a classification to a folder by specifying the label of the classification to add. this api can also be called by including the enterprise id in the url explicitly, for example `/folders/:id/enterprise 12345/securityclassification-6vmvochwuwo`.
All Page Events
Triggers when any Notion page is created or updated across the workspace.
Add domain to list of allowed collaboration domains
Creates a new entry in the list of allowed domains to allow collaboration for.
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.
Add initial classifications
When an enterprise does not yet have any classifications, this api call initializes the classification template with an initial set of classifications. if an enterprise already has a classification, the template will already exist and instead an api call should be made to add additional classifications.
New Comment
Triggers when a new comment is added to a specified Notion block or page.
Add or update user avatar
Adds or updates a user avatar.
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.
Add shared link to file
Adds a shared link to a file.
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.
Add shared link to folder
Adds a shared link to a folder.
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.
Add shared link to web link
Adds a shared link to a web link.
Connect any two apps with Notis in the middle.
Notion and Box, 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 Box.