Telegram Video Brief to Zvid MP4 n8n Workflow (OpenRouter GPT-4.1)

Turn a Telegram video brief into an approved Zvid MP4 draft—then deliver the final video back to Telegram

This Telegram Video Brief to Zvid MP4 n8n workflow takes a brief from Telegram (or a local test input), plans and prepares an editable Zvid draft with a signed credit quote, waits for approval, renders the exact accepted job, and returns the completed MP4 to the same chat. OpenRouter (GPT-4.1 via OpenRouter) is used for planning—even before any video is rendered.

What this workflow does

• Ingest and validate input: Starts from a Telegram message or a local Test brief, normalizes the brief, and rejects unauthorized or non-text Telegram requests.
• Isolate conversation memory: Maintains separate memory per chat and applies a configured per-render credit ceiling to Zvid MCP tool usage.
• Plan and prepare a Zvid draft: Plans the video, selects a Zvid library design, and adapts a saved draft (with support for template quota using a validated static editor project).
• Provide quote + draft link: Returns the actual saved draft link and a signed quote. A later approval triggers submission of one render.
• Render with strict job tracking: Waits for the accepted job status using the native Zvid node—without replacing status checks with additional paid renders.
• Media guard + delivery: Allows only completed Zvid MP4 URLs through a media guard, replies in Telegram, and downloads the file for “Watch video”.

Use cases

• SaaS teams collecting video requirements via Telegram and generating consistent, reusable Zvid drafts.
• Automation engineers needing an approval-gated workflow with credit limiting and exact accepted-job rendering.
• Operators who want a tight loop: brief → quote + editable draft → approval → final MP4 delivered back to the requester.

Technical details

• n8n self-hosted workflow
• Nodes: if, set, code, telegram, zvid (from @zvid/n8n-nodes-zvid), sticky note
• Zvid connection: install @zvid/n8n-nodes-zvid in Settings → Community nodes; connect both Zvid nodes using https://app.zvid.io/api-keys and Base URL https://api.zvid.io
• OpenRouter GPT planning: uses openai/gpt-4.1 (provider charges apply even if no video is rendered)
• Zvid MCP Client Tool: configured at https://mcp.zvid.io/mcp with the required Header