Short answer: Drop the "Kling AI → Kling Image to 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 |
|---|---|---|---|
Image URL or base64 image | string | Required | Image URL or base64 (required) |
Motion Prompt prompt | string | Optional | camera slowly zooms in |
Model model_name | options | Optional | Model. Options: Kling V2.1, Kling V1.6 |
Duration duration | options | Optional | Duration. Options: 5s, 10s |
{"image": "{{trigger.image}}","prompt": "camera slowly zooms in","model_name": "{{trigger.model_name}}","duration": "{{trigger.duration}}"}
{"code": 0,"data": {"task_id": "task_abc","task_status": "submitted"}}
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.