Turn a new content planning view into a quick promo concept
A new focused view can signal a fresh content push and start its visual draft without another manual task.
Trigger
View Created
Triggers when a new Notion view is created. Fires workspace-wide. The payload includes `data.view_type` (`table`, `board`, `gallery`, `calendar`, `list`, `timeline`, `gantt`) and `data.parent` pointing at the view's tree parent (typically the teamspace), so customers can filter downstream.
Action
Seedance 2.0 Fast Video (BytePlus)
Text-to-video with ByteDance Seedance 2.0 Fast.
Why this helps
Setting up a new planning view often marks a real initiative, but creative follow-through still relies on a separate reminder.
- Connect a new planning surface to an immediate creative starting point.
- Reduce the delay between organizing content and making it visible.
- Give teams a quick draft to shape into a campaign asset.
Setup
Build it in a few focused steps.
- 1Connect Notion and ByteDance to Notis once.
- 2Ask Notis to create a quick promo concept when a relevant content planning view is created.
- 3Select Notion View Created and describe the kinds of views that represent a real initiative.
- 4Choose a channel for run reports and test by creating an appropriate view.
Questions about this workflow
Is every new view a good reason for a video?
Not necessarily. Make the prompt specific about the view types or context that signal a promotional initiative.
What context can it use?
Include the intended content area and the message you want the video to support in the instruction.
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.