Skip to content
Notis

Prepare research text for semantic retrieval

When research content changes, convert the relevant text into embeddings for workflows that compare or retrieve related material.

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

Octen Embedding

Convert text into embedding vectors.

Why this helps

Research gets harder to reuse when related notes cannot be discovered by meaning or topic.

  • Create vectors from updated research text.
  • Support similarity search in a connected downstream workflow.
  • Reduce manual preparation of text for retrieval.

Setup

Build it in a few focused steps.

  • 1Connect Notion and Octen to Notis once.
  • 2Create an automation in the portal or ask Notis in plain language.
  • 3Use one instruction to generate embeddings from the relevant text when a research page body changes.
  • 4Select Page Content Updated and scope it to a suitable page or data source.
  • 5Choose a channel for run reports and test with one real research update.

Questions about this workflow

What does the embedding action return?

Octen Embedding converts text into embedding vectors.

Does an embedding itself make notes searchable?

It creates vectors for use by a retrieval workflow; the automation instruction should reflect the intended downstream use.

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.

TriggerScheduled

Octen Broad Search

Broad web search — decompose a query into sub-queries from multiple angles and search concurrently.

ActionInstant

Webhook trigger

Notis starts this workflow when an external tool or custom backend sends an HTTP request.

TriggerInstant

Octen Web Search

Real-time web search across the live internet, with filters, highlights, and full page content.

ActionInstant

All Page Events

Triggers when any Notion page is created or updated across the workspace.

TriggerPolling

Octen Embedding

Convert text into embedding vectors.

ActionInstant

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.

TriggerInstant

Octen Extract

Extract clean, LLM-ready markdown from web pages — up to 20 URLs per call.

ActionInstant

New Comment

Triggers when a new comment is added to a specified Notion block or page.

TriggerPolling

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.

TriggerInstant

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.

TriggerInstant

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.

TriggerInstant

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.