Start month end with parsed results ready to review
A scheduled summary of selected Docparser results gives your monthly close or operations check a clear starting point.
Trigger
Recurring schedule
Notis starts this workflow on a schedule, such as daily, weekly, or during business hours.
Action
Get Multiple Document Results
Tool to retrieve parsed data from multiple documents processed by a specific parser. Use when you need to fetch results for multiple documents at once. Returns up to 100 results by default, with a maximum of 10000.
Why this helps
Month-end reviews become stressful when document details need to be gathered from several places at the last minute.
- Prepares document results before the review begins.
- Reduces last-minute searching across tools.
- Creates a repeatable starting point for monthly routines.
Setup
Build it in a few focused steps.
- 1Connect Docparser to Notis once.
- 2Create an automation through the portal or ask Notis to create it conversationally.
- 3In one instruction, ask Notis to retrieve and summarize results from the selected parser or parsers for month end.
- 4Set a monthly schedule near your review date and choose a channel for run reports.
- 5Test with one manual run and verify the chosen result scope.
Questions about this workflow
Can this retrieve results from several documents?
Yes. The action retrieves results for multiple documents processed by a specific parser.
Does the summary complete a monthly close?
No. It gathers parsed results to support your review.
When this happens · Trigger
Do this · Action
Supported Triggers and Actions
Notis builds workflows that link Notion to Docparser. A trigger fires from one place; an action lands in another.
Notion triggers
Docparser actions
Recurring trigger
Notis starts this workflow on a schedule, such as daily, weekly, or during business hours.
Get Multiple Document Results
Tool to retrieve parsed data from multiple documents processed by a specific parser. Use when you need to fetch results for multiple documents at once. Returns up to 100 results by default, with a maximum of 10000.
Webhook trigger
Notis starts this workflow when an external tool or custom backend sends an HTTP request.
Get Parser Models
Tool to retrieve all model layouts for a specific parser. Use when you need to list different layout configurations within a parser that help handle document variations.
All Page Events
Triggers when any Notion page is created or updated across the workspace.
List Parsers
Tool to retrieve all Document Parsers linked to your account. Use when you need to view available parsers or obtain parser IDs for subsequent operations.
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.
Ping API
Tool to test API authentication and connection health check for Docparser API. Use when you need to verify that API credentials are valid and the connection is working.
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 Docparser, 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 Docparser.