Turn Notion launch briefs into Kling video drafts
Move from a written launch brief to a visual first draft without rebuilding the context in another tool.
Trigger
New Page
Triggers when a new page is added to a Notion database.
Action
Standard Text to Video
Text-to-video with Kling 2.6.
Why this helps
Transferring launch details into a video prompt adds another task just when launch work is already spread across several tools.
- Start creative exploration as soon as a launch brief exists.
- Keep the video concept grounded in the brief's audience and key message.
- Reduce the effort of restarting context in a separate video tool.
Setup
Build it in a few focused steps.
- 1Connect Notion and Kling to Notis once through the portal.
- 2In the portal, create an automation and describe how a new launch brief should become a short video draft.
- 3Select Notion's New Page trigger for the launch brief database and choose a channel for run reports.
- 4Test by adding one real launch brief and reviewing the generated video.
Questions about this workflow
Does this publish the launch video?
No. It generates a video draft for review; publishing is a separate step.
Can I narrow it to launch briefs?
Choose the New Page trigger for the database where you keep launch briefs.
When this happens · Trigger
Do this · Action
Supported Triggers and Actions
Notis builds workflows that link Notion to Kling. A trigger fires from one place; an action lands in another.
Notion triggers
Kling actions
Recurring trigger
Notis starts this workflow on a schedule, such as daily, weekly, or during business hours.
Standard Text to Video
Text-to-video with Kling 2.6.
Webhook trigger
Notis starts this workflow when an external tool or custom backend sends an HTTP request.
Image to Video
Image-to-video with Kling 3.0 (first or first+last frame).
All Page Events
Triggers when any Notion page is created or updated across the workspace.
Edit Video with References
Multimodal video generation and editing with Kling O1.
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.
Fast Text to Video
Text-to-video with Kling 3.0 Turbo.
New Comment
Triggers when a new comment is added to a specified Notion block or page.
Budget Text to Video
Text-to-video with Kling 2.5 Turbo.
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.
Standard Image to Video
Image-to-video with Kling 2.6 (first or first+last frame).
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 Kling, 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 Kling.