Skip to content
Notis

Make vendor research easier to compare

Update a vendor record in Notion and extract its linked pages into clean markdown that is simpler to revisit side by side.

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

Octen Extract

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

Why this helps

Comparing tools often means reopening the same pages and trying to remember what mattered in each one.

  • Review vendor sources in a consistent text format.
  • Lower the effort of resuming an evaluation.
  • Keep source material close to the tracker update.

Setup

Build it in a few focused steps.

  • 1Connect Notion and Octen to Notis once.
  • 2Create an automation from the portal or ask Notis conversationally.
  • 3Write one instruction to extract the relevant URLs from updated vendor records into clean markdown.
  • 4Select Page Properties Updated and scope it to the vendor data source.
  • 5Pick a channel for run reports and test with one real vendor update.

Questions about this workflow

Can I target just the vendor tracker?

Yes. Scope Page Properties Updated to the vendor data source.

How many URLs can be processed in one call?

Octen Extract supports up to 20 URLs per call.

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.