Kie.ai Veo video sub-workflow

What it is

This n8n workflow is a building block. Another workflow calls it to make one video on Kie.ai’s Veo model, and it hands back the video’s address. Seven nodes do the work. It receives a prompt, a frame shape, a list of image addresses and a generation type, and posts them to Kie.ai. Then it asks for the task’s status, waits five seconds and asks again until the video is ready, and returns the first address as resultUrls. Those are the four fields Mindket’s AI product photo to video generator sends to its own video sub-workflow, so this file can fill that slot.

1. Called with a prompt, a frame, images and a type
2. Posts the request to Kie.ai’s Veo endpoint
3. Asks for the task’s status
4. While it runs, waits five seconds and asks again
5. Returns the first video address as resultUrls

Who it suits

n8n builders who make video workflows and want the Kie.ai call, with its waiting loop, in one place that several workflows share. Skip it if you want something to press: it has no form or button of its own and runs only when another workflow calls it.

Where to use it

It runs on the same n8n as the workflow that calls it, because an Execute Workflow node can only pick a workflow from its own n8n.

• n8n Cloud or your own server: import it next to the calling workflow
• The calling workflow: an Execute Workflow node that picks this one and sends the four fields
• AI product photo to video generator: it sends exactly these four fields to its sub-workflow
• The node after the call: it receives resultUrls, ready to download or send on

Setup

Get it saves a zip with workflow.json and Mindket’s setup notes in your downloads folder. Its author puts setup at about 5 minutes.

1. In n8n, create a workflow, open its menu, choose Import from File and pick workflow.json.
2. In Submit generation request and in Get request status, replace <YOUR_KIE_AI_API_KEY> in the Authorization header with your Kie.ai key. The brackets go too, so each header reads Bearer, a space and the key.
3. Save the workflow. It does not need to be published, because another workflow starts it.
4. In the calling workflow, open its Execute Workflow node, choose this workflow in the list and map the four fields.

How to use it

The caller sends four fields. Each goes to Kie.ai under the name the request needs.

The file also fixes model at veo3_fast and sets enableFallback to true, both in the body of Submit generation request. Kie.ai’s own Veo pages explain what the fallback option changes.

Example

A caller sends this for a product shot.

{
  "video_prompt": "Cold brew bottle on a sunny café counter, slow dolly-in",
  "aspect_ratio": "9:16",
  "imageUrls": ["https://example.com/bottle.jpg"],
  "generationType": "REFERENCE_2_VIDEO"
}

The call comes back with one field, resultUrls, holding the first video address as text.

{ "resultUrls": "https://…" }

For newcomers and experts

If you are new. A sub-workflow is a workflow that other workflows call, the way a program calls a function. This one holds the slow part of making a video, which is sending the request and waiting for it. Test it from the calling workflow. Then open this one under Executions to see what each node received.

For experts. The status check runs once straight after the submit, with no wait, and later after each pause. Switch1 reads data.successFlag from Kie.ai’s reply.

Wait2 has no settings of its own, so it uses n8n’s default of five seconds for this version of the node. Change it there to poll less often.

Good to know

Each generation costs money, and a failed task ends without a message.

• Billing: Kie.ai bills each generation to your account
• Silent failure: flags 2 and 3 go nowhere, so the caller gets no item back and you read the run under Executions to see why
• No retry limit: a task that stays at 0 is checked every five seconds until it changes
• Your key: it sits in two header fields as plain text, so anyone who can open the workflow can read it. A header credential in n8n avoids that
• Images: Kie.ai fetches them from the addresses you send, so private links will not work
• Credentials: the JSON holds none, and nothing from its author’s account