HumationHuman + Automation
Back to Catalog

AI content creation and publishing engine with Mistral, Creatomate, and YouTube

NanaBNanaB
3266 views
2/3/2026
Task ManagementDaily TaskAutomationNotionProductivity
Official Page

Description

This n8n workflow automates the entire process of creating and publishing AI-generated videos, triggered by a simple message from a Telegram bot (YTAdmin). It transforms a text prompt into a structured video with scenes, visuals, and voiceover, stores assets in MongoDB, renders the final output using Creatomate, and uploads the video to YouTube. Throughout the process, YTAdmin receives real-time updates on the workflow’s progress. This is ideal for content creators, marketers, or businesses looking to scale video production using automation and AI.

You can see a video demonstrating this template in action here: https://www.youtube.com/watch?v=EjI-ChpJ4xA&t=200s

How it Works

  1. Trigger: Message from YTAdmin (Telegram Bot)
  • The flow starts when YTAdmin sends a content prompt.
  1. Generate Structured Content
  • A Mistral language model processes the input and outputs structured content, typically broken into scenes.
  1. Split & Process Content into Scenes
  • The content is split into categorized parts for scene generation.
  1. Generate Media Assets

  • For each scene:

  • Images: Generated using OpenAI’s image model.

  • Voiceovers: Created using OpenAI’s text-to-speech.

  • Audio files are encoded and stored in MongoDB.

  1. Scene Composition
  • Assets are grouped into coherent scenes.
  1. Render with Creatomate
  • A complete payload is generated and sent to the Creatomate rendering API to produce the video.
  • Progress messages are sent to YTAdmin.
  • The flow pauses briefly to avoid rate limits.
  1. Render Callback
  • Once Creatomate completes rendering, it sends a callback to the flow.
  • If the render fails, an error message is sent to YTAdmin.
  • If the render succeeds, the flow proceeds to post-processing.
  1. Generate Title & Description
  • A second Mistral prompt generates a compelling title and description for YouTube.
  1. Upload to YouTube
  • The rendered video is retrieved from Creatomate.
  • It’s uploaded to YouTube with the AI-generated metadata.
  1. Final Update
  • A success message is sent to YTAdmin, confirming upload completion.

Set Up Steps (Approx. 10–15 Minutes)Step 1: Set Up YTAdmin Bot

  • Create a Telegram bot via BotFather and get your API token.
  • Add this token in n8n's Telegram credentials and link to the "Receive Message from YTAdmin" trigger.

Step 2: Connect Your AI Providers

  • Mistral: Add your API key under HTTP Request or AI Model nodes.
  • OpenAI: Create an account at platform.openai.com and obtain an API key. Use it for both image generation and voiceover synthesis.

Step 3: Configure Audio File Storage with MongoDB via Custom API

  • Receives the Base64 encoded audio data sent in the request body.
  • Connects to the configured MongoDB instance (connection details are managed securely within the API- code below).
  • Uses the MongoDB driver and GridFS to store the audio data.
  • Returns the unique _id (ObjectId) of the stored file in GridFS as a response.
  • This _id is crucial as it will be used in subsequent steps to generate the download URL for the audio file.
  • My API code can be found here for reference: https://github.com/nanabrownsnr/YTAutomation.git

Step 4: Set Up Creatomate

  • Create a Creatomate account, define your video templates, and retrieve your API key.
  • Configure the HTTP request node to match your Creatomate payload requirements.

Step 5: Connect YouTube

  • In n8n, add OAuth2 credentials for your YouTube account.
  • Make sure your Google Cloud project has YouTube Data API enabled.

Step 6: Deploy and Test

  • Send a message to YTAdmin and monitor the flow in n8n.
  • Verify that content is generated, media is created, and the final video is rendered and uploaded.

Customization Options

  1. Change the AI Prompts
  • Modify the generation prompts to adjust tone, voice, or content type (e.g., news recaps, product videos, educational summaries).
  1. Switch Messaging Platform
  • Replace Telegram (YTAdmin) with Slack, Discord, or WhatsApp by swapping out the trigger and response nodes.
  1. Add Subtitles or Effects
  • Integrate Whisper or another speech-to-text tool to generate subtitles.
  • Add overlay or transition effects in the Creatomate video payload.
  1. Use Local File Storage Instead of MongoDB
  • Swap out MongoDB upload http nodes with filesystem or S3-compatible storage.
  1. Repurpose for Other Platforms
  • Swap YouTube upload with TikTok, Instagram, or Vimeo endpoints for broader publishing.

Need Help or Want to Customize This Workflow? If you'd like assistance setting this up or adapting it for a different use case, feel free to reach out to me at nanabrownsnr@gmail.com. I'm happy to help!

AI Content Creation and Publishing Engine with Mistral, Creatomate, and YouTube

This n8n workflow automates the entire process of generating video content ideas, creating video scripts, generating video assets, and publishing them to YouTube, all triggered by a simple command in Telegram. It leverages AI models (Mistral) for content generation and external services like Creatomate for video creation.

What it does

This workflow simplifies and automates the following steps:

  1. Triggered by Telegram: Listens for a specific command (e.g., /create_video) from a Telegram chat.
  2. Initial Response: Sends an acknowledgment message back to the Telegram chat.
  3. Content Idea Generation (AI): Uses a Mistral Cloud Chat Model to generate video content ideas based on a prompt.
  4. Video Script Generation (AI): Generates a detailed video script based on the generated idea, ensuring it's suitable for video production.
  5. Structured Output Parsing: Parses the AI-generated script into a structured JSON format, extracting key elements like title, description, and individual video segments.
  6. Video Asset Creation (Creatomate - via HTTP Request): Makes an HTTP request to the Creatomate API to generate video assets using the parsed script.
  7. Video Generation Status Check: Periodically checks the status of the video generation job with Creatomate using a Wait node and a loop with an If node and HTTP Request.
  8. Video Download: Once the video is ready, it downloads the generated video file from Creatomate.
  9. YouTube Upload: Uploads the completed video to YouTube with the generated title and description.
  10. Confirmation: Sends a confirmation message to the Telegram chat with the YouTube video link.

Prerequisites/Requirements

To use this workflow, you will need:

  • n8n Instance: A running n8n instance.
  • Telegram Bot: A Telegram Bot configured with a Bot Token.
  • Mistral AI Account: An API key for the Mistral Cloud Chat Model.
  • Creatomate Account: An API key for Creatomate.
  • YouTube Account: A YouTube account with API access enabled for uploads (requires Google OAuth 2.0 credentials).

Setup/Usage

  1. Import the workflow: Import the provided JSON into your n8n instance.
  2. Configure Credentials:
    • Telegram Trigger & Telegram: Set up your Telegram Bot credential (Bot Token).
    • Mistral Cloud Chat Model: Configure your Mistral AI API Key credential.
    • HTTP Request (Creatomate): Set up your Creatomate API Key credential.
    • YouTube: Configure your Google OAuth 2.0 credential for YouTube.
  3. Activate the workflow: Once all credentials are set and the nodes are configured, activate the workflow.
  4. Trigger from Telegram: Send the /create_video command (or your configured trigger command) to your Telegram bot to start the content creation process.

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