Short answer: Drop the "Kling AI → Kling Generate Video" action anywhere in your workflow, map the inputs from upstream nodes, and publish.
Every field can be mapped from an upstream trigger, AI step, table row, or hard-coded literal.
| Field | Type | Required | Description |
|---|---|---|---|
Prompt prompt | string | Required | Prompt (required) |
Model model_name | options | Optional | Model. Options: Kling V2.1 (best), Kling V2 Master, Kling V1.6 |
Duration duration | options | Optional | Duration. Options: 5s, 10s |
Aspect Ratio aspect_ratio | options | Optional | Aspect Ratio. Options: 16:9, 9:16, 1:1 |
{"prompt": "{{trigger.prompt}}","model_name": "{{trigger.model_name}}","duration": "{{trigger.duration}}","aspect_ratio": "{{trigger.aspect_ratio}}"}
{"code": 0,"data": {"task_id": "task-abc123","task_status": "submitted"},"message": "SUCCEED"}
Use these fields in downstream nodes for routing, logging, or error handling.
Any of these apps can fire this action as part of a workflow.
Triggered by anything in the catalog. Free tier available. No credit card.