Auto-generate AI videos with Gemini, KIE AI Sora-2 & Blotato (Multi-Platform)
Overview
This n8n template automates the entire process of generating short-form AI videos and publishing them across multiple social media platforms. It combines Google Gemini for structured prompt creation, KIE AI for video generation, and Blotato for centralized publishing. The result is a fully automated content pipeline ideal for creators, marketers, agencies, or anyone who wants consistent, hands-free content generation.
This workflow is especially useful for short-video creators, meme pages, educational creators, UGC teams, auto-posting accounts, and brands who want to maintain high-frequency posting without manual effort.
Good to Know
- API costs: KIE AI generates videos using paid tokens/credits. Prices vary based on model, duration, and resolution (check KIE AI pricing).
- Google Gemini model restrictions: Certain Gemini models are geo-limited. If you receive “model not found,” the model may not be available in your region.
- Blotato publishing: Blotato supports many platforms: YouTube, Instagram, Facebook, LinkedIn, TikTok, X, Bluesky, and more. Platform availability depends on your Blotato setup.
- Runtime considerations: Video generation can take time (10–60 seconds+, depending on the complexity).
- Self-hosted requirement: This workflow uses a community node (Blotato). Community nodes do not run on n8n Cloud. A self-hosted instance is required.
How It Works
-
Scheduler Trigger Defines how frequently new videos should be created (e.g., every 12 hours).
-
Random Template Selector A JavaScript node generates a random number to choose from multiple creative prompt templates.
-
AI Agent (Google Gemini) Gemini generates a JSON object containing:
- A short title
- A human-readable video description
- A detailed text-to-video prompt
The Structured Output Parser ensures strict JSON shape.
-
Video Generation with KIE AI The prompt is sent to KIE AI’s video generation API. KIE AI creates a synthetic AI video based on the description and your chosen parameters (aspect ratio, frames, watermark removal, etc.).
-
Polling & Retrieval The workflow waits until the video is fully rendered, then fetches the final video URL.
-
Media Upload to Blotato The generated video is uploaded into Blotato’s media storage for publishing.
-
Automatic Posting to Social Platforms Blotato distributes the video to all connected platforms. Examples include:
- YouTube
- Bluesky
- TikTok
- X
- Any platform supported by your Blotato account
This results in a fully automated “idea → video → upload → publish” pipeline.
How to Use
-
Start by testing the workflow manually to verify video generation and posting.
-
Adjust the Scheduler Trigger to fit your posting frequency.
-
Add your API credentials for:
- Google Gemini
- KIE AI
- Blotato
-
Ensure your Blotato account has social channels connected.
-
Edit or expand the prompt templates for your content niche:
- Comedy clips
- Educational videos
- Product demos
- Storytelling
- Pet videos
- Motivational content
The more template prompts you add, the more diverse your automated videos will be.
Requirements
- Google Gemini API Key Used for generating structured titles, descriptions, and video prompts.
- KIE AI API key Required for creating the actual AI-generated video.
- Blotato account Required for uploading media and automatically posting to platforms.
- Self-hosted n8n instance Needed because Blotato uses a community node, which n8n Cloud does not support.
Limitations
- KIE AI models may output inconsistent results if prompts are vague.
- High-frequency scheduling may consume API credits quickly.
- Some platforms (e.g., TikTok or Facebook Pages) may require additional permissions or account linking steps in Blotato.
- Video rendering time varies depending on prompt complexity.
Customization Ideas
-
Add more prompt templates to increase variety.
-
Swap Gemini for an LLM of your choice (OpenAI, Claude, etc.).
-
Add a Telegram, Discord, or Slack notification once posting is complete.
-
Store all generated titles, descriptions, and video URLs in:
- Google Sheets
- Notion
- Airtable
- Supabase
-
Add multi-language support using a translation node.
-
Add an approval step where videos go to your team before publishing.
-
Add analytics logging (impressions, views, etc.) using Blotato or another service.
Troubleshooting
- Video not generating? Check if your KIE AI model accepts your chosen parameters.
- Model not found? Switch to a supported Gemini model for your region.
- Publishing fails? Ensure Blotato platform accounts are authenticated.
- Workflow stops early? Increase the wait timeout before polling KIE AI.
This template is designed for easy setup and high flexibility. All technical details, configuration steps, and workflow logic are already included in sticky notes inside the workflow. Once configured, this pipeline becomes a hands-free AI-powered content engine capable of generating and publishing content at scale.
n8n AI Video Generation Workflow with Google Gemini
This n8n workflow automates the process of generating video scripts and potentially video content using AI. It leverages Google Gemini for creative content generation and includes steps for structured output parsing, external API calls, and scheduled execution.
What it does
This workflow streamlines the creation of video content by:
- Triggering on a Schedule: The workflow starts automatically at predefined intervals.
- Generating AI Content: It uses an AI Agent (powered by Google Gemini) to generate creative content, likely video ideas or scripts, based on an internal prompt.
- Parsing Structured Output: It then processes the AI-generated output to extract structured data, ensuring the content is in a usable format (e.g., JSON).
- Making an HTTP Request: An HTTP Request node is included, suggesting an interaction with an external API. This could be to send the generated script to a video generation service (like Kie AI or Sora 2), publish the content, or store it.
- Introducing a Delay: A "Wait" node is used, which pauses the workflow for a specified duration. This is often used to manage API rate limits, allow time for external processes to complete, or introduce a delay between actions.
- Custom Logic (Code Node): A "Code" node is present, indicating that custom JavaScript logic can be executed within the workflow. This allows for advanced data manipulation, conditional logic, or integration with services not directly supported by n8n nodes.
Prerequisites/Requirements
- n8n Instance: A running n8n instance to import and execute the workflow.
- Google Gemini API Key: Credentials for the Google Gemini Chat Model to allow the AI Agent to function.
- External API Credentials: Depending on the HTTP Request node's configuration, you might need API keys or tokens for the external service it interacts with (e.g., a video generation platform, a content management system).
Setup/Usage
- Import the Workflow: Download the provided JSON and import it into your n8n instance.
- Configure Credentials:
- Google Gemini Chat Model: Edit the "Google Gemini Chat Model" node and configure your Google Gemini credentials.
- HTTP Request: If the "HTTP Request" node requires authentication, update its credentials or add necessary headers/body parameters.
- Review AI Agent Prompt: Inspect the "AI Agent" node to understand and potentially modify the prompt used to generate video content.
- Adjust Schedule: Modify the "Schedule Trigger" node to set your desired execution frequency.
- Customize Code Node: If needed, update the JavaScript code in the "Code" node to fit your specific requirements for data processing or integration.
- Activate the Workflow: Once configured, activate the workflow to enable scheduled execution.
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 DailataGenerate 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 NkenchoAutomate 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
By Wessel Bulte