Skip to content
Notis

Make vendor comparisons from your Notion shortlist

Capture the options in Notion and let Notis prepare a sourced comparison to help you decide.

Trigger

New Page

Triggers when a new page is added to a Notion database.

Action

Compare options

Weigh several products, vendors, or approaches.

Why this helps

Comparing vendors from scattered notes makes it hard to see tradeoffs and can delay a decision.

  • See key differences in one researched report.
  • Keep the options and decision context in your workspace.
  • Reduce repeat searches when a purchase decision comes around.

Setup

Build it in a few focused steps.

  • 1Connect Notion and Deep research to Notis once in the portal.
  • 2Create an automation in the portal or tell Notis to compare the vendors in your Notion shortlist and summarize practical tradeoffs.
  • 3Choose the Notion New Page trigger for the shortlist database.
  • 4Choose a channel for run reports and test with a real vendor entry.

Questions about this workflow

Can I compare several options?

Yes. The plain-language instruction can ask Deep research to compare the options represented in your Notion context.

Does the report choose for me?

It returns a sourced comparison; you remain in control of the decision.

When this happens · Trigger

Do this · Action

Supported Triggers and Actions

Notis builds workflows that link Notion to Deep research. A trigger fires from one place; an action lands in another.

Notion triggers

Deep research actions

Recurring trigger

Notis starts this workflow on a schedule, such as daily, weekly, or during business hours.

TriggerScheduled

Research a company

Get a sourced brief before a call.

ActionInstant

Webhook trigger

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

TriggerInstant

Compare options

Weigh several products, vendors, or approaches.

ActionInstant

All Page Events

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

TriggerPolling

Deliver it later

The report arrives as a follow-up message when it is ready.

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

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 Deep research, 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 Deep research.