Prepare bank statement cases with less tool switching
Open the analysis case in Notion and have Notis retrieve current Docsumo document options and user info before the file work begins.
Trigger
Page Created
Triggers when a new Notion page is created. Customer optionally scopes with at most one of: - data_source_id: new row in this data source - parent_page_id: new sub-page under this page (immediate parent only) With neither set, fires for any new page in the workspace the integration has access to. Notion sends ~60s aggregation latency on most events.
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
Case setup can become fragmented when the owner must leave Notion to check document availability and account details.
- Collects setup context at case creation.
- Reduces a separate Docsumo lookup during planning.
- Keeps the eventual analysis step distinct from category discovery.
Setup
Build it in a few focused steps.
- 1Connect Notion and Docsumo to Notis once.
- 2Create an automation and describe in plain language that a new bank statement case should retrieve Docsumo document types and user info.
- 3Choose Page Created and scope it to the case collection.
- 4Choose the run-report channel and test with one real case page.
Questions about this workflow
Does it calculate MCA metrics?
No. It retrieves available document types and user information. MCA Analysis is the separate action for processed bank statements.
Can it run for a particular case database?
Yes. Scope the Page Created trigger to the case data source.
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.