🎥 DEMO: https://www.youtube.com/watch?v=5ZE7mBozaZ4
This workflow is the polling webhook used by the main Telegram AI Shorts Generator workflow published here:
https://creators.n8n.io/workflows/12682
It is responsible for handling long-running AI video generation tasks, including polling Veo, Sora, and Seedance APIs, waiting between attempts, detecting completion or failure, retrieving the final video, and returning the result back to the main workflow for preview, publishing, or extension. Separating this logic into a dedicated webhook keeps the main workflow fast, reliable, and production-ready.
This workflow is a dedicated polling webhook designed to handle long-running AI video generation jobs for Veo, Sora, and Seedance when using n8n.
It is intended to be used as a companion workflow to a main video generation workflow (for example, a Telegram-based AI Shorts generator).
The webhook repeatedly checks the status of an AI video task, waits between attempts, and continues polling until the video is either completed, failed, or times out.
Once generation is complete, the workflow automatically:
• Downloads the final video
• Uploads it to S3-compatible storage
• Restores the original session from Redis
• Merges video data with session metadata
• Sends a Telegram video preview with publishing options
• Supports video extension workflows (Veo only)
• Saves detailed generation metadata alongside the video
• Polls up to 15 attempts (≈15 minutes total)
• Gracefully handles:
• API failures
• missing URLs
• unexpected response formats
• Notifies the user on timeout with task details
• Keeps main workflows fast and responsive
• Handles async AI jobs without blocking executions
• Centralizes polling logic for multiple AI providers
• Makes long-running video generation production-ready
• Cleanly separates orchestration from user interaction
• Telegram AI video bots
• YouTube Shorts automation workflows
• AI content farms
• Multi-model video pipelines
• Any workflow using Veo, Sora, or Seedance APIs
• This workflow is not standalone
• It must be triggered by another workflow via HTTP Request
• Requires shared Redis and S3 configuration with the parent workflow
You will need credentials for:
• KIE.ai API
• Redis
• S3-compatible storage
• Telegram Bot API (for previews)
⸻ Tags
webhook
ai-video
polling
long-running-jobs
content-automation
telegram
youtube
redis
s3
async