Capture customer context as a story video
A valuable customer detail in a comment can become a story draft before it disappears into a busy discussion thread.
Trigger
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.
Action
Seedance 2.0 Mini Video (BytePlus)
Text-to-video with ByteDance Seedance 2.0 Mini.
Why this helps
Useful customer anecdotes are easy to lose in comment threads and rarely make it into a shareable format.
- Give timely customer insight a visual starting point.
- Reduce the chance that a good anecdote gets buried.
- Create a reviewable draft for marketing or founder updates.
Setup
Build it in a few focused steps.
- 1Connect Notion and ByteDance to Notis once.
- 2Ask Notis to create a short customer story video concept from relevant new comments.
- 3Select Notion Comment Created and, if practical, scope it to the customer stories page.
- 4Choose a run-report channel and test with a real, appropriate comment.
Questions about this workflow
Can this run on every workspace comment?
The event can fire for comments the integration can access; use a page filter when you want to narrow its scope.
Should comments contain private customer details?
Keep sensitive information out of the prompt and use only customer details approved for the intended 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.