Kie.ai Video Rendering Cache with n8n Data Table & Google Drive

Turn repeated video prompts into instant, cached results—then save winners to Google Drive

This n8n sub-workflow fixes a broken Sora video-generation step by sending text-to-video jobs to Kie.ai, caching identical requests in an n8n Data Table, and uploading successful renders to Google Drive. The calling workflow gets a single, flat result payload—either the delivered video details or a clear failure report.

What this workflow does

• Receives a prompt + optional render settings from a calling workflow (or manual test run).
• Normalizes and clamps parameters, then generates a deterministic job key and prepares a model fallback chain.
• Checks the n8n Data Table cache for the job key; on a cache hit, it immediately returns the stored video details.
• Submits to Kie.ai in sequence, polling Kie.ai every 20 seconds for up to 5 minutes per model. If a model fails or times out, it moves on.
• Aggregates attempts and selects the first successful render, including an attempt trail and total credits consumed.
• Downloads the winning video, uploads it to Google Drive, and upserts: job key, video URL, Drive file ID, model, and credit usage into the Data Table.
• Returns a single response payload: either delivered video details or a failure payload listing models tried and reasons.

Use cases

• Prevent duplicate Kie.ai renders when multiple workflows reuse the same prompt and settings.
• Build a resilient replacement for a broken Sora step with model fallback and clear failure diagnostics.
• Store and reuse rendered assets in Google Drive while tracking credits per job key.

Technical details

• Kie.ai authenticated via HTTP Header Auth to api.kie.ai.
• Google Drive credentials plus a configured target Drive and folder ID.
• Workflow nodes: if, set, code, wait, data table, sticky note.