Keep processed document follow-up visible as work changes
When work changes in Notion, prompt a focused check of the documents processed by the workflow you rely on.
Trigger
All Page Events
Triggers when any Notion page is created or updated across the workspace.
Action
List Workflow Documents
Tool to retrieve a paginated list of documents processed by a workflow. use when you need to view documents after processing.
Why this helps
Document processing follow-up can drift away from the project pages where the work is being tracked.
- Tie a document status check to active workspace work.
- Make processed items easier to revisit.
- Receive a concise run report through your selected channel.
Setup
Build it in a few focused steps.
- 1Connect Notion and Nano nets to Notis once through the portal.
- 2Create an automation in the portal or ask Notis to list recent documents from the named Nano nets workflow when Notion pages change.
- 3Choose the Notion All Page Events trigger.
- 4Select a run-report channel and test with a relevant page update.
Questions about this workflow
Could this run often?
All Page Events is workspace-wide and can fire for many page changes. Use a narrower trigger when you only need a specific page or database.
Does it process new documents?
The available action lists documents already processed by a workflow.
When this happens · Trigger
Do this · Action
Supported Triggers and Actions
Notis builds workflows that link Notion to Nano nets. A trigger fires from one place; an action lands in another.
Notion triggers
Nano nets actions
Recurring trigger
Notis starts this workflow on a schedule, such as daily, weekly, or during business hours.
Create OCR Model
Tool to create a new ocr model. use when you need to initialize an ocr model before training.
Webhook trigger
Notis starts this workflow when an external tool or custom backend sends an HTTP request.
Delete OCR Model
Tool to delete an ocr model. use when you need to permanently remove a trained model by its id.
All Page Events
Triggers when any Notion page is created or updated across the workspace.
Get all OCR models
Tool to retrieve a paginated list of all ocr models. use when you need to inspect or manage existing ocr models. call after authentication to fetch your account's models.
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.
Get All Prediction Files
Tool to fetch all prediction files associated with a specific model. use when you need to list all inference requests after model processing is complete.
New Comment
Triggers when a new comment is added to a specified Notion block or page.
Get OCR Model Details
Tool to retrieve details of an ocr model. use when you need full metadata of a model by its id.
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.
Get OCR Training Images
Tool to retrieve training images for an ocr model. use when you need to page through images associated with a model before training or analysis.
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.
Get Workflows
Tool to retrieve a list of all workflows in your nanonets account. use when you need to inventory or inspect all configured workflows.
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.
List Workflow Documents
Tool to retrieve a paginated list of documents processed by a workflow. use when you need to view documents after processing.
Connect any two apps with Notis in the middle.
Notion and Nano nets, 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 Nano nets.