Queue a revised document for batch processing
Make a document revision the cue to submit an updated OCR task.
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
Submit Batch Any Document OCR Task
Tool to submit batch OCR processing tasks for various document types including bank statements, resumes, passports, delivery sheets, and more. Use when you need to asynchronously process documents with custom configurations. The task is processed asynchronously; use the Results Check API with the returned task ID to monitor status and retrieve results.
Why this helps
Revised files can be overlooked when reprocessing requires a separate step after editing their Notion record.
- Submit the revised document through the batch OCR task workflow.
- Keep a task ID in the run report for later result checks.
- Reduce the chance that document updates go unprocessed.
Setup
Build it in a few focused steps.
- 1Connect Notion and Eagle Doc to Notis once through the portal.
- 2Create an automation in the portal or ask Notis to build it in plain language.
- 3Tell Notis in one instruction to submit the revised document file for Eagle Doc batch OCR after a page content update and report the task ID.
- 4Choose Notion Page Content Updated, select a run-report channel, and test with one revised document.
Questions about this workflow
Are batch results returned in the same step?
The batch action is asynchronous. It returns a task ID, and the Results Check API is used later to check status and retrieve results.
What kind of update should trigger it?
Use the content update event for the page holding the document, and describe relevant revision context in the instruction.
When this happens · Trigger
Do this · Action
Supported Triggers and Actions
Notis builds workflows that link Notion to Eagle doc. A trigger fires from one place; an action lands in another.
Notion triggers
Eagle doc actions
Recurring trigger
Notis starts this workflow on a schedule, such as daily, weekly, or during business hours.
Process Any Document with OCR
Tool to process any document type with OCR and automatic classification. Supports bank statements, resumes, passports, delivery sheets, and more. Use when you need to extract structured data from various document types.
Webhook trigger
Notis starts this workflow when an external tool or custom backend sends an HTTP request.
Submit Batch Any Document OCR Task
Tool to submit batch OCR processing tasks for various document types including bank statements, resumes, passports, delivery sheets, and more. Use when you need to asynchronously process documents with custom configurations. The task is processed asynchronously; use the Results Check API with the returned task ID to monitor status and retrieve results.
All Page Events
Triggers when any Notion page is created or updated across the workspace.
Delete Batch Processing Task
Tool to delete a submitted batch processing task from the queue. Use when you need to cancel or remove a previously submitted batch OCR task before processing completes.
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.
Eagle Doc Invoice OCR from Base64
Tool to extract invoice data from base64 encoded images using Eagle Doc OCR API. Use when you need to process invoice images that are already base64 encoded. Supports optional parameters for privacy control, coordinate extraction, and full text extraction.
New Comment
Triggers when a new comment is added to a specified Notion block or page.
Get Management Quota
Tool to get contractual quota allowance and current usage counters for all workloads. Use when you need to check remaining capacity for dashboards or billing workflows.
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.
Receipt OCR V1 (Legacy)
Tool to process receipt images with v1 API to extract structured data. Use when you need to extract merchant details, line items, totals, and payment information from receipt images or PDFs. Note: This is a deprecated legacy version; consider using newer API versions if available.
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.
Receipt OCR V3
Tool to process receipt images into structured JSON with 40+ fields including merchant info, line items, taxes, and payments. Use when extracting detailed data from receipt images or PDFs.
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.
Get Receipt Quota V1
Tool to get quota information for receipt processing API v1 (deprecated). Use when you need to check remaining quota for receipt OCR processing.
Connect any two apps with Notis in the middle.
Notion and Eagle doc, 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 Eagle doc.