Keep document context during tracker changes
When you change a tracker structure, process its relevant scans so you can review the underlying records with less backtracking.
Trigger
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.
Action
OCR Parse Image
Tool to submit image or pdf to ocr.space for ocr processing.
Why this helps
A schema change can lead to cleanup work, and scanned records make that review slower when their contents are not searchable.
- Bring source text into a tracker maintenance session.
- Reduce manual document opening during cleanup.
- Keep migration review grounded in the source records.
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 relevant scanned records when a tracker schema changes.
- 3Write one plain-language instruction describing the document context and asking OCR.space to extract text for the schema review.
- 4Choose Notion Data Source Schema Updated and select a channel for run reports.
- 5Test during a planned schema change with one accessible source document.
Questions about this workflow
What causes this trigger to fire?
A column is added, removed, or renamed in a Notion data source.
Will every existing row be OCR processed automatically?
The trigger reports the schema change. Specify the relevant documents in the prompt and review what the automation processes.
When is this useful?
It can help when a tracker change includes a review of scanned source records.
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.