See what a significant plan edit changes
When a Notion page's content changes, ask Entelligence to assess the implications and surface questions that still need an answer.
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
Interact with the repository agent
Send a question and related information to the repository agent and receive a streaming response
Why this helps
Important changes buried in a page can be hard to recognize after several rounds of editing.
- Get a fresh view of evolving plans without rereading every detail.
- Identify implications and unresolved questions after an edit.
- Make it easier to keep your next decision aligned with current thinking.
Setup
Build it in a few focused steps.
- 1Connect Notion and Entelligence to Notis once through the portal.
- 2Create an automation in the portal, or ask Notis to have Entelligence review relevant Notion content edits.
- 3Describe in one plain-language instruction the kinds of implications or open questions to identify.
- 4Choose the Notion Page Content Updated trigger and a channel for run reports.
- 5Test with one real plan edit and check whether the analysis is useful.
Questions about this workflow
Can I limit the trigger to a particular page or data source?
The trigger supports optional page, parent page, or data source scope. Select the relevant scope when choosing the trigger.
Does the review compare every revision?
The automation passes available event context for Entelligence to analyze. Describe the comparison or review you want in the prompt.
When this happens · Trigger
Do this · Action
Supported Triggers and Actions
Notis builds workflows that link Notion to Entelligence. A trigger fires from one place; an action lands in another.
Notion triggers
Entelligence actions
Recurring trigger
Notis starts this workflow on a schedule, such as daily, weekly, or during business hours.
Add a new repository
Add a new repository to the system with specified details
Webhook trigger
Notis starts this workflow when an external tool or custom backend sends an HTTP request.
Interact with the repository agent
Send a question and related information to the repository agent and receive a streaming response
All Page Events
Triggers when any Notion page is created or updated across the workspace.
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 Entelligence, 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 Entelligence.