Resolve factual questions where the discussion happens
Turn a focused page discussion into a source-aware web check, so you can keep the conversation moving without opening a separate research session.
Trigger
New Comment
Triggers when a new comment is added to a specified Notion block or page.
Action
Octen Web Search
Real-time web search across the live internet, with filters, highlights, and full page content.
Why this helps
Small unanswered questions in a discussion can linger and create extra follow-up for the person coordinating the work.
- Search for current supporting context.
- Keep factual follow-up tied to the relevant page.
- Make it easier to distinguish a claim from a question.
Setup
Build it in a few focused steps.
- 1Connect Notion and Octen to Notis once in the portal.
- 2Create the automation in the portal or ask Notis in plain language.
- 3Describe when a page comment should prompt Octen to search for current evidence on its factual question.
- 4Select New Comment and specify the page or block to watch.
- 5Choose the report channel and test using a real question on that page.
Questions about this workflow
How is this different from watching all workspace comments?
New Comment is intended for comments on a specified Notion block or page.
Will every comment trigger it?
The trigger watches new comments on the selected page or block. Explain in the instruction which comments should get a search.
When this happens · Trigger
Do this · Action
Supported Triggers and Actions
Notis builds workflows that link Notion to Octen. A trigger fires from one place; an action lands in another.
Notion triggers
Octen actions
Recurring trigger
Notis starts this workflow on a schedule, such as daily, weekly, or during business hours.
Octen Broad Search
Broad web search — decompose a query into sub-queries from multiple angles and search concurrently.
Webhook trigger
Notis starts this workflow when an external tool or custom backend sends an HTTP request.
Octen Web Search
Real-time web search across the live internet, with filters, highlights, and full page content.
All Page Events
Triggers when any Notion page is created or updated across the workspace.
Octen Embedding
Convert text into embedding vectors.
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.
Octen Extract
Extract clean, LLM-ready markdown from web pages — up to 20 URLs per call.
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 Octen, 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 Octen.