HumationHuman + Automation
Back to Catalog

Transform product photos into studio-quality visuals with Nano Banana & Telegram

SuSSuS
243 views
2/3/2026
Microsoft TeamsGoogle SheetsNotificationsAutomationIssue Tracking
Official Page

Turn a single product photo into scroll-stopping, studio-quality visuals in minutes.
Perfect for Shopify / WooCommerce / Amazon / Etsy sellers, agencies, and UGC creators who want consistent, on-brand images without costly photoshoots or endless editing.

Why you’ll love it

  • Sell more, faster: Professional, consistent visuals boost trust and conversions.
  • Save time & money: No studio, no photographer, no retouching marathon.
  • Multiple looks instantly: Get up to 3 variants per product (great for A/B testing).
  • On-brand results: Subtle brand color grading for a polished, consistent look.
  • Zero friction delivery: Images are sent straight to your Telegram for instant review.

Perfect for

  • D2C brands, marketplace sellers, and dropshippers
  • Agencies producing UGC for clients
  • Creators who need ad-ready product images today
  • Teams that want reliable results without learning complex tools

What’s included

  • n8n workflow (template) that automates: form input → prompt creation → image rendering → delivery
  • Built-in guidance (sticky notes) to keep you moving fast
  • Prompt logic tuned for product realism (camera, lighting, materials, subtle brand grading)

Step-by-Step — How it works

  1. Open the form
    Enter:

    • Product Name & Product Description (material, finish, color, USP)
    • Product Image (required)
    • Optional: Background Image, or describe it (Background Type + Background Description)
    • Choose Camera Angle, Lighting Style, Aperture (Depth of Field)
    • Set Aspect Ratio, Variants (1–3), and your TG_Chat ID (Telegram target)

  2. Click “Submit”
    The workflow automatically:

    • Uploads your images
    • Writes photography-accurate prompts (focal length, aperture, lighting, surface/shadows)
    • Renders each variant into clean PNG results

  3. Receive your images

    • Finished images land in your Telegram chat/group for instant feedback and use

That’s it. No manual editing, no waiting, no hassle.

Real problems solved

  • Inconsistent brand look? Get uniform, polished visuals across your store and ads.
  • No time for shoots? Generate studio/lifestyle shots from one upload.
  • Need options fast? Produce multiple variants (A/B/C) in a single run.
  • Limited budget? Cut studio and retouching costs to nearly zero.

Customize it to your stack

  • Swap Telegram for email, Slack, Google Drive, Dropbox, or S3
  • Save prompts & URLs to Notion/Airtable for tracking
  • Add an approval step before delivery
  • Map aspect ratios to fixed pixel sizes for ad platforms

Requirements

  • n8n (self-hosted or cloud)
  • Access to OpenAI and Kie.ai (API creds)
  • A Telegram bot added to your target chat (for delivery)

You control which assets and metadata are sent to external APIs. Always ensure you have rights to the images you upload.

FAQs

Do I need a background image?
No. If you skip it, the workflow builds a realistic scene from your background description.

How many images do I get?
Up to 3 variants per run (you choose 1–3).

Are the results on-brand?
Yes—subtle grading honors your brand colors without over-saturation.

Can I change the delivery channel?
Absolutely. Replace Telegram with your preferred destination (email, storage, chat).

Use cases

  • PDP images, marketplace listings, social ads, story posts, influencer kits, quick mockups for pitch decks and client approvals.

Ready to level up your product visuals?

Add to cart, upload your first product image, and get studio-quality results—today.

Transform Product Photos into Studio-Quality Visuals with AI Agent and Telegram

This n8n workflow automates the process of transforming product photos into studio-quality visuals using an AI agent and delivers them via Telegram. It's designed to streamline the creation of professional product imagery, making it easier to generate engaging visuals for e-commerce, marketing, or social media.

What it does

  1. Triggers on Form Submission: The workflow starts when a new submission is received via an n8n form. This form is expected to contain the initial product photo URL and a prompt for the AI agent.
  2. Sets Initial Data: It prepares the input data for the AI agent, likely extracting the image URL and prompt from the form submission.
  3. Processes with AI Agent: An AI Agent (powered by LangChain and OpenAI Chat Model) takes the product photo URL and the user-provided prompt to generate a studio-quality visual.
  4. Parses AI Output: The AI agent's response is then parsed using a Structured Output Parser, ensuring the generated image URL and any accompanying text are correctly extracted.
  5. Splits Out Items: If the AI agent returns multiple items (e.g., several generated images or variations), this node splits them into individual items for further processing.
  6. Loops Over Items: It iterates through each generated item (e.g., each studio-quality image).
  7. Sends Photo to Telegram: For each item, it sends the newly generated studio-quality image to a specified Telegram chat.
  8. Waits (Optional Delay): Includes a short delay (1 second) between sending each photo to Telegram, potentially to avoid rate limits or improve user experience.
  9. Merges Outputs: After processing all items, it merges the outputs from the Telegram node.
  10. Sends Confirmation to Telegram: Finally, it sends a confirmation message to Telegram, indicating that the photo transformation and delivery process is complete.

Prerequisites/Requirements

  • n8n Instance: A running n8n instance.
  • Telegram Bot: A configured Telegram Bot token and chat ID to send messages and photos.
  • OpenAI API Key: An OpenAI API key configured as a credential in n8n for the OpenAI Chat Model.
  • n8n Form: An n8n Form Trigger configured to receive product photo URLs and prompts.

Setup/Usage

  1. Import the Workflow: Import the provided JSON into your n8n instance.
  2. Configure Credentials:
    • Telegram: Set up your Telegram Bot API credential with your bot token.
    • OpenAI: Set up your OpenAI API credential with your API key.
  3. Configure n8n Form Trigger:
    • Edit the "On form submission" node.
    • Ensure the form fields capture the necessary information, such as imageUrl (the URL of the product photo) and prompt (the instructions for the AI agent).
  4. Configure Telegram Nodes:
    • Edit both "Telegram" nodes.
    • Select your Telegram Bot credential.
    • Specify the Chat ID where the transformed photos and confirmation messages should be sent.
  5. Configure AI Agent and OpenAI Chat Model:
    • Ensure the "AI Agent" node is correctly linked to your "OpenAI Chat Model" credential.
    • Review the "Structured Output Parser" to ensure it matches the expected JSON output format from your AI agent.
  6. Activate the Workflow: Once configured, activate the workflow.
  7. Submit the Form: Submit data to the n8n form trigger with a product image URL and a descriptive prompt (e.g., "Transform this into a studio-quality shot with a minimalist background and soft lighting"). The workflow will then process the request and send the resulting image(s) to your Telegram chat.

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