Template:
4 „Gefällt mir“
It created a good video, but speed looks too slow.
That 40-second Wait is easy to blame, but it only controls when the workflow checks again. It does not change the finished video’s playback speed. If generation is slow, a shorter wait only notices completion sooner. If the reel itself feels slow, the scene timing or final render needs to change.
For playback pacing, generate the narration first and use its actual duration to decide how much visual material you need. A short spoken line should not sit on a long generic scene. Keep each visual prompt to one visible action and cut any dead time at the start or end of the rendered clip. I would test the same 15-second script twice, once with the current prompts and once with more specific motion, before changing the rest of the workflow.
The polling loop needs a stop condition too. Save the video creation ID, increment an attempt counter after each Get Video call, and mark the job failed after a deadline if `mediaUrl` is still empty. Otherwise a failed render can circle through Wait forever without telling you what happened.
Cache the finished video ID and media URL before the approval email. If publishing fails later, retry the existing asset instead of creating a different video. Since you already use the blotato node, keep Create Video and Create Post as separate jobs. Only call Create Post after approval, then save the returned post ID and check until the status is `published` or `failed`. A green n8n execution only proves the workflow ran.
Run the 15-second control first. That will tell you whether the slow part is the generated motion, the scene length, or simply how long the workflow waits before showing the result.
1 „Gefällt mir“