Generate and cache Kie.ai video renders to Google Drive
Ready for 3.0Ready for 3.0. This template uses no nodes that n8n 3.0 removes. No removed nodes, versions or helpers found. Static check, last run 2026-10-19.
What this workflow does
This workflow has 22 nodes and runs manually, when you click “Execute workflow” (plus 1 other trigger). Along the way it connects Google Drive. It also calls api.kie.ai over HTTP.
How it runs
Trigger: Manually, when you click “Execute workflow” (plus 1 other trigger).
- Sample Job Input (Edit Fields (Set)): sets 4 fields: prompt, durationSeconds, aspectRatio…
- Normalize Job Request (Code): runs custom JavaScript code
- Look Up Render Cache (Data table): get
- Rendered This Before? (If): checks a condition and branches into true / false
- Return The Cached Video (Edit Fields (Set)): sets 6 fields: delivered, videoUrl, driveFileId…
- Build Model Chain (Code): runs custom JavaScript code
- Loop Over Model Chain (Loop Over Items (Split in Batches)): loops over the items in batches
- Pick The Successful Render (Code): runs custom JavaScript code
- Submit Render Job (HTTP Request): calls api.kie.ai (POST)
- Did Any Model Deliver? (If): checks a condition and branches into true / false
…plus 10 more steps. See the full node list below.
Services it uses
HTTP calls to: api.kie.ai
Before you upgrade to n8n 3.0
Nothing in this workflow is removed in n8n 3.0, so it should import and run after the upgrade.
Nodes used (10)
- Manual Trigger
n8n-nodes-base.manualTrigger - Edit Fields (Set)
n8n-nodes-base.set - Execute Workflow Trigger
n8n-nodes-base.executeWorkflowTrigger - Code
n8n-nodes-base.code - Data table
n8n-nodes-base.dataTable - If
n8n-nodes-base.if - Loop Over Items (Split in Batches)
n8n-nodes-base.splitInBatches - HTTP Request
n8n-nodes-base.httpRequest - Wait
n8n-nodes-base.wait - Google Drive
n8n-nodes-base.googleDrive
From the author
Quick overview This sub-workflow replaces a broken Sora video-generation step by submitting text-to-video jobs to Kie.ai, caching identical requests in an n8n Data Table, and saving successful renders to Google Drive before returning a single result payload…