HumationHuman + Automation
Back to Catalog

Generate 5-level AI explanations for different audiences from Telegram to Google Docs with GPT-4.1-mini

Sridevi EdupugantiSridevi Edupuganti
93 views
2/3/2026
Multipart Form DataWebhookData TransformationImage ProcessingFile Upload
Official Page

Description

Ask any question and get five different answers instantly. Each answer is written for a different audience—from kids to business executives. Your Telegram bot delivers all five explanations in under 10 seconds and saves them to Google Docs automatically. Perfect for teachers, writers, and anyone who needs to explain things to different people.

Who's It For

• Educators creating multi-grade
curriculum content • Content creators generating material for diverse audiences • Technical writers producing documentation at different expertise levels • Parents explaining complex topics to children • Anyone who needs to explain things to different people.

How It Works

• Transforms any question into five distinct explanations: kid-friendly stories (5-year-olds), relatable content (teenagers), professional explanations (graduates), academic analysis (PhD researchers), and strategic insights (business executives) • Five AI agents process simultaneously for 3-8 second response times • Delivers six formatted Telegram messages (header + five explanations) • Automatically archives complete conversations to Google Docs • Uses binary tree merge architecture for reliable data handling

How to Set Up

• Create Telegram bot via @BotFather and add token to n8n credentials • Obtain OpenAI API key and add to n8n credentials • Connect Google account to grant Docs access • Create blank Google Doc and paste URL in workflow's Google Docs node • Activate workflow and test with any question

Requirements

• Telegram Bot API token (free) • OpenAI API key (pay-per-use • Google account with Docs access (free) • n8n instance (cloud or self-hosted)

How to Customize

• Modify AI prompts in 'Create 5 Items' node for different tones and styles • Adjust character limits in formatting nodes to control message length • Change output destinations from Telegram to Slack, email, or other platforms • Switch AI providers from OpenAI to alternatives • Add additional comprehension levels by duplicating AI agent nodes

Need Help?

For detailed notes and implementation, please leverage the README document at: https://drive.google.com/file/d/19Fx-FoihL70qpOi4CnEwQ6Sud2dbUnE_/view?usp=sharing

Join the Discord (https://discord.com/invite/XPKeKXeB7d) or Join the n8n community forum (https://community.n8n.io/) for support

Generate 5-Level AI Explanations for Different Audiences from Telegram to Google Docs with GPT-4 Mini

This n8n workflow automates the process of generating multi-level AI explanations for a given topic, triggered by a message in Telegram, and then saving these explanations to a Google Docs document. It leverages an AI Agent with an OpenAI Chat Model to create explanations tailored for different audiences.

What it does

This workflow simplifies and automates the following steps:

  1. Listens for Telegram Messages: It starts by monitoring a configured Telegram bot for incoming messages.
  2. Extracts Message Content: The text from the incoming Telegram message is extracted to be used as the topic for explanation.
  3. Generates AI Explanations: An AI Agent, powered by an OpenAI Chat Model, takes the extracted topic and generates a 5-level explanation. These explanations are designed for various audiences, from simple (e.g., "for a 5-year-old") to highly technical (e.g., "for a PhD student").
  4. Formats Output: The generated explanations are then formatted into a structured text, ready for document creation.
  5. Creates Google Docs Document: A new Google Docs document is created, titled with the original Telegram message, and populated with the multi-level AI explanation.
  6. Confirms via Telegram: A confirmation message, including a link to the newly created Google Docs document, is sent back to the Telegram chat.

Prerequisites/Requirements

To use this workflow, you will need:

  • n8n Instance: A running n8n instance.
  • Telegram Bot: A Telegram bot token and chat ID configured as an n8n credential.
  • OpenAI API Key: An OpenAI API key configured as an n8n credential for the AI Agent and Chat Model. This workflow is designed to use a "GPT-4 mini" equivalent model (implied by the directory name, but configured via the OpenAI Chat Model node).
  • Google Account: A Google account with access to Google Docs, configured as an n8n OAuth2 credential.

Setup/Usage

  1. Import the Workflow: Download the provided JSON and import it into your n8n instance.
  2. Configure Credentials:
    • Telegram: Set up your Telegram Bot API credential.
    • OpenAI: Set up your OpenAI API Key credential.
    • Google Docs: Set up your Google OAuth2 credential with access to Google Docs.
  3. Activate the Workflow: Once all credentials are configured, activate the workflow.
  4. Trigger the Workflow: Send a message to your configured Telegram bot with the topic you want an explanation for (e.g., "Explain Quantum Computing").
  5. Receive Explanation: The bot will respond with a link to a new Google Docs document containing the 5-level explanation.

Related Templates

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

AI-powered code review with linting, red-marked corrections in Google Sheets & Slack

Advanced Code Review Automation (AI + Lint + Slack) Who’s it for For software engineers, QA teams, and tech leads who want to automate intelligent code reviews with both AI-driven suggestions and rule-based linting — all managed in Google Sheets with instant Slack summaries. How it works This workflow performs a two-layer review system: Lint Check: Runs a lightweight static analysis to find common issues (e.g., use of var, console.log, unbalanced braces). AI Review: Sends valid code to Gemini AI, which provides human-like review feedback with severity classification (Critical, Major, Minor) and visual highlights (red/orange tags). Formatter: Combines lint and AI results, calculating an overall score (0–10). Aggregator: Summarizes results for quick comparison. Google Sheets Writer: Appends results to your review log. Slack Notification: Posts a concise summary (e.g., number of issues and average score) to your team’s channel. How to set up Connect Google Sheets and Slack credentials in n8n. Replace placeholders (<YOURSPREADSHEETID>, <YOURSHEETGIDORNAME>, <YOURSLACKCHANNEL_ID>). Adjust the AI review prompt or lint rules as needed. Activate the workflow — reviews will start automatically whenever new code is added to the sheet. Requirements Google Sheets and Slack integrations enabled A configured AI node (Gemini, OpenAI, or compatible) Proper permissions to write to your target Google Sheet How to customize Add more linting rules (naming conventions, spacing, forbidden APIs) Extend the AI prompt for project-specific guidelines Customize the Slack message formatting Export analytics to a dashboard (e.g., Notion or Data Studio) Why it’s valuable This workflow brings realistic, team-oriented AI-assisted code review to n8n — combining the speed of automated linting with the nuance of human-style feedback. It saves time, improves code quality, and keeps your team’s review history transparent and centralized.

higashiyama By higashiyama
90

🎓 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