Turn a recurring support theme into a response video draft
When a recurring question deserves a clearer answer, start a video draft from the support context you already collected.
Trigger
Webhook received
Notis starts this workflow when an external tool or custom backend sends an HTTP request.
Action
Edit Video with References
Multimodal video generation and editing with Kling O1.
Why this helps
Repeated customer questions can keep demanding individual replies because useful explanations are hard to turn into reusable content.
- Turn a recurring support topic into a reusable visual explanation draft.
- Use existing context and references to guide the edit.
- Reduce repeated effort on the same explanation.
Setup
Build it in a few focused steps.
- 1Connect Notion and Kling to Notis once through the portal.
- 2Create an automation with one plain-language instruction to turn the relevant support theme and available references into a short response video draft.
- 3Choose an incoming webhook trigger and a channel for run reports.
- 4Send one real test request for a documented support theme and review the result.
Questions about this workflow
Can this use an existing video reference?
Describe in the instruction how the available video and other references should inform the edit.
Does it send the video to customers?
No. It creates a draft for review; sharing it is a separate choice.
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.