Retrieve the source document behind a changed record
A changed tracking record can prompt Notis to fetch its associated Aryn document, keeping source material close to the work being tracked.
Trigger
Page Properties Updated
Triggers when properties of a Notion page are 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 property change in the workspace the integration has access to. Adding a column to a data source fires this trigger once per existing row. Customers can branch on `data.updated_properties` (array of property IDs) to filter downstream.
Action
Get Document by ID
Tool to retrieve a document by id. use after both docset and document ids are available.
Why this helps
A status or detail change often requires checking the underlying document, which adds another manual lookup.
- Links record upkeep with source document access.
- Reduces manual searching when a tracked item changes.
- Supports review while the updated record is still in focus.
Setup
Build it in a few focused steps.
- 1Connect Notion and Aryn to Notis once through the portal.
- 2Create an automation in the portal or ask Notis conversationally to create one.
- 3Use one plain-language instruction to retrieve the Aryn document associated with a changed Notion record when both IDs are available.
- 4Choose the Notion Page Properties Updated trigger for the relevant data source and a channel for run reports.
- 5Test with a record that has a known Aryn docset and document ID.
Questions about this workflow
Can the action use a Notion record title to find the file?
The listed retrieval action is by document ID and requires the docset ID as well.
Can the trigger be scoped to a data source?
Yes. Page Properties Updated supports a data_source_id scope.
When this happens · Trigger
Do this · Action
Supported Triggers and Actions
Notis builds workflows that link Notion to Aryn. A trigger fires from one place; an action lands in another.
Notion triggers
Aryn actions
Recurring trigger
Notis starts this workflow on a schedule, such as daily, weekly, or during business hours.
Create DocSet
Tool to create a new docset. use when you need to allocate a storage container before adding documents.
Webhook trigger
Notis starts this workflow when an external tool or custom backend sends an HTTP request.
Create DocSet
Tool to create a new docset. use when you need to allocate a storage container before adding documents.
All Page Events
Triggers when any Notion page is created or updated across the workspace.
Delete DocSet
Tool to delete a docset and all its documents. use after confirming the docset id, when you need to permanently remove a docset and its contents.
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.
Generate plan
Tool to generate a query plan without executing it. use when you need to review the logical plan before running your query (e.g., "generate a plan for revenue breakdown by region").
New Comment
Triggers when a new comment is added to a specified Notion block or page.
Get DocSet Metadata
Tool to retrieve metadata for a specific docset. use when you have the docset id and optionally need usage statistics.
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.
Get Document by ID
Tool to retrieve a document by id. use after both docset and document ids are available.
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.
Get Document Binary
Tool to retrieve the binary content of a document by docset id and document id.
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.
List Async Tasks
Tool to list all outstanding asynchronous tasks for the account. use when you need to check pending or running tasks.
Connect any two apps with Notis in the middle.
Notion and Aryn, 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 Aryn.