Start contract table extraction after page edits
Update the contract context in Notion and let Extracta ai take on the table extraction step.
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
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
Contract details can be difficult to compare when key tables remain buried in documents and need manual retrieval.
- Starts table extraction in response to relevant page content edits.
- Helps turn contract documents into reviewable information sooner.
- Reduces the risk of an edited contract being overlooked in a manual queue.
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 tell Notis the desired result in plain language.
- 3Ask Notis to start an Extracta ai table extraction when the selected contract page content changes.
- 4Choose the Page Content Updated trigger and scope it to the relevant page if appropriate.
- 5Test by updating one contract page with an accessible document and check the extraction.
Questions about this workflow
Does every edit trigger the workflow?
Page content updates are aggregated over a short window; scope the trigger to the contract page when that fits your use.
Can I request tables specifically?
Yes. State in the prompt that the extraction should focus on tables in the contract document.
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.