HumationHuman + Automation
Back to Catalog

AI image generation & editing with Google Gemini and Telegram Bot

Santhej KalladaSanthej Kallada
771 views
2/3/2026
Google SheetsEmail ManagementAutomationData ExtractionGmail
Official Page

Who is this for?

  • Creators, designers, and developers exploring AI-powered image generation.
  • Automation enthusiasts who want to integrate image creation into n8n workflows.
  • Telegram bot builders looking to add visual AI capabilities.
  • Marketers or freelancers automating creative content workflows.

What problem is this workflow solving?

Creating AI images usually requires multiple tools and manual setup. This workflow removes the complexity by:

  • Connecting Nano Banana (AI image model) directly to n8n.
  • Allowing image generation via Telegram chatbot.
  • Providing a no-code setup that is fully automated and scalable.

What this workflow does

This workflow demonstrates how to generate AI images using Nano Banana and n8n, with an integrated Telegram chatbot interface.
The process includes:

  1. Connecting Gemini Nano Banana to n8n.
  2. Automating image generation requests triggered from Telegram.
  3. Returning AI-generated images back to the user.
  4. Allowing customization of prompts and styles dynamically.

By the end, you’ll have a fully functional automation to generate and send AI-created images through Telegram — no coding required.

Setup

  1. Create accounts:
  • Sign up on n8n.io and ensure you have Telegram Bot API access.
  • Connect your Nano Banana or Gemini API endpoint.
  1. Set up your Telegram Bot:
  • Use BotFather to create a new bot and get the token.
  • Add the “Telegram Trigger” node in n8n.
  1. Configure Nano Banana connection:
  • Add an HTTP Request node for Nano Banana API.
  • Insert your API key and prompt parameters.
  1. Handle responses:
  • Parse the AI-generated image output.
  • Send the image file back to the Telegram user.
  1. Test and Deploy:
  • Run a sample image prompt.
  • Verify that Telegram returns the correct generated image.

How to customize this workflow to your needs

  • Modify prompts or styles to fit different artistic use cases.
  • Add conditional logic for image size, aspect ratio, or filters.
  • Integrate with Google Drive or Notion for image storage.
  • Schedule automatic image generation for campaigns or content creation.
  • Expand with OpenAI or Stability AI for hybrid workflows.

Notes

  • Nano Banana API may have rate limits depending on usage.
  • Ensure your Telegram bot has permission to send files and images.
  • You can host this workflow on n8n Cloud or self-hosted setups.

Want A Video Tutorial on How to Setup This Automation:

 https://youtu.be/0s6ZdU1fjc4

AI Image Generation & Editing with Google Gemini and Telegram Bot

This n8n workflow empowers you to interact with Google Gemini for AI image generation and editing, all through a convenient Telegram bot. You can generate new images from text prompts, edit existing images by providing new instructions, and manage your generated images by saving them to Google Drive and Airtable.

What it does

  1. Listens for Telegram Commands: The workflow is triggered by messages received from a configured Telegram bot.
  2. Parses Telegram Input: It extracts the message text and identifies if the user wants to generate a new image (/imagine) or edit an existing one (/edit).
  3. Handles Image Generation (/imagine):
    • If the command is /imagine, it extracts the text prompt for image generation.
    • It sends the prompt to the Google Gemini API to generate an image.
    • The generated image is then sent back to the user via Telegram.
    • The image and its prompt are saved to Google Drive and Airtable for record-keeping.
  4. Handles Image Editing (/edit):
    • If the command is /edit, it expects the user to reply to an existing image message with the new editing instructions.
    • It retrieves the original image from Google Drive (using a file ID stored in Airtable, linked by the Telegram message ID).
    • It sends the original image and the editing instructions to the Google Gemini API for modification.
    • The edited image is sent back to the user via Telegram, replacing the original.
    • The updated image is saved to Google Drive and Airtable, overwriting the previous version.
  5. Manages Data Storage: All generated and edited images, along with their associated prompts and file IDs, are stored in Google Drive and Airtable.

Prerequisites/Requirements

To use this workflow, you will need:

  • n8n Instance: A running instance of n8n.
  • Telegram Bot: A Telegram bot token and a chat ID where the bot will operate.
  • Google Gemini API Key: Access to the Google Gemini API for image generation and editing.
  • Google Drive Account: A Google Drive account configured with n8n credentials to store images.
  • Airtable Account: An Airtable base and table configured with n8n credentials to store image metadata (prompts, file IDs, Telegram message IDs).

Setup/Usage

  1. Import the Workflow: Download the JSON provided and import it into your n8n instance.
  2. Configure Credentials:
    • Telegram Trigger & Node: Set up your Telegram Bot API credentials.
    • HTTP Request (Google Gemini): Configure your Google Gemini API key as a Bearer Token or API Key credential.
    • Google Drive: Set up your Google Drive OAuth2 credentials.
    • Airtable: Set up your Airtable API Key credentials.
  3. Configure Nodes:
    • Telegram Trigger: Ensure the "Allowed Updates" include messages and edited_messages.
    • HTTP Request (Google Gemini): Update the API endpoint and parameters according to the Google Gemini API documentation if different from the default.
    • Google Drive: Specify the folder ID where images should be saved.
    • Airtable: Specify your Base ID and Table Name for storing image data. Ensure your Airtable table has fields for:
      • Prompt (Text)
      • Image File ID (Text)
      • Telegram Message ID (Number)
      • Chat ID (Number)
      • Original Image URL (URL - for editing purposes, if applicable)
  4. Activate the Workflow: Once all credentials and node settings are configured, activate the workflow.

To use the bot:

  • Generate an image: Send a message to your Telegram bot starting with /imagine followed by your prompt (e.g., /imagine a futuristic city at sunset).
  • Edit an image: Reply to an image previously generated by the bot with /edit followed by your editing instructions (e.g., /edit make it a cyberpunk style).

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