Skip to content
Notis

Add useful video references to new learning pages

A new learning note can come with a few videos to help turn reading into action.

Trigger

Page Created

Triggers when a new Notion page is created. Customer optionally scopes with at most one of: - data_source_id: new row in this data source - parent_page_id: new sub-page under this page (immediate parent only) With neither set, fires for any new page in the workspace the integration has access to. Notion sends ~60s aggregation latency on most events.

Action

/v1/youtube

Why this helps

Learning notes often lack practical demonstrations, so the next step becomes another open-ended search.

  • Pair a learning topic with practical demonstrations.
  • Make it easier to move from notes into trying a technique.
  • Give future readers a quick starting point.

Setup

Build it in a few focused steps.

  • 1Connect Notion and api.kadec0.xyz to Notis once in the portal.
  • 2Ask Notis to find a small set of useful video demonstrations related to each new learning page.
  • 3Select Page Created for the learning page or its parent page.
  • 4Choose a channel for run reports and test with one real learning page.

Questions about this workflow

How do I keep this focused on a learning area?

Select the Page Created trigger scoped to the relevant parent page or data source when creating the automation.

Can the prompt request beginner-friendly videos?

Yes. Include the intended audience and format in the plain-language instruction.

When this happens · Trigger

Do this · Action

Supported Triggers and Actions

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

Notion triggers

api.kadec0.xyz actions

Recurring trigger

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

TriggerScheduled

/v1/youtube

ActionInstant

Webhook trigger

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

TriggerInstant

/v1/serp-batch

ActionInstant

All Page Events

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

TriggerPolling

/v1/scrape

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

/v1/enrich

ActionInstant

New Comment

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

TriggerPolling

/v1/serp-read

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

/v1/cve

ActionInstant

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 api.kadec0.xyz, 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 api.kadec0.xyz.