Generate AI avatar videos with GPT-5 & publish to social media platforms
This workflow contains community nodes that are only compatible with the self-hosted version of n8n.

Automate Social Media with HeyGen and GPT-5: Publish Videos to TikTok, YouTube & Instagram
π₯ Who is this for?
This workflow is designed for:
- Content creators who want to scale their short-form video production
- Marketing teams seeking consistent and automated publishing pipelines
- Agencies managing multiple social accounts for clients
- Entrepreneurs looking to save time by automating repetitive content tasks
π‘ What problem is this workflow solving?
Publishing on multiple platforms like YouTube Shorts, TikTok, and Instagram is often:
- Time-consuming (manual editing, caption writing, uploads)
- Inconsistent (different requirements for each platform)
- Prone to delays (switching between tools)
This workflow solves these issues by creating a fully automated video pipeline powered by GPT-5, HeyGen, and Blotato.
βοΈ What this workflow does
- Capture voice idea via Telegram
- Transcribe voice to text using OpenAI Whisper
- Generate a catchy title and caption with GPT-5
- Create an AI avatar video with HeyGen
- Save and organize assets in Google Drive and Google Sheets
- Upload final video to Blotato
- Auto-publish to:
- YouTube Shorts
- TikTok
- (Optional: Facebook, X/Twitter, LinkedIn, Pinterest, Threads, Bluesky)
- Update logs in Google Sheets
- Send a Telegram confirmation once published
π§° Setup
Before using this workflow, ensure you have:
- A Telegram Bot connected to n8n for voice input
- An OpenAI API key for transcription (Whisper) and GPT-5 processing
- A HeyGen account & API key for avatar video generation
- A Google Drive & Google Sheets integration for storing assets and logs
- A Blotato account (Pro plan) with API access enabled
- Verified Community Nodes enabled in n8n Admin Panel
- Blotato node installed and credentials configured
π οΈ How to customize this workflow
- Prompts β Adjust GPT-5 prompts to match your brand voice and niche
- Avatars β Use custom avatars or voices via HeyGen configuration
- Platforms β Activate only the social nodes you need (e.g., focus on TikTok & YouTube Shorts)
- Approval steps β Add Telegram or Slack confirmation before publishing
- Analytics β Extend the workflow to track engagement data in Google Sheets, Airtable, or Notion
This workflow turns a simple spoken idea into a viral-ready video β automatically generated, styled, and posted across your most important platforms.
π Documentation: Notion Guide
Need help customizing?
n8n Workflow: Generate AI Avatar Videos with GPT & Publish to Social Media
This n8n workflow automates the process of generating AI avatar videos based on a Google Sheet, getting approval via Telegram, and then publishing them to social media platforms. It leverages AI models for content generation and video creation, streamlining a complex content production pipeline.
What it does
This workflow simplifies and automates the following steps:
- Triggers on Telegram Message: The workflow starts when a specific message is received in Telegram.
- Fetches Data from Google Sheets: It reads data from a specified Google Sheet, likely containing prompts or content for video generation.
- Generates AI Content (Thinking Tool): An AI "Think" tool is used to process the input, potentially generating scripts, ideas, or further instructions for the video.
- Generates AI Chat Model Response: An OpenAI Chat Model is used to generate conversational content, likely for the video script.
- Generates AI Video: An OpenAI node is used to generate the actual AI avatar video based on the generated content.
- Stores Video in Google Drive: The generated video is uploaded and saved to a designated folder in Google Drive.
- Sends Approval Request to Telegram: A message is sent to Telegram with the generated video link, requesting approval.
- Waits for Approval: The workflow pauses, waiting for a specific approval message from Telegram.
- Conditional Publishing:
- If Approved: If the video is approved, it proceeds to the "Publish to Social Media" step (represented by an empty HTTP Request node, implying integration with social media APIs).
- If Rejected: If the video is rejected, it sends a rejection notification to Telegram.
- Updates Google Sheet: The workflow updates the Google Sheet with the status of the video (e.g., "Approved", "Rejected", "Published").
Prerequisites/Requirements
To use this workflow, you will need:
- n8n Instance: A running n8n instance.
- Telegram Account & Bot: A Telegram bot and a chat ID to send and receive messages for triggering and approvals.
- Google Sheets Account: Access to a Google Sheet containing the input data and for status updates.
- Google Drive Account: A Google Drive account to store the generated videos.
- OpenAI API Key: An API key for OpenAI to utilize its Chat Model and potentially other AI capabilities for content and video generation.
- Social Media Accounts: Credentials and API access for the social media platforms you intend to publish to (represented by the generic HTTP Request node). This will require further configuration.
Setup/Usage
- Import the Workflow: Download the provided JSON and import it into your n8n instance.
- Configure Credentials:
- Set up your Telegram Bot credential for both the "Telegram Trigger" and "Telegram" nodes.
- Configure your Google Sheets credential for the "Google Sheets" nodes.
- Set up your Google Drive credential for the "Google Drive" node.
- Configure your OpenAI API Key credential for the "OpenAI Chat Model" and "OpenAI" nodes.
- Customize Nodes:
- Telegram Trigger (Node 50): Configure the trigger message or command that will initiate the workflow.
- Google Sheets (Node 18): Specify the spreadsheet ID, sheet name, and any filters or ranges to read data from.
- AI Agent (Node 1119), OpenAI Chat Model (Node 1153), OpenAI (Node 1250), Think (Node 1289): Configure the AI prompts, models, and parameters according to your content generation needs.
- Google Drive (Node 58): Specify the folder where generated videos should be stored.
- Telegram (Node 49): Configure the chat ID to send approval requests and notifications.
- Wait (Node 514): Set the expected approval message from Telegram.
- HTTP Request (Node 19): This node is currently a generic HTTP Request. You will need to configure it to interact with your desired social media platform's API for publishing. This might involve setting the URL, headers, body, and authentication.
- Google Sheets (Node 18 - for updates): Configure the sheet and columns to update the video status.
- Activate the Workflow: Once all nodes are configured, activate the workflow.
- Trigger the Workflow: Send the configured trigger message to your Telegram bot to start the process.
- Approve/Reject Videos: Monitor your Telegram for approval requests and respond with the designated approval/rejection messages.
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 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.