Skip to content
Notis

Give every new project page a visual overview

A new project can get a shareable visual summary while its purpose and direction are fresh.

Trigger

Page Added to Page

Fires when a new subpage (a `child_page` type block) is added under a specified parent Notion page.

Action

Seedance 2.5 Video (BytePlus)

Text-to-video with ByteDance Seedance 2.5.

Why this helps

Founders often repeat the same project explanation across kickoff calls, updates, and stakeholder messages.

  • Create an early visual aid from the project context already written down.
  • Make project kickoffs easier to explain consistently.
  • Avoid starting every introduction from a blank page.

Setup

Build it in a few focused steps.

  • 1Connect Notion and ByteDance to Notis once in the portal.
  • 2Ask Notis to create a short project overview video when a subpage is added beneath your project hub.
  • 3Choose the Notion Page Added to Page trigger and the parent project page.
  • 4Select a channel for run reports and test by creating one real project subpage.

Questions about this workflow

Does this apply to every subpage in the workspace?

The trigger is intended for subpages under the selected parent page.

What should the project page say?

A goal, audience, expected outcome, and any important constraints make a stronger overview prompt.

When this happens · Trigger

Do this · Action

Supported Triggers and Actions

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

Notion triggers

ByteDance actions

Recurring trigger

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

TriggerScheduled

Seedance 2.5 Video (BytePlus)

Text-to-video with ByteDance Seedance 2.5.

ActionInstant

Webhook trigger

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

TriggerInstant

Seedance 2.0 Mini Video (BytePlus)

Text-to-video with ByteDance Seedance 2.0 Mini.

ActionInstant

All Page Events

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

TriggerPolling

Seedance 2.0 Video (BytePlus)

Text-to-video with ByteDance Seedance 2.0.

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

Seedance 2.0 Fast Video (BytePlus)

Text-to-video with ByteDance Seedance 2.0 Fast.

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 ByteDance, 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 ByteDance.