Move legal intake documents toward review
Capture the intake page once and let document extraction become the next step.
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
Legal paperwork can sit in an intake queue while someone remembers to move it into a separate processing tool.
- Links legal intake capture with document processing.
- Makes it easier to surface information for a review session.
- Reduces manual handoffs when several matters are in progress.
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 for the setup in plain language.
- 3Tell Notis to start an Extracta ai extraction for the document attached to a new legal intake page.
- 4Select Page Created and scope it to the legal intake parent page or data source.
- 5Test with one real intake page and confirm the extraction starts.
Questions about this workflow
Can this support different legal document types?
Describe the relevant document types and desired extraction in the prompt, then validate with a representative document.
How do I keep the workflow focused?
Scope the Page Created trigger to the legal intake location that holds these pages.
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.