HumationHuman + Automation
Back to Catalog

Generate images with Pollinations & blog articles with Gemini 2.5 from Telegram

Fahmi OktafianFahmi Oktafian
1199 views
2/3/2026
Lead ManagementWebhookHubSpotSalesforceCRM
Official Page

This n8n workflow is a Telegram bot that allows users to either:

  • Generate AI images using Pollinations API, or
  • Generate blog articles using Gemini AI

Users simply type image your prompt or blog your title, and the bot responds with either an AI-generated image or article.

Who's it for

This template is ideal for:

  • Content creators and marketers who want to generate visual and written content quickly

  • Telegram bot developers looking for real-world AI integration

  • Educators or students automating content workflows

  • Anyone managing content pipelines using Google Sheets

What it does / How it works

Telegram Interaction

  • Trigger Telegram Message: Listens for new messages or button clicks via Telegram

  • Classify Telegram Input: JavaScript logic to classify input as /start, /help, normal text, or callback

  • Switch Input Type: Directs the flow based on the classification

Menu & Help

  • Send Main Menu to User: Shows "Generate Image", "Blog Article", "Help" options

  • Switch Callback Selection: Routes based on button pressed (image, blog, or help)

  • Send Help Instructions: Sends markdown instructions on how to use the bot

Input Validation

  • Validate Command Format: Ensures input starts with image or blog

  • Notify Invalid Input Format: If validation fails, informs user of correct format

Image Generator

  • Prompt User for Image Description → When user clicks Generate Image

  • Detect Text-Based Input Type → Detects if text is image or blog

  • Switch Text Command Type → Directs whether to generate image or article

  • Show Typing for Image Generation → Sends "uploading photo..." typing status

  • Build Image Generation URL → Constructs Pollinations API image URL from prompt

  • Download AI Image → Makes HTTP request to get the image

  • Send Image Result to Telegram → Sends image to user via Telegram

  • Log Image Prompt to Google Sheets → Logs prompt, image URL, date, and user ID

  • Upload Image to Google Drive → Saves image to Google Drive folder

Blog Article Generator

  • Prompt User for Blog Title → When user clicks Blog Article

  • Store Blog Prompt → Saves prompt for later use

  • Log Blog Prompt to Google Sheets → Writes title + user ID to Google Sheets

  • Send Article Style Options → Offers: Formal, Casual, or News style

  • Store Selected Article Style → Updates row with chosen style in Google Sheets

  • Fetch Last User Prompt → Finds the latest prompt submitted by this user

  • Extract Last Blog Prompt → Extracts row for use in AI request

  • Gemini Chat Wrapper → Handles input into LangChain node for AI processing

  • Generate Article with Gemini → Calls Gemini to create 3-paragraph blog post

  • Parse Gemini Response → Parses JSON string to extract title and content

  • Send Article to Telegram → Sends blog article result back to user

  • Log Final Article to Google Sheets → Updates row with final content and timestamp

Requirements

  • Telegram bot (via @BotFather)
  • Pollinations API (free and public endpoint)
  • Google Sheets & Drive (OAuth credential setup in n8n)
  • Google Gemini / PaLM API key via LangChain
  • Self-hosted or cloud n8n setup

Setup Instructions

  • Clone the workflow and import it into your n8n instance

  • Set credentials:

    • Telegram API
    • Google Sheets OAuth
    • Google Drive OAuth
    • Gemini (via LangChain)

  • Replace:

    • Sheet ID with your own Google Sheet
    • Folder ID on Google Drive
    • chat_id placeholders if needed (use expressions instead)

  • Deploy and send /start in your Telegram bot

🔧 Customization Tips

  • Edit the Gemini prompt to adjust article length or tone

  • Add extra style buttons like "SEO", "Story", "Academic"

  • Add image post-processing (e.g. compression, renaming)

  • Add error catching logic (e.g. if Pollinations image fails)

  • Store images with filenames based on timestamp/user

Security Considerations

  • Use n8n credentials for all tokens (Telegram, Gemini, Sheets, Drive)

  • Never hardcode your token inside HTTP nodes

  • Do not expose real Google Sheet or Drive links in shared version

  • Use Set node to collect all editable variables (like folder ID, sheet name)

n8n Workflow: Generate Images with Pollinations & Blog Articles with Gemini from Telegram

This n8n workflow automates the process of generating images and blog articles based on commands received via Telegram. It intelligently routes requests to either an image generation service (Pollinations) or a large language model (Google Gemini) depending on the user's input. The generated content is then stored in Google Drive and Google Sheets, and the results are sent back to the user on Telegram.

What it does

This workflow simplifies content creation by:

  1. Listening for Telegram Commands: It acts as a Telegram bot, waiting for incoming messages.
  2. Parsing Telegram Input: It extracts the command and prompt from the Telegram message.
  3. Conditional Routing: It checks if the message starts with /image.
    • If /image command:
      • It constructs a URL to the Pollinations API to generate an image based on the provided prompt.
      • It makes an HTTP request to Pollinations to get the image.
      • It saves the generated image to Google Drive.
      • It records the request details (prompt, image URL) in Google Sheets.
      • It sends the generated image back to the user on Telegram.
    • If no /image command:
      • It uses Google Gemini (via a LangChain Basic LLM Chain) to generate a blog article based on the provided prompt.
      • It saves the generated article text to Google Sheets.
      • It sends the generated article text back to the user on Telegram.
  4. Logging and Storage: All generated content (images, articles) and relevant metadata are stored in Google Drive and Google Sheets for easy access and tracking.

Prerequisites/Requirements

To use this workflow, you will need:

  • n8n Instance: A running instance of n8n.
  • Telegram Bot Token: A Telegram bot configured and its API token.
  • Google Account: Access to Google Drive and Google Sheets.
  • Google Gemini API Key: Credentials for Google Gemini (likely configured through a Google Cloud project).
  • Pollinations API Access: This workflow assumes Pollinations is accessible via a public HTTP endpoint. No specific API key is typically required for basic usage, but check Pollinations' current documentation.

Setup/Usage

  1. Import the Workflow:
    • Download the provided JSON file.
    • In your n8n instance, click "Workflows" in the left sidebar.
    • Click "New" -> "Import from JSON" and paste the workflow JSON or upload the file.
  2. Configure Credentials:
    • Telegram Trigger: Configure your Telegram Bot credentials.
    • Telegram (Send Message) Node: Configure your Telegram Bot credentials.
    • Google Sheets Node: Configure your Google Sheets credentials (OAuth 2.0 recommended).
    • Google Drive Node: Configure your Google Drive credentials (OAuth 2.0 recommended).
    • Google Gemini Chat Model Node: Configure your Google Gemini credentials.
  3. Update Node Parameters:
    • Google Sheets: Update the "Spreadsheet ID" and "Sheet Name" in the Google Sheets nodes to point to your desired spreadsheet for logging.
    • Google Drive: Update the "Folder ID" in the Google Drive node to specify where images should be saved.
    • Code Node (Pollinations URL): Ensure the URL for Pollinations is correct if you're using a custom setup.
  4. Activate the Workflow: Once all credentials and parameters are configured, activate the workflow.

How to use from Telegram:

  • To generate an image: Send a message to your Telegram bot starting with /image followed by your prompt.
    • Example: /image a futuristic city at sunset, digital art
  • To generate a blog article: Send any message to your Telegram bot (not starting with /image) with your article prompt.
    • Example: Write a short blog post about the benefits of remote work.

Related Templates

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 Dutch Public Procurement Data Collection with TenderNed

TenderNed Public Procurement What This Workflow Does This workflow automates the collection of public procurement data from TenderNed (the official Dutch tender platform). It: Fetches the latest tender publications from the TenderNed API Retrieves detailed information in both XML and JSON formats for each tender Parses and extracts key information like organization names, titles, descriptions, and reference numbers Filters results based on your custom criteria Stores the data in a database for easy querying and analysis Setup Instructions This template comes with sticky notes providing step-by-step instructions in Dutch and various query options you can customize. Prerequisites TenderNed API Access - Register at TenderNed for API credentials Configuration Steps Set up TenderNed credentials: Add HTTP Basic Auth credentials with your TenderNed API username and password Apply these credentials to the three HTTP Request nodes: "Tenderned Publicaties" "Haal XML Details" "Haal JSON Details" Customize filters: Modify the "Filter op ..." node to match your specific requirements Examples: specific organizations, contract values, regions, etc. How It Works Step 1: Trigger The workflow can be triggered either manually for testing or automatically on a daily schedule. Step 2: Fetch Publications Makes an API call to TenderNed to retrieve a list of recent publications (up to 100 per request). Step 3: Process & Split Extracts the tender array from the response and splits it into individual items for processing. Step 4: Fetch Details For each tender, the workflow makes two parallel API calls: XML endpoint - Retrieves the complete tender documentation in XML format JSON endpoint - Fetches metadata including reference numbers and keywords Step 5: Parse & Merge Parses the XML data and merges it with the JSON metadata and batch information into a single data structure. Step 6: Extract Fields Maps the raw API data to clean, structured fields including: Publication ID and date Organization name Tender title and description Reference numbers (kenmerk, TED number) Step 7: Filter Applies your custom filter criteria to focus on relevant tenders only. Step 8: Store Inserts the processed data into your database for storage and future analysis. Customization Tips Modify API Parameters In the "Tenderned Publicaties" node, you can adjust: offset: Starting position for pagination size: Number of results per request (max 100) Add query parameters for date ranges, status filters, etc. Add More Fields Extend the "Splits Alle Velden" node to extract additional fields from the XML/JSON data, such as: Contract value estimates Deadline dates CPV codes (procurement classification) Contact information Integrate Notifications Add a Slack, Email, or Discord node after the filter to get notified about new matching tenders. Incremental Updates Modify the workflow to only fetch new tenders by: Storing the last execution timestamp Adding date filters to the API query Only processing publications newer than the last run Troubleshooting No data returned? Verify your TenderNed API credentials are correct Check that you have setup youre filter proper Need help setting this up or interested in a complete tender analysis solution? Get in touch 🔗 LinkedIn – Wessel Bulte

Wessel BulteBy Wessel Bulte
247

🎓 How to transform unstructured email data into structured format with AI agent

This workflow automates the process of extracting structured, usable information from unstructured email messages across multiple platforms. It connects directly to Gmail, Outlook, and IMAP accounts, retrieves incoming emails, and sends their content to an AI-powered parsing agent built on OpenAI GPT models. The AI agent analyzes each email, identifies relevant details, and returns a clean JSON structure containing key fields: From – sender’s email address To – recipient’s email address Subject – email subject line Summary – short AI-generated summary of the email body The extracted information is then automatically inserted into an n8n Data Table, creating a structured database of email metadata and summaries ready for indexing, reporting, or integration with other tools. --- Key Benefits ✅ Full Automation: Eliminates manual reading and data entry from incoming emails. ✅ Multi-Source Integration: Handles data from different email providers seamlessly. ✅ AI-Driven Accuracy: Uses advanced language models to interpret complex or unformatted content. ✅ Structured Storage: Creates a standardized, query-ready dataset from previously unstructured text. ✅ Time Efficiency: Processes emails in real time, improving productivity and response speed. *✅ Scalability: Easily extendable to handle additional sources or extract more data fields. --- How it works This workflow automates the transformation of unstructured email data into a structured, queryable format. It operates through a series of connected steps: Email Triggering: The workflow is initiated by one of three different email triggers (Gmail, Microsoft Outlook, or a generic IMAP account), which constantly monitor for new incoming emails. AI-Powered Parsing & Structuring: When a new email is detected, its raw, unstructured content is passed to a central "Parsing Agent." This agent uses a specified OpenAI language model to intelligently analyze the email text. Data Extraction & Standardization: Following a predefined system prompt, the AI agent extracts key information from the email, such as the sender, recipient, subject, and a generated summary. It then forces the output into a strict JSON structure using a "Structured Output Parser" node, ensuring data consistency. Data Storage: Finally, the clean, structured data (the from, to, subject, and summarize fields) is inserted as a new row into a specified n8n Data Table, creating a searchable and reportable database of email information. --- Set up steps To implement this workflow, follow these configuration steps: Prepare the Data Table: Create a new Data Table within n8n. Define the columns with the following names and string type: From, To, Subject, and Summary. Configure Email Credentials: Set up the credential connections for the email services you wish to use (Gmail OAuth2, Microsoft Outlook OAuth2, and/or IMAP). Ensure the accounts have the necessary permissions to read emails. Configure AI Model Credentials: Set up the OpenAI API credential with a valid API key. The workflow is configured to use the model, but this can be changed in the respective nodes if needed. Connect the Nodes: The workflow canvas is already correctly wired. Visually confirm that the email triggers are connected to the "Parsing Agent," which is connected to the "Insert row" (Data Table) node. Also, ensure the "OpenAI Chat Model" and "Structured Output Parser" are connected to the "Parsing Agent" as its AI model and output parser, respectively. Activate the Workflow: Save the workflow and toggle the "Active" switch to ON. The triggers will begin polling for new emails according to their schedule (e.g., every minute), and the automation will start processing incoming messages. --- Need help customizing? Contact me for consulting and support or add me on Linkedin.

DavideBy Davide
1616