Skip to content
Notis

Start a New Data Source with Shared Industry Context

A new data source signals that a team is about to organize a topic. Notis can use that creation event to search for current terminology, benchmarks, and public examples related to its purpose.

Trigger

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.

Action

Search

Tool to perform unified search across 40+ search engines including Google, Bing, Yahoo, DuckDuckGo, YouTube, Amazon, and more. Use when you need to retrieve search results with rich structured data including organic results, ads, knowledge graphs, local listings, images, videos, and related searches. Supports advanced filtering by location, language, date, device type, and SafeSearch settings.

Why this helps

A collection grows around inconsistent assumptions because nobody pauses at creation time to gather shared external context.

  • Establish common context before the collection grows
  • Discover useful public terminology and examples
  • Attach research timing to the structural creation event

Setup

Build it in a few focused steps.

  • 1Connect Notion and Search API to Notis once.
  • 2Tell Notis what benchmarks, terminology, and examples to search for when a new data source appears.
  • 3Select the Notion Data Source Created trigger and a report channel.
  • 4Test by creating a small data source for a real topic.

Questions about this workflow

Why use the Data Source Created event?

It fires when a data source is added, including when a template creates one or more data sources inside a database container.

Can the search be different for each topic?

Yes. Write the instruction so Notis uses the available data source context when forming the search.

When this happens · Trigger

Do this · Action

Supported Triggers and Actions

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

Notion triggers

Search api actions

Recurring trigger

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

TriggerScheduled

Get Account Info

Tool to retrieve account usage statistics including monthly usage, remaining credits, hourly limits, and subscription period information. Use when you need to check current account status or usage limits.

ActionInstant

Webhook trigger

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

TriggerInstant

Get Cached Search by ID

Tool to retrieve cached search results by search ID in JSON format. Use when you need to access previously executed search results without re-running the query. The search ID is found in the search_metadata.id or search_metadata.json_url field from initial search responses. Cached results are available for 90 days.

ActionInstant

All Page Events

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

TriggerPolling

Get Cached Search HTML by ID

Tool to retrieve cached search results by search ID in HTML format. Use when you need to access the raw HTML snapshot of a previous search execution. The search ID is available in the search_metadata.id or search_metadata.html_url field from initial search responses.

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

Get Locations

Tool to get available locations for geo-localized search queries. Use when you need to find location identifiers for targeting Google searches to specific geographic areas. Returns location metadata including identifiers, names, coordinates, and population reach.

ActionInstant

New Comment

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

TriggerPolling

Search

Tool to perform unified search across 40+ search engines including Google, Bing, Yahoo, DuckDuckGo, YouTube, Amazon, and more. Use when you need to retrieve search results with rich structured data including organic results, ads, knowledge graphs, local listings, images, videos, and related searches. Supports advanced filtering by location, language, date, device type, and SafeSearch settings.

ActionInstant

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 Search api, 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 Search api.