Skip to content
Notis

Turn new receipt pages into searchable text

Add a receipt to your Notion database and have OCR.space read the document, reducing manual transcription before expense review.

Trigger

New Page

Triggers when a new page is added to a Notion database.

Action

OCR Parse Image

Tool to submit image or pdf to ocr.space for ocr processing.

Why this helps

Typing receipt details takes attention away from the work of running the business and makes small expenses easy to overlook.

  • Reduce manual receipt transcription.
  • Make expense records easier to search and review.
  • Keep receipt processing close to the database where expenses are tracked.

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 tell Notis in plain language what it should do.
  • 3Use one instruction asking Notis to OCR the receipt image or PDF on each new expense page and make the extracted text available for review.
  • 4Select the Notion New Page trigger and choose where run reports should be sent.
  • 5Test with one real receipt page and confirm the extracted text is useful.

Questions about this workflow

What starts this workflow?

A new page in the Notion database where you track expenses.

What does OCR.space process?

The image or PDF associated with the page, when it is available to the automation.

Does OCR replace expense review?

No. It extracts text to help you review the receipt; verify important amounts and details against the original.

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.

TriggerScheduled

OCR Parse Image

Tool to submit image or pdf to ocr.space for ocr processing.

ActionInstant

Webhook trigger

Notis starts this workflow when an external tool or custom backend sends an HTTP request.

TriggerInstant

All Page Events

Triggers when any Notion page is created or updated across the workspace.

TriggerPolling

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.

TriggerInstant

New Comment

Triggers when a new comment is added to a specified Notion block or page.

TriggerPolling

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.

TriggerInstant

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.

TriggerInstant

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.

TriggerInstant

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.