n8n Reel Cloner Workflow: Apify Cut-by-Cut Product Rebuild

Rebuild reel clones cut-by-cut—keeping the exact shot count, pacing, and order

This n8n Reel Cloner workflow takes a reel apart, replaces the product in every shot, and then reassembles the finished video in the original sequence—so your output matches the source’s exact shot count and pacing, not a loose “similar” recreation.

What this workflow does

• Send a reel URL + product manually or via a webhook.
• Apify downloads the source reel, then a scene-detection actor finds every hard cut and saves one keyframe per shot.
• Background polling for long reels: the job is polled rather than waited on, preventing timeouts mid-run.
• Single Gemini Flash call for shot prompts: all keyframes are sent to Gemini Flash in one call, which generates an image prompt and motion prompt per shot with your product substituted for what the source was selling.
• fal.ai generates and animates each scene: it produces a still image for each shot, then animates it using that shot’s motion prompt, one scene at a time.
• Trim to exact shot duration and reassemble: each clip is trimmed to the replacement shot’s exact length, then joined in the original order; the finished video and thumbnail are returned.

Use cases

• SaaS operators who want consistent, repeatable ad/video iterations using a proven reel format—without losing pacing.
• Automation engineers building content pipelines that transform reel URLs into product-specific creatives.
• n8n workflow builders needing cut-by-cut scene handling (hard cuts, per-shot keyframes) instead of single-pass cloning.

Technical details

• Auth setup (critical): create three separate Header Auth credentials: Apify (Bearer token), Google Gemini (X-goog-api-key), and fal.ai (Authorization: Key).
• n8n node building blocks: if, set, code, wait, webhook, split out.
• Best practice note: don’t reuse one Header Auth credential across different hosts—n8n may silently send the wrong key.