Keep classification playbooks grounded in current options
Update the classification playbook in Notion and have Notis retrieve Docsumo's available document types and user info for a quick review.
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
Get User Document Types
Tool to list available user document types and user info. use when you need to discover all supported document classifications and user limits.
Why this helps
Procedural notes can drift from current tool availability, leaving the owner to remember a separate lookup.
- Makes playbook reviews more complete with little extra effort.
- Adds account-limit context where it may affect instructions.
- Reduces stale category references.
Setup
Build it in a few focused steps.
- 1Connect Notion and Docsumo to Notis once.
- 2Create an automation and describe that playbook content updates should retrieve Docsumo's available document types and user info.
- 3Choose Page Content Updated and scope it to the playbook page.
- 4Select a channel for run reports and test with one real content edit.
Questions about this workflow
Can I scope this to one playbook?
Yes. Select the Page Content Updated trigger and choose the specific page.
Does it update the playbook automatically?
No. It retrieves Docsumo's available types and user information for the owner to review.
When this happens · Trigger
Do this · Action
Supported Triggers and Actions
Notis builds workflows that link Notion to Docsumo. A trigger fires from one place; an action lands in another.
Notion triggers
Docsumo actions
Recurring trigger
Notis starts this workflow on a schedule, such as daily, weekly, or during business hours.
Get Enabled Document Types
Tool to retrieve enabled document types summary for the user.
Webhook trigger
Notis starts this workflow when an external tool or custom backend sends an HTTP request.
Get User Document Types
Tool to list available user document types and user info. use when you need to discover all supported document classifications and user limits.
All Page Events
Triggers when any Notion page is created or updated across the workspace.
MCA Analysis
Tool to perform merchant cash advance (mca) analysis on bank statements. use when you need a month-by-month breakdown of account credits, debits, and balances after documents are processed.
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.
New Comment
Triggers when a new comment is added to a specified Notion block or page.
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.
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 Docsumo, 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 Docsumo.