Review client form scans with less friction
Update a client page and have OCR.space extract text from its attached form scan for your next 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
OCR Parse Image
Tool to submit image or pdf to ocr.space for ocr processing.
Why this helps
Client forms can contain useful details in images that take extra time to inspect when preparing follow-up.
- Make form content easier to search during client follow-up.
- Spend less time reopening and scanning documents.
- Keep source text near the related client notes.
Setup
Build it in a few focused steps.
- 1Connect Notion and OCR.space to Notis once through the portal.
- 2Create an automation in the portal or ask Notis to read client form scans when their pages change.
- 3Write one plain-language instruction to OCR attached client form images or PDFs on relevant content updates and present the text for review.
- 4Select Notion Page Content Updated and choose the report channel.
- 5Test with one updated client page and confirm the result against its form.
Questions about this workflow
Does this process every updated Notion page?
The trigger can be scoped to one page, a data source, or a parent page. Describe the client context in the prompt.
Will it fill in client fields?
The OCR action extracts text; review it and handle any record updates according to your setup.
What if the document has personal information?
Only use documents and connections you are authorized to process, and review the OCR result before acting on it.
When this happens · Trigger
Do this · Action
Supported Triggers and Actions
Notis builds workflows that link Notion to Ocrspace. A trigger fires from one place; an action lands in another.
Notion triggers
Ocrspace actions
Recurring trigger
Notis starts this workflow on a schedule, such as daily, weekly, or during business hours.
OCR Parse Image
Tool to submit image or pdf to ocr.space for ocr processing.
Webhook trigger
Notis starts this workflow when an external tool or custom backend sends an HTTP request.
All Page Events
Triggers when any Notion page is created or updated across the workspace.
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 Ocrspace, 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 Ocrspace.