Generate videos from text prompts using GPT-5 and Google Veo-3
This workflow contains community nodes that are only compatible with the self-hosted version of n8n.
π¬ GPT-5 Cinematic Video Generator (n8n + AI/ML API + Google Veo-3) This n8n workflow transforms even a single word into a fully rendered cinematic video using Google Veo-3 image-to-video and prompt expansion with GPT-5. Ideal for rapid creative prototyping, content creation, and AI-driven video production.
π Key Features
- Ultra-Short Input Ready β Works with just one keyword or a short idea.
- AI Prompt Expansion β GPT-5 adds cinematic elements: camera motion, mood, color palette, and composition.
- Automated Video Generation β Veo-3 i2v model creates smooth, visually appealing clips.
- Smart Polling β Waits until video is ready, with success/fail handling.
- Direct Output β Returns ready-to-use video URL for download or publishing.
π Setup Guide
-
Create AI/ML API Credentials
- Get your API key from AI/ML API Keys.
- In n8n > Credentials, add AI/ML account (Bearer token).
-
(Optional) Change Image Source
- Edit the
Set image URLnode to point to your desired still image for video generation.
- Edit the
-
Run from Chat
- Send a word or short phrase via Chat Trigger to start the process.
-
(Optional) Extend Output
- Add Google Drive upload, YouTube publish, or database logging nodes for a complete content pipeline.
π‘ How It Works
- Trigger β Receives chat input (keyword or brief).
- Prompt Expansion β GPT-5 turns it into a cinematic, Veo-3-optimized description.
- Video Creation β Sends prompt + image to Veo-3 image-to-video.
- Polling β Checks generation status every 30 seconds until complete.
- Result β Returns direct video URL, ready for your next steps.
n8n Chat-Driven Workflow Template
This n8n workflow provides a foundational template for creating chat-driven automations. It listens for incoming chat messages and includes basic logic to process them, demonstrating how to integrate chat interactions with workflow automation.
What it does
This workflow is a starting point for building interactive chat automations. It currently performs the following steps:
- Listens for Chat Messages: The workflow is triggered whenever a chat message is received through a configured chat service.
- Edits Fields: It includes a placeholder to edit or transform fields from the incoming chat message, allowing for data manipulation.
- Conditional Logic: An 'If' node is present to introduce conditional branching, enabling different actions based on the content or context of the chat message.
- Waits (Optional): A 'Wait' node is included, which can be configured to pause the workflow for a specified duration, useful for rate limiting or waiting for external processes.
- Makes HTTP Requests: It contains an HTTP Request node, demonstrating how to make API calls to external services based on chat input.
- Handles Errors: A 'Stop and Error' node is available on one branch of the conditional logic, showing how to gracefully stop the workflow and report an error if certain conditions are met.
Prerequisites/Requirements
To use this workflow, you will need:
- n8n Instance: A running n8n instance.
- Chat Service Integration: A configured chat service (e.g., Slack, Telegram, Discord, etc.) connected to the "Chat Trigger" node. This typically involves setting up credentials for the chosen chat platform within n8n.
Setup/Usage
- Import the Workflow:
- Download the provided JSON file.
- In your n8n instance, click on "Workflows" in the left sidebar.
- Click "New" and then "Import from JSON".
- Paste the JSON content or upload the file.
- Configure Chat Trigger:
- Locate the "When chat message received" node.
- Click on it to open its settings.
- Select or create credentials for your desired chat service (e.g., Slack, Telegram).
- Follow the specific instructions for your chosen chat service to connect it to n8n.
- Customize Workflow Logic:
- Edit Fields (Set): Modify this node to extract, transform, or set specific data points from the incoming chat message (
{{ $json.text }}for the message content, for example). - If Node: Configure the conditions in the "If" node to define different paths based on chat message content (e.g., if message contains "hello", if user is admin).
- HTTP Request: Adjust the "HTTP Request" node to call external APIs relevant to your automation (e.g., a GPT-5 API for text generation, a Google Veo 3 API for video generation, although these specific integrations are not pre-configured in this generic template).
- Wait Node: Configure the delay if needed.
- Stop and Error: Customize the error message if the workflow takes this path.
- Edit Fields (Set): Modify this node to extract, transform, or set specific data points from the incoming chat message (
- Activate the Workflow:
- Once configured, ensure the workflow is active by toggling the "Active" switch in the top right corner of the workflow editor.
This template provides a flexible starting point. You can expand upon it by adding more nodes for advanced processing, database interactions, notifications, and more, to create powerful chat-driven automations.
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.
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
Automate Dutch Public Procurement Data Collection with TenderNed
TenderNed Public Procurement What This Workflow Does This workflow automates the collection of public procurement data from TenderNed (the official Dutch tender platform). It: Fetches the latest tender publications from the TenderNed API Retrieves detailed information in both XML and JSON formats for each tender Parses and extracts key information like organization names, titles, descriptions, and reference numbers Filters results based on your custom criteria Stores the data in a database for easy querying and analysis Setup Instructions This template comes with sticky notes providing step-by-step instructions in Dutch and various query options you can customize. Prerequisites TenderNed API Access - Register at TenderNed for API credentials Configuration Steps Set up TenderNed credentials: Add HTTP Basic Auth credentials with your TenderNed API username and password Apply these credentials to the three HTTP Request nodes: "Tenderned Publicaties" "Haal XML Details" "Haal JSON Details" Customize filters: Modify the "Filter op ..." node to match your specific requirements Examples: specific organizations, contract values, regions, etc. How It Works Step 1: Trigger The workflow can be triggered either manually for testing or automatically on a daily schedule. Step 2: Fetch Publications Makes an API call to TenderNed to retrieve a list of recent publications (up to 100 per request). Step 3: Process & Split Extracts the tender array from the response and splits it into individual items for processing. Step 4: Fetch Details For each tender, the workflow makes two parallel API calls: XML endpoint - Retrieves the complete tender documentation in XML format JSON endpoint - Fetches metadata including reference numbers and keywords Step 5: Parse & Merge Parses the XML data and merges it with the JSON metadata and batch information into a single data structure. Step 6: Extract Fields Maps the raw API data to clean, structured fields including: Publication ID and date Organization name Tender title and description Reference numbers (kenmerk, TED number) Step 7: Filter Applies your custom filter criteria to focus on relevant tenders only. Step 8: Store Inserts the processed data into your database for storage and future analysis. Customization Tips Modify API Parameters In the "Tenderned Publicaties" node, you can adjust: offset: Starting position for pagination size: Number of results per request (max 100) Add query parameters for date ranges, status filters, etc. Add More Fields Extend the "Splits Alle Velden" node to extract additional fields from the XML/JSON data, such as: Contract value estimates Deadline dates CPV codes (procurement classification) Contact information Integrate Notifications Add a Slack, Email, or Discord node after the filter to get notified about new matching tenders. Incremental Updates Modify the workflow to only fetch new tenders by: Storing the last execution timestamp Adding date filters to the API query Only processing publications newer than the last run Troubleshooting No data returned? Verify your TenderNed API credentials are correct Check that you have setup youre filter proper Need help setting this up or interested in a complete tender analysis solution? Get in touch π LinkedIn β Wessel Bulte