Generate video from prompt using Vertex AI Veo 3 and upload to Google Drive

21110 views

2/3/2026

IMAP OpenAI Automation Email Summarization

Who’s it for

This template is perfect for content creators, AI enthusiasts, marketers, and developers who want to automate the generation of cinematic videos using Google Vertex AI’s Veo 3 model. It’s also ideal for anyone experimenting with generative AI for video using n8n.

What it does

This workflow:

Accepts a text prompt and a GCP access token via form.
Sends the prompt to the Veo 3 (preview model) using Vertex AI’s predictLongRunning endpoint.
Waits for the video rendering to complete.
Fetches the final result and converts the base64-encoded video to a file.
Uploads the resulting .mp4 to your Google Drive.

Output

How to set up

Enable Vertex AI API in your GCP project: https://console.cloud.google.com/marketplace/product/google/aiplatform.googleapis.com
Authenticate with GCP using Cloud Shell or local terminal:

gcloud auth login
gcloud config set project [YOUR_PROJECT_ID]
gcloud auth application-default set-quota-project [YOUR_PROJECT_ID]
gcloud auth print-access-token

Copy the token and use it in the form when running the workflow.
⚠️ This token lasts ~1 hour. Regenerate as needed.

Connect your Google Drive OAuth2 credentials to allow file upload.
Import this workflow into n8n and execute it via form trigger.

Requirements

n8n (v1.94.1+)
A Google Cloud project with:
- Vertex AI API enabled
- Billing enabled
A way to get Access Token gcloud auth print-access-token
A Google Drive OAuth2 credential connected to n8n

How to customize the workflow

You can modify the
- durationSeconds
- aspectRatio
- generateAudio
in the HTTP node to match your use case.
Replace the Google Drive upload node with alternatives like Dropbox, S3, or YouTube upload.
Extend the workflow to add subtitles, audio dubbing, or LINE/Slack alerts.

Step-by-step for each major node:

Prompt Input → Vertex Predict → Wait → Fetch Result → Convert to File → Upload

Best Practices Followed

No hardcoded API tokens
Secure: GCP token is input via form, not stored in workflow
All nodes are renamed with clear purpose
All editable config grouped in Set node

External References

GCP Veo API Docs: https://cloud.google.com/vertex-ai/docs/generative-ai/video/overview

Disclaimer

This workflow uses official Google Cloud APIs and requires a valid GCP project.
Access token should be generated securely using gcloud CLI.
Do not embed tokens in the workflow itself.

Notes on GCP Access Token

To use the Vertex AI API in n8n securely:

Run the following on your local machine or GCP Cloud Shell:

gcloud auth login
gcloud config set project your-project-id
gcloud auth print-access-token

Paste the token in the workflow form field YOUR_ACCESS_TOKEN when submitting.
Do not hardcode the token into HTTP nodes or Set nodes — input it each time or use a secure credential vault.

Generate Video from Prompt using Vertex AI Veo 3 and Upload to Google Drive

This n8n workflow automates the process of generating a video from a text prompt using Google Cloud's Vertex AI Veo 3 model and then uploading the generated video file to Google Drive.

What it does

This workflow streamlines the video creation process by:

Receiving a Video Prompt: It starts by accepting a text prompt for video generation via an n8n form submission.
Preparing Request Data: It takes the submitted prompt and formats it into the necessary JSON payload for the Vertex AI API call.
Generating Video with Vertex AI Veo 3: It sends an HTTP request to the Vertex AI Veo 3 API, passing the video prompt to generate a video.
Waiting for Video Generation: It includes a Wait step to allow sufficient time for the video generation process to complete, as AI video generation can be time-consuming.
Converting Video to File: It takes the generated video data (likely a URL or base64 encoded content from the API response) and converts it into a storable file format.
Uploading to Google Drive: Finally, it uploads the generated video file to a specified folder in Google Drive.

Prerequisites/Requirements

To use this workflow, you will need:

n8n Instance: A running n8n instance.
Google Cloud Project with Vertex AI: Access to a Google Cloud project with the Vertex AI API enabled and configured for Veo 3.
Google Cloud Service Account: A service account with appropriate permissions to call the Vertex AI API and upload to Google Drive.
Google Drive Account: A Google Drive account where the generated videos will be stored.
n8n Credentials: Configured n8n credentials for:
- HTTP Request: Potentially for API key or OAuth for Vertex AI.
- Google Drive: OAuth 2.0 credentials for Google Drive.

Setup/Usage

Import the Workflow: Download the provided JSON and import it into your n8n instance.
Configure Credentials:
- Open the HTTP Request node and set up the authentication method for your Vertex AI API. This typically involves an API key or OAuth 2.0 with the correct scopes.
- Open the Google Drive node and configure your Google Drive OAuth 2.0 credentials. Ensure the credentials have permission to create and upload files in your desired Google Drive folder.
Configure Nodes:
- On form submission (Form Trigger): This node provides the URL for the form. Users will submit their video prompts here.
- Edit Fields (Set): This node prepares the data for the HTTP request. Ensure the prompt field correctly maps to the input from the form.
- HTTP Request:
  - Update the URL to point to your specific Vertex AI Veo 3 endpoint.
  - Adjust the Body Parameters to match the Vertex AI Veo 3 API specification, ensuring the prompt is correctly passed.
  - Set the Method to POST.
- Wait: Adjust the Time in the Wait node based on the expected video generation time. Start with a reasonable duration (e.g., 5-10 minutes) and adjust as needed.
- Convert to File: This node will take the binary data or URL of the generated video from the HTTP Request node's output and convert it into a file. Ensure the File Type and File Name are configured appropriately.
- Google Drive:
  - Specify the Folder ID in Google Drive where you want to upload the videos.
  - Ensure the File Name and File Content parameters are correctly mapped from the Convert to File node's output.
Activate the Workflow: Once configured, activate the workflow.
Submit a Prompt: Access the URL provided by the On form submission trigger node and submit a text prompt for your video. The workflow will then execute, generating and uploading the video.

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.

By 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

By 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.

By Le Nguyen

942