Read paperwork as new subpages arrive
Add an incoming document beneath a hub page and let OCR handle extracting its text.
Trigger
Page Added to Page
Fires when a new subpage (a `child_page` type block) is added under a specified parent Notion page.
Action
OCRWebService Recognize
Tool to call soap recognize operation. use when performing ocr on an image to retrieve text, output document, word coordinates, and errors.
Why this helps
Nested pages can be easy to overlook when you are moving between client or project workspaces.
- Gives new subpages a consistent processing step.
- Keeps client or project paperwork organized under its hub.
- Reduces the need to revisit pages just to check for scans.
Setup
Build it in a few focused steps.
- 1Connect Notion and Ocr web service to Notis once.
- 2Create an automation in the portal or ask Notis conversationally.
- 3In one instruction, ask Notis to OCR scan references on new subpages under the chosen hub.
- 4Choose Page Added to Page, name the parent page, and set the report channel.
- 5Test by adding one subpage with a real scan reference.
Questions about this workflow
Which subpages will start OCR?
This trigger watches new subpages under the parent page you specify.
Should I include a condition in the instruction?
Yes. Ask Notis to process only subpages that reference a scanned document or image.
When this happens · Trigger
Do this · Action
Supported Triggers and Actions
Notis builds workflows that link Notion to Ocr web service. A trigger fires from one place; an action lands in another.
Notion triggers
Ocr web service actions
Recurring trigger
Notis starts this workflow on a schedule, such as daily, weekly, or during business hours.
Get Account Credentials
Tool to extract ocrwebservice credentials. use when credentials need to be retrieved from connection metadata before invoking service operations.
Webhook trigger
Notis starts this workflow when an external tool or custom backend sends an HTTP request.
Get Account Information
Tool to retrieve current account details such as remaining pages, subscription plan, and expiration date. use when checking account status before submitting ocr jobs.
All Page Events
Triggers when any Notion page is created or updated across the workspace.
OCR Web Service Log
Tool to retrieve ocr processing logs. use after specifying date range for your account.
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.
OCRWebService Recognize
Tool to call soap recognize operation. use when performing ocr on an image to retrieve text, output document, word coordinates, and errors.
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 Ocr web service, 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 Ocr web service.