HumationHuman + Automation
Back to Catalog

Transform product photos into social media videos with Gemini AI, Kling & LATE

Bilel ArouaBilel Aroua
1677 views
2/3/2026
AIOpenAIAutomationNotionFeedback
Official Page

shorti_cover2.png exemple.png

👥 Who is this for?

Creators, marketers, and brands that want to turn a single product photo into premium motion clips, then optionally publish to Instagram/TikTok/YouTube via LATE. No editing skills required.

❓ What problem does it solve?

Producing short vertical ads from a static packshot takes time (retouching, motion design, soundtrack, publishing). This workflow automates the entire process: image enhancement → cinematic motion → optional upscale → soundtrack → share.

🛠️ What this workflow does

  • Collects a product photo via Telegram.
  • Generates two refined edit prompts + two motion prompts using multi-agent Gemini orchestration.
  • Creates two edited images with Fal.ai Gemini-Flash (image edit).
  • Renders two 5s vertical videos with Kling (via fal.run queue).
  • Auto-stitches them (FFmpeg API) and optionally upscales with Topaz.
  • Generates a clean ambient soundtrack with MMAudio.
  • Sends previews + final links back on Telegram.
  • Optionally publishes to Instagram, TikTok, YouTube Shorts, and more via LATE.

⚡ Setup

  • Telegram: Bot token (Telegram node).
  • Fal.ai: HTTP Header Auth (Authorization: Bearer <FAL_API_KEY>) for Gemini-Flash edit, Kling queue, FFmpeg compose, Topaz upscale, and MMAudio.
  • Google Gemini (PaLM credential) for AI agents.
  • ImgBB: API key for uploading original/edited images.
  • LATE: create an account at getlate.dev and use your API key for publishing (optional).

▶️ How to use

  1. Start the workflow and DM your bot a clear product photo (jpg/jpeg/webp).
  2. Approve the two still concepts when prompted in Telegram.
  3. The orchestrator generates cinematic motion prompts and queues Kling renders.
  4. Receive two motion previews, then a stitched final (upscaled + soundtrack).
  5. Choose to auto-publish to Instagram/TikTok/YouTube via LATE (optional).

🎨 How to customize

  • Art Direction → tweak the “Art Director” system message (lighting, backgrounds, grading).
  • Motion Flavor → adjust the “Motion Designer” vocabulary for different camera moves/dynamics.
  • Durations/Aspect → default is 9:16, 5s; you can change Kling duration.
  • Soundtrack → edit the MMAudio prompt to reflect your brand’s sonic identity.
  • Publishing → enable/disable LATE targets; customize captions/hashtags.

✅ Prerequisites

  • A Telegram bot created via @BotFather.
  • A Fal.ai account + API key.
  • An ImgBB account + API key.
  • (Optional) a LATE account with connected social profiles — sign up at getlate.dev.

💡 Detailed technical notes, architecture, and step-by-step flow explanation are included as sticky notes inside this workflow.

🆘 Support

If you need help setting up or customizing this workflow:

I can provide guidance, troubleshooting, or custom extra workflow adaptations.

Transform Product Photos into Social Media Videos with Gemini AI & Kling

This n8n workflow automates the process of generating social media video scripts and video content from product photos, leveraging Google Gemini AI for creative content generation and Kling AI for video creation. It allows for a human-in-the-loop approval process via Telegram before video generation.

What it does

This workflow streamlines the creation of engaging social media video content from product images through the following steps:

  1. Triggers on Telegram Input: The workflow starts when a message is received via Telegram. This message is expected to contain a product photo URL and a description.
  2. Extracts Product Information: It processes the incoming Telegram message to extract the product photo URL and any accompanying text description.
  3. Generates Social Media Video Script (AI): An AI agent (Google Gemini) is used to generate a social media video script based on the provided product photo URL and description. This script includes elements like video scenes, voiceover text, and suggested visuals.
  4. Formats Script for Approval: The generated script is formatted into a readable message for review.
  5. Sends Script for Human Approval (Telegram): The formatted script is sent back to the Telegram user for approval. The workflow waits for a "yes" or "no" response.
  6. Conditional Processing based on Approval:
    • If Approved: The workflow proceeds to generate the video.
    • If Rejected: The workflow stops, and optionally, a rejection message could be sent (not explicitly shown in the provided JSON but can be added).
  7. Generates Video Content (AI): If approved, another AI agent (Kling AI, inferred from the directory name and common use cases with Gemini for video) is used to create the actual video based on the approved script. This involves making an HTTP request to a video generation API.
  8. Sends Video Link (Telegram): The URL of the generated video is sent back to the Telegram user.
  9. Aggregates and Splits Video Scenes: The workflow processes the video scenes generated by the AI, potentially splitting them out for individual processing or combining them for the final video creation step.
  10. Prepares Data for Video Generation: It sets up the necessary data structure for the video generation API call, including the script details and any other required parameters.

Prerequisites/Requirements

To use this workflow, you will need:

  • n8n Instance: A running n8n instance.
  • Telegram Bot Token: A Telegram Bot Token and a chat ID to interact with the workflow.
  • Google Gemini API Key: Access to the Google Gemini API for the Google Gemini Chat Model node.
  • Kling AI API Key: An API key for Kling AI (or a similar video generation service) to use with the HTTP Request node for video creation.
  • AI Agent Credentials: Appropriate credentials configured in n8n for the AI Agent nodes to access the language models and tools.

Setup/Usage

  1. Import the Workflow: Download the workflow JSON and import it into your n8n instance.
  2. Configure Credentials:
    • Set up your Telegram API credential with your Bot Token.
    • Configure your Google Gemini credential with your API key.
    • If using Kling AI or another video generation service, configure an HTTP Request credential or directly embed the API key in the HTTP Request node if appropriate.
  3. Activate the Telegram Trigger: Ensure the Telegram Trigger node is active and configured to listen for messages in your desired chat.
  4. Review AI Agent Configurations:
    • Open the AI Agent nodes (AI Agent and AI Agent Tool) and verify their configurations, including the selected language model (Google Gemini Chat Model) and any specific instructions or tools.
    • The Think tool likely represents a custom tool or a thinking process within the AI agent.
  5. Configure HTTP Request for Video Generation:
    • Locate the HTTP Request node (node ID 19). This node is responsible for calling the video generation API.
    • Update the URL, headers (including your Kling AI API key or similar), and body with the correct API endpoint and payload for your chosen video generation service. The workflow currently prepares data in Edit Fields (node 38) and Code (node 834) that will likely feed into this request.
  6. Start the Workflow: Once all credentials and nodes are configured, activate the workflow.

Now, when you send a message with a product photo URL and description to your Telegram bot, the workflow will automatically generate a social media video script, ask for your approval, and then create the video.

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