Turn a new case study record into a visual story
As soon as a case study takes shape, create a visual concept that helps the team see its narrative.
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
Seedance 2.5 Video (BytePlus)
Text-to-video with ByteDance Seedance 2.5.
Why this helps
Case studies require many follow-ups, and adding a video version can slip behind other launch work.
- Give the story a visual direction early in the process.
- Reduce the effort needed to start a video brief.
- Help reviewers react to the narrative before production.
Setup
Build it in a few focused steps.
- 1Connect Notion and ByteDance to Notis once.
- 2Ask Notis to create a case study video concept from new records in the chosen database.
- 3Select Notion Page Created and scope it to the case study data source.
- 4Choose a reporting channel and test with one real case study record.
Questions about this workflow
Does a new record need to be complete?
A focused draft can start early; include the customer, challenge, outcome, and approved details as they become available.
Can it invent missing results?
Tell Notis to use only facts on the page and review the output for accuracy.
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.