HumationHuman + Automation
Back to Catalog

Generate & publish AI cinematic videos to YouTube Shorts using VEO3 & Gemini

SuSSuS
2061 views
2/3/2026
File ManagementGoogle DriveNotificationsAutomationEmail
Official Page

How it Works

This workflow uses VEO3 to generate surreal cinematic AI videos at a fraction of the cost compared to Google’s standard video generation APIs.
With it, you can automatically run a YouTube Shorts channel (and optionally Instagram uploads) that posts new AI videos every day completely automated.

Workflow Overview

  1. Schedule Trigger

    • Runs automatically at your chosen times (e.g., twice per day).

  2. AI Prompt Generator

    • Creates a detailed video idea based on your chosen niche.
    • You only need to adapt the system prompt to your theme (e.g., Travel Facts, Tech Visuals, Mini-Facts, Impossible Realities, Food Illusions).
    • Output includes:
      • Video Prompt (for VEO3 API)
      • Social Caption with hashtags
      • YouTube Title
      • YouTube Description

  3. VEO3 Video Generation

    • Sends the prompt to KIE AI VEO3 (model: veo3_fast).
    • Produces 9:16 vertical short-form videos optimized for YouTube Shorts, TikTok, Instagram Reels.
    • Significantly cheaper than Google’s Video AI while delivering cinematic quality.

  4. Publishing

    • Uploads automatically to YouTube Shorts (with AI-generated titles, descriptions, tags).
    • In parallel, posts the same video to a Telegram channel (Instagram upload possible with a small modification).

Why Use This Workflow?

  • Cost Advantage:

    • Google’s video generation is very expensive.
    • VEO3 costs are much lower, making it possible to publish multiple Shorts every day without breaking your budget.

  • Automated Channel Growth:

    • Build a fully automated YouTube Shorts channel.
    • Post fresh videos daily → more reach, more chances to go viral.

  • Flexible Niches:

    • Simply edit the system prompt to match your niche.
    • Examples:
      • Mini Facts Channel
      • Surreal Visual Loops
      • Tech Explainers in Visual Form
      • Food or Nature Illusions
    • The AI adapts automatically to your theme.

  • Cross-Platform:

    • Out of the box: YouTube + Telegram.
    • With small adjustments: Instagram Reels, TikTok uploads possible.

Setup Steps

  1. Get API Keys:

    • KIE AI VEO3 API key.
    • YouTube API credentials (OAuth2).
    • (Optional) Telegram Bot API or Instagram Graph API.

  2. Configure Schedule:

    • Define how often you want new videos (e.g., 1–5 per day).

  3. Adapt Prompts:

    • Change the AI Agent system prompt to your target niche.

  4. Run & Scale:

    • Let the workflow run automatically.
    • Watch your channel fill with new daily Shorts.

Tips & Notes

  • With VEO3 you can experiment with higher volume since costs are predictable and far lower than Google.
  • Start with one niche channel → once it works, clone the workflow to build multiple parallel AI-driven channels.
  • Always respect YouTube/Instagram guidelines when posting automated content.
  • Adding background music layers or captions can further increase virality.

⚡ Summary:
With this template you can create an AI-powered YouTube Shorts machine that runs on autopilot.
Just choose your niche, adjust the prompt, and let VEO3 + n8n handle video creation, uploading, and scaling — cheaper, faster, and smarter than traditional Google Video AI.

Questions or custom requests?
📩 suliemansaid.business@gmail.com

n8n Workflow: AI Cinematic Video Generation and YouTube Shorts Publishing with Veo3 and Gemini

This n8n workflow automates the process of generating AI-powered cinematic video concepts and publishing them as YouTube Shorts. It leverages the power of Google Gemini for AI content generation and interacts with external APIs (presumably Veo3, based on the directory name) for video creation, ultimately publishing the final video to YouTube and notifying via Telegram.

What it does

This workflow streamlines the creation and distribution of short-form video content by:

  1. Scheduling Execution: Triggers the workflow at specified intervals (e.g., daily, hourly).
  2. Generating AI Content: Uses an AI Agent powered by Google Gemini to generate cinematic video ideas or scripts.
  3. Parsing AI Output: Extracts structured data (e.g., video title, description, script) from the AI Agent's response.
  4. Creating Video (External API): Sends an HTTP request to an external API (likely a video generation service like Veo3) to create the cinematic video based on the AI-generated content.
  5. Waiting for Video Processing: Pauses the workflow to allow sufficient time for the video generation service to process and finalize the video.
  6. Uploading to YouTube: Publishes the generated video as a YouTube Short, including the AI-generated title and description.
  7. Notifying via Telegram: Sends a Telegram message with a confirmation and potentially the YouTube video link.

Prerequisites/Requirements

To use this workflow, you will need:

  • n8n Instance: A running n8n instance.
  • Google Gemini API Key: For the Google Gemini Chat Model node.
  • External Video Generation Service API Key/Endpoint: For the HTTP Request node (e.g., Veo3 API credentials and endpoint).
  • YouTube Account & Credentials: Configured in n8n for the YouTube node to upload videos.
  • Telegram Bot Token & Chat ID: Configured in n8n for the Telegram node to send notifications.

Setup/Usage

  1. Import the Workflow: Download the provided JSON and import it into your n8n instance.
  2. Configure Credentials:
    • Set up a Google Gemini credential for the Google Gemini Chat Model node.
    • Configure the HTTP Request node with the necessary API endpoint and authentication for your video generation service (e.g., Veo3).
    • Set up your YouTube OAuth 2.0 or API Key credentials in n8n.
    • Configure your Telegram Bot Token and Chat ID credentials in n8n.
  3. Customize AI Agent: Adjust the prompt and configuration of the AI Agent node to guide the Gemini model in generating the desired cinematic video concepts.
  4. Adjust Output Parser: Ensure the Structured Output Parser node correctly extracts the necessary fields (e.g., title, description, script, tags) from the AI Agent's output for subsequent nodes.
  5. Configure HTTP Request: Update the HTTP Request node to match the specific API documentation of your chosen video generation service, passing the AI-generated content as parameters.
  6. Set Wait Time: Adjust the Wait node's duration to accommodate the typical processing time of your video generation service.
  7. Customize YouTube Upload: Configure the YouTube node with the desired video privacy, category, and other metadata, using expressions to dynamically insert the AI-generated title and description.
  8. Customize Telegram Message: Modify the Telegram node's message to include relevant information, such as the YouTube video URL.
  9. Activate the Workflow: Once all configurations are complete, activate the workflow. It will run automatically based on the schedule defined in the Schedule Trigger node.

Related Templates

Track competitor SEO keywords with Decodo + GPT-4.1-mini + Google Sheets

This workflow automates competitor keyword research using OpenAI LLM and Decodo for intelligent web scraping. Who this is for SEO specialists, content strategists, and growth marketers who want to automate keyword research and competitive intelligence. Marketing analysts managing multiple clients or websites who need consistent SEO tracking without manual data pulls. Agencies or automation engineers using Google Sheets as an SEO data dashboard for keyword monitoring and reporting. What problem this workflow solves Tracking competitor keywords manually is slow and inconsistent. Most SEO tools provide limited API access or lack contextual keyword analysis. This workflow solves that by: Automatically scraping any competitor’s webpage with Decodo. Using OpenAI GPT-4.1-mini to interpret keyword intent, density, and semantic focus. Storing structured keyword insights directly in Google Sheets for ongoing tracking and trend analysis. What this workflow does Trigger — Manually start the workflow or schedule it to run periodically. Input Setup — Define the website URL and target country (e.g., https://dev.to, france). Data Scraping (Decodo) — Fetch competitor web content and metadata. Keyword Analysis (OpenAI GPT-4.1-mini) Extract primary and secondary keywords. Identify focus topics and semantic entities. Generate a keyword density summary and SEO strength score. Recommend optimization and internal linking opportunities. Data Structuring — Clean and convert GPT output into JSON format. Data Storage (Google Sheets) — Append structured keyword data to a Google Sheet for long-term tracking. Setup Prerequisites If you are new to Decode, please signup on this link visit.decodo.com n8n account with workflow editor access Decodo API credentials OpenAI API key Google Sheets account connected via OAuth2 Make sure to install the Decodo Community node. Create a Google Sheet Add columns for: primarykeywords, seostrengthscore, keyworddensity_summary, etc. Share with your n8n Google account. Connect Credentials Add credentials for: Decodo API credentials - You need to register, login and obtain the Basic Authentication Token via Decodo Dashboard OpenAI API (for GPT-4o-mini) Google Sheets OAuth2 Configure Input Fields Edit the “Set Input Fields” node to set your target site and region. Run the Workflow Click Execute Workflow in n8n. View structured results in your connected Google Sheet. How to customize this workflow Track Multiple Competitors → Use a Google Sheet or CSV list of URLs; loop through them using the Split In Batches node. Add Language Detection → Add a Gemini or GPT node before keyword analysis to detect content language and adjust prompts. Enhance the SEO Report → Expand the GPT prompt to include backlink insights, metadata optimization, or readability checks. Integrate Visualization → Connect your Google Sheet to Looker Studio for SEO performance dashboards. Schedule Auto-Runs → Use the Cron Node to run weekly or monthly for competitor keyword refreshes. Summary This workflow automates competitor keyword research using: Decodo for intelligent web scraping OpenAI GPT-4.1-mini for keyword and SEO analysis Google Sheets for live tracking and reporting It’s a complete AI-powered SEO intelligence pipeline ideal for teams that want actionable insights on keyword gaps, optimization opportunities, and content focus trends, without relying on expensive SEO SaaS tools.

Ranjan DailataBy Ranjan Dailata
161

Generate song lyrics and music from text prompts using OpenAI and Fal.ai Minimax

Spark your creativity instantly in any chat—turn a simple prompt like "heartbreak ballad" into original, full-length lyrics and a professional AI-generated music track, all without leaving your conversation. 📋 What This Template Does This chat-triggered workflow harnesses AI to generate detailed, genre-matched song lyrics (at least 600 characters) from user messages, then queues them for music synthesis via Fal.ai's minimax-music model. It polls asynchronously until the track is ready, delivering lyrics and audio URL back in chat. Crafts original, structured lyrics with verses, choruses, and bridges using OpenAI Submits to Fal.ai for melody, instrumentation, and vocals aligned to the style Handles long-running generations with smart looping and status checks Returns complete song package (lyrics + audio link) for seamless sharing 🔧 Prerequisites n8n account (self-hosted or cloud with chat integration enabled) OpenAI account with API access for GPT models Fal.ai account for AI music generation 🔑 Required Credentials OpenAI API Setup Go to platform.openai.com → API keys (sidebar) Click "Create new secret key" → Name it (e.g., "n8n Songwriter") Copy the key and add to n8n as "OpenAI API" credential type Test by sending a simple chat completion request Fal.ai HTTP Header Auth Setup Sign up at fal.ai → Dashboard → API Keys Generate a new API key → Copy it In n8n, create "HTTP Header Auth" credential: Name="Fal.ai", Header Name="Authorization", Header Value="Key [Your API Key]" Test with a simple GET to their queue endpoint (e.g., /status) ⚙️ Configuration Steps Import the workflow JSON into your n8n instance Assign OpenAI API credentials to the "OpenAI Chat Model" node Assign Fal.ai HTTP Header Auth to the "Generate Music Track", "Check Generation Status", and "Fetch Final Result" nodes Activate the workflow—chat trigger will appear in your n8n chat interface Test by messaging: "Create an upbeat pop song about road trips" 🎯 Use Cases Content Creators: YouTubers generating custom jingles for videos on the fly, streamlining production from idea to audio export Educators: Music teachers using chat prompts to create era-specific folk tunes for classroom discussions, fostering interactive learning Gift Personalization: Friends crafting anniversary R&B tracks from shared memories via quick chats, delivering emotional audio surprises Artist Brainstorming: Songwriters prototyping hip-hop beats in real-time during sessions, accelerating collaboration and iteration ⚠️ Troubleshooting Invalid JSON from AI Agent: Ensure the system prompt stresses valid JSON; test the agent standalone with a sample query Music Generation Fails (401/403): Verify Fal.ai API key has minimax-music access; check usage quotas in dashboard Status Polling Loops Indefinitely: Bump wait time to 45-60s for complex tracks; inspect fal.ai queue logs for bottlenecks Lyrics Under 600 Characters: Tweak agent prompt to enforce fuller structures like [V1][C][V2][B][C]; verify output length in executions

Daniel NkenchoBy Daniel Nkencho
601

Automate invoice processing with OCR, GPT-4 & Salesforce opportunity creation

PDF Invoice Extractor (AI) End-to-end pipeline: Watch Drive ➜ Download PDF ➜ OCR text ➜ AI normalize to JSON ➜ Upsert Buyer (Account) ➜ Create Opportunity ➜ Map Products ➜ Create OLI via Composite API ➜ Archive to OneDrive. --- Node by node (what it does & key setup) 1) Google Drive Trigger Purpose: Fire when a new file appears in a specific Google Drive folder. Key settings: Event: fileCreated Folder ID: google drive folder id Polling: everyMinute Creds: googleDriveOAuth2Api Output: Metadata { id, name, ... } for the new file. --- 2) Download File From Google Purpose: Get the file binary for processing and archiving. Key settings: Operation: download File ID: ={{ $json.id }} Creds: googleDriveOAuth2Api Output: Binary (default key: data) and original metadata. --- 3) Extract from File Purpose: Extract text from PDF (OCR as needed) for AI parsing. Key settings: Operation: pdf OCR: enable for scanned PDFs (in options) Output: JSON with OCR text at {{ $json.text }}. --- 4) Message a model (AI JSON Extractor) Purpose: Convert OCR text into strict normalized JSON array (invoice schema). Key settings: Node: @n8n/n8n-nodes-langchain.openAi Model: gpt-4.1 (or gpt-4.1-mini) Message role: system (the strict prompt; references {{ $json.text }}) jsonOutput: true Creds: openAiApi Output (per item): $.message.content → the parsed JSON (ensure it’s an array). --- 5) Create or update an account (Salesforce) Purpose: Upsert Buyer as Account using an external ID. Key settings: Resource: account Operation: upsert External Id Field: taxid_c External Id Value: ={{ $json.message.content.buyer.tax_id }} Name: ={{ $json.message.content.buyer.name }} Creds: salesforceOAuth2Api Output: Account record (captures Id) for downstream Opportunity. --- 6) Create an opportunity (Salesforce) Purpose: Create Opportunity linked to the Buyer (Account). Key settings: Resource: opportunity Name: ={{ $('Message a model').item.json.message.content.invoice.code }} Close Date: ={{ $('Message a model').item.json.message.content.invoice.issue_date }} Stage: Closed Won Amount: ={{ $('Message a model').item.json.message.content.summary.grand_total }} AccountId: ={{ $json.id }} (from Upsert Account output) Creds: salesforceOAuth2Api Output: Opportunity Id for OLI creation. --- 7) Build SOQL (Code / JS) Purpose: Collect unique product codes from AI JSON and build a SOQL query for PricebookEntry by Pricebook2Id. Key settings: pricebook2Id (hardcoded in script): e.g., 01sxxxxxxxxxxxxxxx Source lines: $('Message a model').first().json.message.content.products Output: { soql, codes } --- 8) Query PricebookEntries (Salesforce) Purpose: Fetch PricebookEntry.Id for each Product2.ProductCode. Key settings: Resource: search Query: ={{ $json.soql }} Creds: salesforceOAuth2Api Output: Items with Id, Product2.ProductCode (used for mapping). --- 9) Code in JavaScript (Build OLI payloads) Purpose: Join lines with PBE results and Opportunity Id ➜ build OpportunityLineItem payloads. Inputs: OpportunityId: ={{ $('Create an opportunity').first().json.id }} Lines: ={{ $('Message a model').first().json.message.content.products }} PBE rows: from previous node items Output: { body: { allOrNone:false, records:[{ OpportunityLineItem... }] } } Notes: Converts discount_total ➜ per-unit if needed (currently commented for standard pricing). Throws on missing PBE mapping or empty lines. --- 10) Create Opportunity Line Items (HTTP Request) Purpose: Bulk create OLIs via Salesforce Composite API. Key settings: Method: POST URL: https://<your-instance>.my.salesforce.com/services/data/v65.0/composite/sobjects Auth: salesforceOAuth2Api (predefined credential) Body (JSON): ={{ $json.body }} Output: Composite API results (per-record statuses). --- 11) Update File to One Drive Purpose: Archive the original PDF in OneDrive. Key settings: Operation: upload File Name: ={{ $json.name }} Parent Folder ID: onedrive folder id Binary Data: true (from the Download node) Creds: microsoftOneDriveOAuth2Api Output: Uploaded file metadata. --- Data flow (wiring) Google Drive Trigger → Download File From Google Download File From Google → Extract from File → Update File to One Drive Extract from File → Message a model Message a model → Create or update an account Create or update an account → Create an opportunity Create an opportunity → Build SOQL Build SOQL → Query PricebookEntries Query PricebookEntries → Code in JavaScript Code in JavaScript → Create Opportunity Line Items --- Quick setup checklist 🔐 Credentials: Connect Google Drive, OneDrive, Salesforce, OpenAI. 📂 IDs: Drive Folder ID (watch) OneDrive Parent Folder ID (archive) Salesforce Pricebook2Id (in the JS SOQL builder) 🧠 AI Prompt: Use the strict system prompt; jsonOutput = true. 🧾 Field mappings: Buyer tax id/name → Account upsert fields Invoice code/date/amount → Opportunity fields Product name must equal your Product2.ProductCode in SF. ✅ Test: Drop a sample PDF → verify: AI returns array JSON only Account/Opportunity created OLI records created PDF archived to OneDrive --- Notes & best practices If PDFs are scans, enable OCR in Extract from File. If AI returns non-JSON, keep “Return only a JSON array” as the last line of the prompt and keep jsonOutput enabled. Consider adding validation on parsing.warnings to gate Salesforce writes. For discounts/taxes in OLI: Standard OLI fields don’t support per-line discount amounts directly; model them in UnitPrice or custom fields. Replace the Composite API URL with your org’s domain or use the Salesforce node’s Bulk Upsert for simplicity.

Le NguyenBy Le Nguyen
942