Move receipt capture forward when you create a page
Create the receipt page in Notion, then let the extraction begin without another reminder to yourself.
Trigger
Page Created
Triggers when a new Notion page is created. Customer optionally scopes with at most one of: - data_source_id: new row in this data source - parent_page_id: new sub-page under this page (immediate parent only) With neither set, fires for any new page in the workspace the integration has access to. Notion sends ~60s aggregation latency on most events.
Action
Create Extraction
Tool to initiate a new document extraction process. use when you have prepared extraction details and need to start processing the document. returns a unique extraction id for tracking.
Why this helps
Receipts often pile up because capturing the expense requires remembering a separate follow-up step.
- Turns receipt capture into one connected action.
- Helps prevent forgotten expense documents from sitting untouched.
- Cuts down the time spent switching from Notion to a separate extraction tool.
Setup
Build it in a few focused steps.
- 1Connect Notion and Extracta ai to Notis once through the portal.
- 2Create an automation in the portal or ask Notis conversationally for a receipt workflow.
- 3Tell Notis to start a receipt extraction in Extracta ai when you create a Notion receipt page.
- 4Select the Notion Page Created trigger and choose where Notis should report runs.
- 5Try one real receipt page and check that the extraction appears in Extracta ai.
Questions about this workflow
Can this help with expense capture?
Yes. The workflow starts a receipt extraction when the selected Notion page is created.
What if the receipt is not attached or available?
The instruction should identify where the receipt document can be found, and the test should use a page with an accessible receipt.
When this happens · Trigger
Do this · Action
Supported Triggers and Actions
Notis builds workflows that link Notion to Extracta ai. A trigger fires from one place; an action lands in another.
Notion triggers
Extracta ai actions
Recurring trigger
Notis starts this workflow on a schedule, such as daily, weekly, or during business hours.
Create Extraction
Tool to initiate a new document extraction process. use when you have prepared extraction details and need to start processing the document. returns a unique extraction id for tracking.
Webhook trigger
Notis starts this workflow when an external tool or custom backend sends an HTTP request.
Delete Extraction
Tool to delete an extraction process. use after confirming the extraction id to remove. example: delete extraction with id '123e4567-e89b-12d3-a456-426614174000'.
All Page Events
Triggers when any Notion page is created or updated across the workspace.
View Extraction
Tool to retrieve details of an existing extraction process. use after starting an extraction to monitor its status and retrieve results.
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 Extracta ai, 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 Extracta ai.