HumationHuman + Automation
Back to Catalog

Generate animal battle videos with Flux AI, Creatomate & multi-platform publishing

Jadai kongoloJadai kongolo
188 views
2/3/2026
NotificationSlackGitLabWebhookCI/CD
Official Page

Author: Jadai Kongolo

Overview

This comprehensive n8n workflow automates the entire production pipeline for creating viral "versus" style battle videos. The system generates dramatic AI-powered fight scenes between animals (or any characters you choose), complete with photorealistic imagery, cinematic effects, and automatic multi-platform publishing. Perfect for content creators looking to generate engaging short-form content at scale without manual editing or design work.

Use Cases

  1. Viral Social Media Content: Automatically produce trending "X vs Y" battle videos that perform exceptionally well on TikTok, Instagram Reels, and YouTube Shorts. These comparison-style videos consistently generate high engagement and shares.

  2. Educational Entertainment: Create visually stunning educational content comparing animals, historical figures, sports teams, or any competitive matchups while maintaining viewer interest through dramatic AI-generated imagery.

  3. Automated Content Pipeline: Build a hands-free content factory that can produce multiple videos per day on schedule, complete with automatic posting to all major social platforms through integrated social media management tools.

👉 check out the UGC version of this here

How It Works

Stage 1 - Scene Generation

The workflow begins by fetching a main character from your Google Sheets database (filtered by "To Do" status). An AI agent powered by GPT-4.1-mini then generates eight unique opponents from your specified category, ensuring each comes from a different environment or background for maximum variety and interest.

Stage 2 - AI Image Creation

The system creates three distinct types of images for each matchup:

Close-Up Portraits: Generates fierce, intimidating close-up shots of both the main character and each opponent using Flux image generation through PiAPI. The AI creates hyper-realistic, photorealistic images showing each character roaring with detailed textures, dramatic lighting, and threatening expressions.

Battle Aftermath Scenes: A separate AI agent determines the realistic winner based on each character's strengths, then generates a dramatic full-body scene showing the victor standing dominantly over the defeated opponent. These images include visible battle scars, wounds, and cinematic composition that makes the outcome unmistakably clear.

The workflow includes intelligent polling mechanisms (90-second waits) to ensure all images are fully generated before proceeding, then aggregates and stores all image URLs in your Google Sheet for reference.

Stage 3 - Video Assembly

Using Creatomate's video rendering API, the workflow combines all generated images with background music and animated transitions into a polished final video. The template creates a fast-paced montage showing all eight battles with "VS" graphics and dynamic cuts timed to music beats.

Stage 4 - Multi-Platform Publishing

Once rendered, the video is automatically uploaded to Blotato's social media management platform and simultaneously published to:

  • Instagram Reels with optimized captions
  • TikTok with proper AI-generated content disclosure
  • YouTube Shorts as unlisted for review

The workflow updates your Google Sheet with "Created" status and final video URL for tracking and analytics.

Customization Options

Content Themes

  • Modify the Google Sheet to change from animals to any category: superheroes, historical warriors, vehicles, mythical creatures, sports teams, etc.
  • Adjust AI prompts in the "Scene Creator" node to control opponent selection criteria
  • Edit the "Image Prompt Generator" to customize visual style (fantasy, sci-fi, realistic, cartoon, etc.)

Video Production

  • Change video dimensions in "Generate Close Ups" and "Generate Scene" nodes for different platform requirements
  • Replace the Creatomate template with your own design for different visual styles
  • Swap background music by updating the music source URL in the "Render Video" node
  • Adjust the number of battles per video (currently 8 scenes)

Publishing Settings

  • Configure posting schedules via the Schedule Trigger node
  • Modify platform-specific settings (privacy levels, comments, duets) in Instagram/TikTok/YouTube nodes
  • Add or remove social platforms by connecting additional Blotato API endpoints
  • Customize captions using data from your Google Sheet

AI Models

  • Switch between different OpenRouter models for cost/quality tradeoffs
  • Use GPT-4.1 for complex winner determination and GPT-4.1-mini for faster scene generation
  • Experiment with different Flux models through PiAPI for various artistic styles

Prerequisites

  • Google Sheets: Connected Google account with access to the workflow template
  • OpenRouter API: For GPT-4.1 and GPT-4.1-mini access
  • PiAPI Account: For Flux image generation (use referral code for bonus credits)
  • Creatomate Account: For video rendering with template access
  • Blotato Account: For multi-platform social media publishing (use promo code "NATE30" for 30% off for 6 months)

🛠️ Setup Guide

  1. Make a copy of this Google Sheet Template and connect it to the five Google Sheet nodes in the workflow:

    • Get Main Character
    • Add Close Ups
    • Add Winner
    • Get Elements
    • Update Video Status

  2. Connect your OpenRouter API key to the two OpenRouter nodes in the "Output Parser & Chat Models" section:

    • GPT 4.1-mini
    • GPT 4.1

  3. Create a PiAPI account and connect your API key to:

    • Generate Close Ups
    • Generate Scene
    • Get Close Ups
    • Get Winners

  4. Create a Creatomate account and connect your template ID and API key to the Render Video node.
    You can duplicate the same template shown in the video by using the source code linked in the same Skool post where you downloaded the workflow.

  5. Connect your Blotato account and get your API key to enable auto-publishing:

    • Configure the Upload to Blotato node
    • Add your account IDs to Instagram, TikTok, and YouTube nodes

  6. Customize the Schedule Trigger node to set your desired posting frequency (daily, weekly, etc.)

The Generate authentic, influencer-style UGC videos on autopilot version of this AI video generator can be found here.

Generate Animal Battle Videos with Flux AI & Creatomate (Multi-Platform Publishing)

This n8n workflow automates the creation of engaging animal battle videos using AI-generated content and a video automation platform, then prepares them for multi-platform publishing. It leverages a Google Sheet as the source for animal battle prompts and uses an AI agent to generate video script details, which are then used to create videos via an external API.

What it does

  1. Triggers on a Schedule: The workflow starts on a predefined schedule (e.g., daily, weekly) to check for new battle prompts.
  2. Reads Battle Prompts: It fetches animal battle scenarios from a specified Google Sheet.
  3. Generates Video Script with AI: For each battle prompt, an AI Agent (powered by LangChain and OpenRouter) is used to generate a detailed video script, including:
    • videoTitle: A catchy title for the battle video.
    • animal1Name, animal2Name: The names of the two animals battling.
    • animal1Description, animal2Description: Descriptions of each animal.
    • battleScenario: A detailed description of the battle.
    • winner: The declared winner of the battle.
    • videoScript: The full script for the video.
    • hashtags: Relevant hashtags for social media.
  4. Prepares Data for Video Creation: The generated AI script details are transformed and set into the appropriate format for the video creation API.
  5. Creates Video with Creatomate (via HTTP Request): An HTTP Request node sends the prepared data to a video automation platform (e.g., Creatomate) to generate the actual video.
  6. Waits for Video Processing: The workflow pauses, allowing time for the video to be processed and rendered by the video automation platform.
  7. Retrieves Video URL: After the wait, it makes another HTTP Request to fetch the final video URL from the video automation platform.
  8. Merges Data: The original battle prompt data is merged with the generated video script and the final video URL.
  9. Updates Google Sheet: The workflow writes the generated video title, script, and URL back to the Google Sheet, marking the battle as processed and providing a link to the created video.

Prerequisites/Requirements

  • n8n Instance: A running n8n instance.
  • Google Sheets Account: To store and retrieve animal battle prompts.
  • OpenRouter API Key: For the AI Agent to access various large language models.
  • Creatomate (or similar video automation platform) Account and API Key: To generate videos based on the AI-generated scripts. The HTTP Request nodes are configured to interact with such a platform.
  • AI Agent Credentials: Configured within n8n for the AI Agent node.

Setup/Usage

  1. Import the Workflow: Download the provided JSON and import it into your n8n instance.
  2. Configure Credentials:
    • Google Sheets: Set up your Google Sheets credential to allow n8n to read from and write to your spreadsheet.
    • OpenRouter: Configure your OpenRouter API key credential.
    • HTTP Request (Creatomate/Video Platform): Set up the necessary API key or authentication for your chosen video automation platform within the HTTP Request nodes.
  3. Configure Google Sheet Node (ID: 18):
    • Specify the Spreadsheet ID of your Google Sheet.
    • Ensure the Sheet Name is correct.
    • Verify the Range for reading and writing data.
    • Make sure your Google Sheet has columns corresponding to the data being read and written (e.g., Animal 1, Animal 2, Video Title, Video Script, Video URL, Status).
  4. Configure AI Agent Node (ID: 1119):
    • Select your OpenRouter Chat Model credential.
    • Review the prompt and ensure it aligns with your desired video script output.
  5. Configure HTTP Request Nodes (ID: 19):
    • Video Creation: Update the URL and body to match your video automation platform's API for creating videos.
    • Video Retrieval: Update the URL and any necessary parameters to match your video automation platform's API for checking video status or retrieving the final URL.
  6. Configure Schedule Trigger (ID: 839): Adjust the schedule to your desired frequency for generating videos.
  7. Activate the Workflow: Once all configurations are complete, activate the workflow.

Related Templates

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

Wessel BulteBy Wessel Bulte
247

🎓 How to transform unstructured email data into structured format with AI agent

This workflow automates the process of extracting structured, usable information from unstructured email messages across multiple platforms. It connects directly to Gmail, Outlook, and IMAP accounts, retrieves incoming emails, and sends their content to an AI-powered parsing agent built on OpenAI GPT models. The AI agent analyzes each email, identifies relevant details, and returns a clean JSON structure containing key fields: From – sender’s email address To – recipient’s email address Subject – email subject line Summary – short AI-generated summary of the email body The extracted information is then automatically inserted into an n8n Data Table, creating a structured database of email metadata and summaries ready for indexing, reporting, or integration with other tools. --- Key Benefits ✅ Full Automation: Eliminates manual reading and data entry from incoming emails. ✅ Multi-Source Integration: Handles data from different email providers seamlessly. ✅ AI-Driven Accuracy: Uses advanced language models to interpret complex or unformatted content. ✅ Structured Storage: Creates a standardized, query-ready dataset from previously unstructured text. ✅ Time Efficiency: Processes emails in real time, improving productivity and response speed. *✅ Scalability: Easily extendable to handle additional sources or extract more data fields. --- How it works This workflow automates the transformation of unstructured email data into a structured, queryable format. It operates through a series of connected steps: Email Triggering: The workflow is initiated by one of three different email triggers (Gmail, Microsoft Outlook, or a generic IMAP account), which constantly monitor for new incoming emails. AI-Powered Parsing & Structuring: When a new email is detected, its raw, unstructured content is passed to a central "Parsing Agent." This agent uses a specified OpenAI language model to intelligently analyze the email text. Data Extraction & Standardization: Following a predefined system prompt, the AI agent extracts key information from the email, such as the sender, recipient, subject, and a generated summary. It then forces the output into a strict JSON structure using a "Structured Output Parser" node, ensuring data consistency. Data Storage: Finally, the clean, structured data (the from, to, subject, and summarize fields) is inserted as a new row into a specified n8n Data Table, creating a searchable and reportable database of email information. --- Set up steps To implement this workflow, follow these configuration steps: Prepare the Data Table: Create a new Data Table within n8n. Define the columns with the following names and string type: From, To, Subject, and Summary. Configure Email Credentials: Set up the credential connections for the email services you wish to use (Gmail OAuth2, Microsoft Outlook OAuth2, and/or IMAP). Ensure the accounts have the necessary permissions to read emails. Configure AI Model Credentials: Set up the OpenAI API credential with a valid API key. The workflow is configured to use the model, but this can be changed in the respective nodes if needed. Connect the Nodes: The workflow canvas is already correctly wired. Visually confirm that the email triggers are connected to the "Parsing Agent," which is connected to the "Insert row" (Data Table) node. Also, ensure the "OpenAI Chat Model" and "Structured Output Parser" are connected to the "Parsing Agent" as its AI model and output parser, respectively. Activate the Workflow: Save the workflow and toggle the "Active" switch to ON. The triggers will begin polling for new emails according to their schedule (e.g., every minute), and the automation will start processing incoming messages. --- Need help customizing? Contact me for consulting and support or add me on Linkedin.

DavideBy Davide
1616

Document RAG & chat agent: Google Drive to Qdrant with Mistral OCR

Knowledge RAG & AI Chat Agent: Google Drive to Qdrant Description This workflow transforms a Google Drive folder into an intelligent, searchable knowledge base and provides a chat agent to query it. It’s composed of two distinct flows: An ingestion pipeline to process documents. A live chat agent that uses RAG (Retrieval-Augmented Generation) and optional web search to answer user questions. This system fully automates the creation of a “Chat with your docs” solution and enhances it with external web-searching capabilities. --- Quick Implementation Steps Import the workflow JSON into your n8n instance. Set up credentials for Google Drive, Mistral AI, OpenAI, and Qdrant. Open the Web Search node and add your Tavily AI API key to the Authorization header. In the Google Drive (List Files) node, set the Folder ID you want to ingest. Run the workflow manually once to populate your Qdrant database (Flow 1). Activate the workflow to enable the chat trigger (Flow 2). Copy the public webhook URL from the When chat message received node and open it in a new tab to start chatting. --- What It Does The workflow is divided into two primary functions: Knowledge Base Ingestion (Manual Trigger) This flow populates your vector database. Scans Google Drive: Lists all files from a specified folder. Processes Files Individually: Downloads each file. Extracts Text via OCR: Uses Mistral AI OCR API for text extraction from PDFs, images, etc. Generates Smart Metadata: A Mistral LLM assigns metadata like documenttype, project, and assignedto. Chunks & Embeds: Text is cleaned, chunked, and embedded via OpenAI’s text-embedding-3-small model. Stores in Qdrant: Text chunks, embeddings, and metadata are stored in a Qdrant collection (docaiauto). AI Chat Agent (Chat Trigger) This flow powers the conversational interface. Handles User Queries: Triggered when a user sends a chat message. Internal RAG Retrieval: Searches Qdrant Vector Store first for answers. Web Search Fallback: If unavailable internally, the agent offers to perform a Tavily AI web search. Contextual Responses: Combines internal and external info for comprehensive answers. --- Who's It For Ideal for: Teams building internal AI knowledge bases from Google Drive. Developers creating AI-powered support, research, or onboarding bots. Organizations implementing RAG pipelines. Anyone making unstructured Google Drive documents searchable via chat. --- Requirements n8n instance (self-hosted or cloud). Google Drive Credentials (to list and download files). Mistral AI API Key (for OCR & metadata extraction). OpenAI API Key (for embeddings and chat LLM). Qdrant instance (cloud or self-hosted). Tavily AI API Key (for web search). --- How It Works The workflow runs two independent flows in parallel: Flow 1: Ingestion Pipeline (Manual Trigger) List Files: Fetch files from Google Drive using the Folder ID. Loop & Download: Each file is processed one by one. OCR Processing: Upload file to Mistral Retrieve signed URL Extract text using Mistral DOC OCR Metadata Extraction: Analyze text using a Mistral LLM. Text Cleaning & Chunking: Split into 1000-character chunks. Embeddings Creation: Use OpenAI embeddings. Vector Insertion: Push chunks + metadata into Qdrant. Flow 2: AI Chat Agent (Chat Trigger) Chat Trigger: Starts when a chat message is received. AI Agent: Uses OpenAI + Simple Memory to process context. RAG Retrieval: Queries Qdrant for related data. Decision Logic: Found → Form answer. Not found → Ask if user wants web search. Web Search: Performs Tavily web lookup. Final Response: Synthesizes internal + external info. --- How To Set Up Import the Workflow Upload the provided JSON into your n8n instance. Configure Credentials Create and assign: Google Drive → Google Drive nodes Mistral AI → Upload, Signed URL, DOC OCR, Cloud Chat Model OpenAI → Embeddings + Chat Model nodes Qdrant → Vector Store nodes Add Tavily API Key Open Web Search node → Parameters → Headers Add your key under Authorization (e.g., tvly-xxxx). Node Configuration Google Drive (List Files): Set Folder ID. Qdrant Nodes: Ensure same collection name (docaiauto). Run Ingestion (Flow 1) Click Test workflow to populate Qdrant with your Drive documents. Activate Chat (Flow 2) Toggle the workflow ON to enable real-time chat. Test Open the webhook URL and start chatting! --- How To Customize Change LLMs: Swap models in OpenAI or Mistral nodes (e.g., GPT-4o, Claude 3). Modify Prompts: Edit the system message in ai chat agent to alter tone or logic. Chunking Strategy: Adjust chunkSize and chunkOverlap in the Code node. Different Sources: Replace Google Drive with AWS S3, Local Folder, etc. Automate Updates: Add a Cron node for scheduled ingestion. Validation: Add post-processing steps after metadata extraction. Expand Tools: Add more functional nodes like Google Calendar or Calculator. --- Use Case Examples Internal HR Bot: Answer HR-related queries from stored policy docs. Tech Support Assistant: Retrieve troubleshooting steps for products. Research Assistant: Summarize and compare market reports. Project Management Bot: Query document ownership or project status. --- Troubleshooting Guide | Issue | Possible Solution | |------------|------------------------| | Chat agent doesn’t respond | Check OpenAI API key and model availability (e.g., gpt-4.1-mini). | | Known documents not found | Ensure ingestion flow ran and both Qdrant nodes use same collection name. | | OCR node fails | Verify Mistral API key and input file integrity. | | Web search not triggered | Re-check Tavily API key in Web Search node headers. | | Incorrect metadata | Tune Information Extractor prompt or use a stronger Mistral model. | --- Need Help or More Workflows? Want to customize this workflow for your business or integrate it with your existing tools? Our team at Digital Biz Tech can tailor it precisely to your use case from automation logic to AI-powered enhancements. We can help you set it up for free — from connecting credentials to deploying it live. Contact: shilpa.raju@digitalbiz.tech Website: https://www.digitalbiz.tech LinkedIn: https://www.linkedin.com/company/digital-biz-tech/ You can also DM us on LinkedIn for any help. ---

DIGITAL BIZ TECHBy DIGITAL BIZ TECH
1409