Turn an updated feature brief into a demo draft
When the feature story changes, generate a fresh short demo concept without rebuilding the request from scratch.
Trigger
Page Content Updated
Triggers when the body content of a Notion page is 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 page content edit in the workspace the integration has access to. Notion aggregates content edits within a short window (~60s typical).
Action
Seedance 2.0 Mini Video (BytePlus)
Text-to-video with ByteDance Seedance 2.0 Mini.
Why this helps
A changed brief can leave a stale video request and force someone to notice, summarize, and resubmit it manually.
- Respond to meaningful brief edits with a new video draft.
- Keep the demo aligned with the latest feature explanation.
- Make it easier to review an idea before investing in production.
Setup
Build it in a few focused steps.
- 1Connect Notion and ByteDance to Notis once in the portal.
- 2Ask Notis to generate a concise feature demo whenever a feature brief's body is updated.
- 3Pick the Notion Page Content Updated trigger, scoped to the relevant page or data source if useful.
- 4Choose a reporting channel and test with a real brief edit.
Questions about this workflow
Will every small edit create a video?
Notion groups nearby content edits, and your prompt can ask Notis to act only when the change updates the feature story.
Can the video use the brief's details?
Yes. Describe in the prompt which information from the updated page should guide the video.
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.
Seedance 2.5 Video (BytePlus)
Text-to-video with ByteDance Seedance 2.5.
Webhook trigger
Notis starts this workflow when an external tool or custom backend sends an HTTP request.
Seedance 2.0 Mini Video (BytePlus)
Text-to-video with ByteDance Seedance 2.0 Mini.
All Page Events
Triggers when any Notion page is created or updated across the workspace.
Seedance 2.0 Video (BytePlus)
Text-to-video with ByteDance Seedance 2.0.
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.
Seedance 2.0 Fast Video (BytePlus)
Text-to-video with ByteDance Seedance 2.0 Fast.
New Comment
Triggers when a new comment is added to a specified Notion block or page.
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.
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.
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.
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.