Find the thread in a busy discussion
Use a page-specific comment trigger to ask Entelligence what concerns or questions keep resurfacing in one important discussion.
Trigger
New Comment
Triggers when a new comment is added to a specified Notion block or page.
Action
Interact with the repository agent
Send a question and related information to the repository agent and receive a streaming response
Why this helps
Long comment threads can make it difficult to see whether people are raising the same underlying issue.
- Notice recurring themes without manually rereading a long thread.
- Bring unanswered questions into view.
- Focus analysis on the discussion attached to one selected page.
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 comments on a selected Notion page.
- 3Describe in one plain-language instruction the themes or unanswered questions you want surfaced.
- 4Choose the Notion New Comment trigger and specify the page or block to watch.
- 5Select a channel for run reports and test with one real comment.
Questions about this workflow
How does this differ from a workspace-wide comment trigger?
This New Comment trigger watches a specified Notion block or page, keeping the workflow focused on one discussion.
Can it identify repeated concerns over time?
The prompt can ask Entelligence to look for recurring themes using the context available for the event. For a broader trend view, provide the relevant context in the instruction.
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.