HumationHuman + Automation
Back to Catalog

Automatically transcribe Telegram voice messages with OpenAI Whisper & Google Workspace

Trung TranTrung Tran
1273 views
2/3/2026
emailsmtpautomationattachmentsimap
Official Page

πŸŽ™οΈ VoiceScribe AI: Telegram Audio Message Auto Transcription with OpenAI Whisper

> Automatically transcribe Telegram voice messages and store them as structured logs in Google Sheets, while backing up the audio in Google Drive.

πŸ§‘β€πŸ’Ό Who’s it for

  • Journalists, content creators, or busy professionals who often record voice memos or short interviews on the go.
  • Anyone who wants to turn voice recordings into searchable, structured notes.

βš™οΈ How it works / What it does

  1. User sends a voice message to a Telegram bot.
  2. n8n checks if the message is an audio voice note.
  3. If valid, it downloads the audio file and:
    • Transcribes it using OpenAI Whisper (or your LLM of choice).
    • Uploads the original audio to Google Drive for safekeeping.
  4. The transcript and audio metadata are merged.
  5. The workflow:
    • Logs the data into a Google Sheet.
    • Sends a formatted confirmation message to the user via Telegram.

If the input is not audio, the bot politely informs the user that only voice messages are accepted.

βœ… Features

  • Accepts only Telegram voice messages.
  • Transcribes via OpenAI Whisper.
  • Logs DateTime, Duration, Transcript, and Audio URL to Google Sheets.
  • Sends user feedback message via Telegram with download + transcript link.

πŸš€ How to set up

Prerequisites

  • Telegram Bot connected to n8n (via Telegram Trigger)
  • Google Drive & Google Sheets credentials configured
  • OpenAI or Whisper API credentials (for transcription)

Steps

  1. Telegram Trigger
    Start the flow when a new message is sent to your bot.
  2. Check Message Type
    Use a conditional node to confirm it's a voice message.
  3. Download Voice Message
    Download the .oga file from Telegram.
  4. Transcribe Audio
    Send the binary audio to OpenAI Whisper or your transcription service.
  5. Upload to Google Drive
    Backup the original audio file.
  6. Merge Outputs
    Combine transcription with Drive metadata.
  7. Transform to Row Format
    Prepare structured JSON for Google Sheets.
  8. Append to Google Sheet
    Store the transcript log (DateTime, Duration, Transcript, AudioURL).
  9. Send Confirmation to User
    Inform the user via Telegram with their transcript and download link.
  10. Unsupported Message Handler
    Reply to users who send non-audio messages.

πŸ“„ Example Output in Google Sheet

| DateTime | Duration | Transcript | AudioURL | |-----------------------|----------|--------------------------------------------|------------------------------------------------------------| | 2025-08-07T13:12:19Z | 27 | Dα»± Γ‘n Outlet Activation lΓ ... | https://drive.google.com/uc?id=xxxx&export=download |

🧠 How to customize the workflow

  • Swap Whisper with Deepgram, AssemblyAI, or other providers.
  • Add speaker name detection or prompt-based tagging via GPT.
  • Route transcripts into Notion, Airtable, or CRM systems.
  • Add multi-language support or summarization steps.

πŸ“¦ Requirements

| Component | Required | |---------------------|----------| | Telegram API | βœ… | | Google Drive API | βœ… | | Google Sheets API | βœ… | | OpenAI Whisper API | βœ… | | n8n Cloud or Self-hosted | βœ… |

Created with ❀️ using n8n

Automatically Transcribe Telegram Voice Messages with OpenAI Whisper and Google Workspace

This n8n workflow automates the transcription of voice messages received in Telegram, saves the audio file to Google Drive, records the transcription in Google Sheets, and sends the transcribed text back to the Telegram chat.

What it does

  1. Listens for Telegram Voice Messages: Triggers when a new voice message is received in a configured Telegram chat.
  2. Filters for Voice Messages: Ensures the incoming message is indeed a voice message.
  3. Downloads Voice Message: Retrieves the voice message file from Telegram and saves it to a specified Google Drive folder.
  4. Transcribes Audio: Uses OpenAI's Whisper model to transcribe the downloaded audio file into text.
  5. Records Transcription: Appends the original sender, the transcription, and a link to the Google Drive file to a Google Sheet.
  6. Sends Transcription to Telegram: Posts the transcribed text back to the Telegram chat where the voice message originated.

Prerequisites/Requirements

  • n8n Account: A running n8n instance (cloud or self-hosted).
  • Telegram Bot: A Telegram Bot Token and Chat ID.
  • Google Drive Account: For storing the voice message audio files.
  • Google Sheets Account: For logging the transcriptions.
  • OpenAI API Key: For accessing the Whisper transcription model.

Setup/Usage

  1. Import the Workflow: Import the provided JSON into your n8n instance.
  2. Configure Credentials:
    • Telegram Trigger & Telegram Node: Set up your Telegram Bot API credentials.
    • Google Drive Node: Configure your Google Drive credentials (OAuth 2.0 recommended).
    • OpenAI Node: Provide your OpenAI API Key.
    • Google Sheets Node: Configure your Google Sheets credentials (OAuth 2.0 recommended).
  3. Specify Google Drive Folder: In the "Google Drive" node, specify the Folder ID where voice messages should be saved.
  4. Specify Google Sheet: In the "Google Sheets" node, specify the Spreadsheet ID and Sheet Name where transcriptions should be logged.
  5. Activate the Workflow: Once all credentials and configurations are set, activate the workflow.

Now, any voice message sent to your configured Telegram bot will be automatically transcribed and processed!

Related Templates

Two-way property repair management system with Google Sheets & Drive

This workflow automates the repair request process between tenants and building managers, keeping all updates organized in a single spreadsheet. It is composed of two coordinated workflows, as two separate triggers are required β€” one for new repair submissions and another for repair updates. A Unique Unit ID that corresponds to individual units is attributed to each request, and timestamps are used to coordinate repair updates with specific requests. General use cases include: Property managers who manage multiple buildings or units. Building owners looking to centralize tenant repair communication. Automation builders who want to learn multi-trigger workflow design in n8n. --- βš™οΈ How It Works Workflow 1 – New Repair Requests Behind the Scenes: A tenant fills out a Google Form (β€œRepair Request Form”), which automatically adds a new row to a linked Google Sheet. Steps: Trigger: Google Sheets rowAdded – runs when a new form entry appears. Extract & Format: Collects all relevant form data (address, unit, urgency, contacts). Generate Unit ID: Creates a standardized identifier (e.g., BUILDING-UNIT) for tracking. Email Notification: Sends the building manager a formatted email summarizing the repair details and including a link to a Repair Update Form (which activates Workflow 2). --- Workflow 2 – Repair Updates Behind the Scenes:\ Triggered when the building manager submits a follow-up form (β€œRepair Update Form”). Steps: Lookup by UUID: Uses the Unit ID from Workflow 1 to find the existing row in the Google Sheet. Conditional Logic: If photos are uploaded: Saves each image to a Google Drive folder, renames files consistently, and adds URLs to the sheet. If no photos: Skips the upload step and processes textual updates only. Merge & Update: Combines new data with existing repair info in the same spreadsheet row β€” enabling a full repair history in one place. --- 🧩 Requirements Google Account (for Forms, Sheets, and Drive) Gmail/email node connected for sending notifications n8n credentials configured for Google API access --- ⚑ Setup Instructions (see more detail in workflow) Import both workflows into n8n, then copy one into a second workflow. Change manual trigger in workflow 2 to a n8n Form node. Connect Google credentials to all nodes. Update spreadsheet and folder IDs in the corresponding nodes. Customize email text, sender name, and form links for your organization. Test each workflow with a sample repair request and a repair update submission. --- πŸ› οΈ Customization Ideas Add Slack or Telegram notifications for urgent repairs. Auto-create folders per building or unit for photo uploads. Generate monthly repair summaries using Google Sheets triggers. Add an AI node to create summaries/extract relevant repair data from repair request that include long submissions.

Matt@VeraisonLabsBy Matt@VeraisonLabs
208

Send WooCommerce cross-sell offers to customers via WhatsApp using Rapiwa API

Who Is This For? This n8n workflow enables automated cross-selling by identifying each WooCommerce customer's most frequently purchased product, finding a related product to recommend, and sending a personalized WhatsApp message using the Rapiwa API. It also verifies whether the user's number is WhatsApp-enabled before sending, and logs both successful and unsuccessful attempts to Google Sheets for tracking. What This Workflow Does Retrieves all paying customers from your WooCommerce store Identifies each customer's most purchased product Finds the latest product in the same category as their most purchased item Cleans and verifies customer phone numbers for WhatsApp compatibility Sends personalized WhatsApp messages with product recommendations Logs all activities to Google Sheets for tracking and analysis Handles both verified and unverified numbers appropriately Key Features Customer Segmentation: Automatically identifies paying customers from your WooCommerce store Product Analysis: Determines each customer's most purchased product Smart Recommendations: Finds the latest products in the same category as customer favorites WhatsApp Integration: Uses Rapiwa API for message delivery Phone Number Validation: Verifies WhatsApp numbers before sending messages Dual Logging System: Tracks both successful and failed message attempts in Google Sheets Rate Limiting: Uses batching and wait nodes to prevent API overload Personalized Messaging: Includes customer name and product details in messages Requirements WooCommerce store with API access Rapiwa account with API access for WhatsApp verification and messaging Google account with Sheets access Customer phone numbers in WooCommerce (stored in billing.phone field) How to Use β€” Step-by-Step Setup Credentials Setup WooCommerce API: Configure WooCommerce API credentials in n8n (e.g., "WooCommerce (get customer)" and "WooCommerce (get customer data)") Rapiwa Bearer Auth: Create an HTTP Bearer credential with your Rapiwa API token Google Sheets OAuth2: Set up OAuth2 credentials for Google Sheets access Configure Google Sheets Ensure your sheet has the required columns as specified in the Google Sheet Column Structure section Verify Code Nodes Code (get paying_customer): Filters customers to include only those who have made purchases Get most buy product id & Clear Number: Identifies the most purchased product and cleans phone numbers Configure HTTP Request Nodes Get customer data: Verify the WooCommerce API endpoint for retrieving customer orders Get specific product data: Verify the WooCommerce API endpoint for product details Get specific product recommend latest product: Verify the WooCommerce API endpoint for finding latest products by category Check valid WhatsApp number Using Rapiwa: Verify the Rapiwa endpoint for WhatsApp number validation Rapiwa Sender: Verify the Rapiwa endpoint for sending messages Google Sheet Required Columns You’ll need two Google Sheets (or two tabs in one spreadsheet): A Google Sheet formatted like this ➀ sample The workflow uses a Google Sheet with the following columns to track coupon distribution: Both must have the following headers (match exactly): | name | number | email | address1 | price | suk | title | product link | validity | staus | | ---------- | ------------- | ----------------------------------------------- | ----------- | ----- | --- | ---------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------ | ---------- | -------- | | Abdul Mannan | 8801322827799 | contact@spagreen.net | mirpur dohs | 850 | | Sharp Most Demanding Hoodie x Nike | https://yourshopdomain/p-img-nike | verified | sent | | Abdul Mannan | 8801322827799 | contact@spagreen.net | mirpur dohs | 850 | | Sharp Most Demanding Hoodie x Nike | https://yourshopdomain/p-img-nike | unverified | not sent | | Abdul Mannan | 8801322827799 | contact@spagreen.net | mirpur dohs | 850 | | Sharp Most Demanding Hoodie x Nike | https://yourshopdomain/p-img-nike | verified | sent | Important Notes Phone Number Format: The workflow cleans phone numbers by removing all non-digit characters. Ensure your WooCommerce phone numbers are in a compatible format. API Rate Limits: Rapiwa and WooCommerce APIs have rate limits. Adjust batch sizes and wait times accordingly. Data Privacy: Ensure compliance with data protection regulations when sending marketing messages. Error Handling: The workflow logs unverified numbers but doesn't have extensive error handling. Consider adding error notifications for failed API calls. Product Availability: The workflow recommends the latest product in a category, but doesn't check if it's in stock. Consider adding stock status verification. Testing: Always test with a small batch before running the workflow on your entire customer list. Useful Links Dashboard: https://app.rapiwa.com Official Website: https://rapiwa.com Documentation: https://docs.rapiwa.com Support & Help WhatsApp: Chat on WhatsApp Discord: SpaGreen Community Facebook Group: SpaGreen Support Website: https://spagreen.net Developer Portfolio: Codecanyon SpaGreen

RapiwaBy Rapiwa
183

Track SDK documentation drift with GitHub, Notion, Google Sheets, and Slack

πŸ“Š Description Automatically track SDK releases from GitHub, compare documentation freshness in Notion, and send Slack alerts when docs lag behind. This workflow ensures documentation stays in sync with releases, improves visibility, and reduces version drift across teams. πŸš€πŸ“šπŸ’¬ What This Template Does Step 1: Listens to GitHub repository events to detect new SDK releases. 🧩 Step 2: Fetches release metadata including version, tag, and publish date. πŸ“¦ Step 3: Logs release data into Google Sheets for record-keeping and analysis. πŸ“Š Step 4: Retrieves FAQ or documentation data from Notion. πŸ“š Step 5: Merges GitHub and Notion data to calculate documentation drift. πŸ” Step 6: Flags SDKs whose documentation is over 30 days out of date. ⚠️ Step 7: Sends detailed Slack alerts to notify responsible teams. πŸ”” Key Benefits βœ… Keeps SDK documentation aligned with product releases βœ… Prevents outdated information from reaching users βœ… Provides centralized release tracking in Google Sheets βœ… Sends real-time Slack alerts for overdue updates βœ… Strengthens DevRel and developer experience operations Features GitHub release trigger for real-time monitoring Google Sheets logging for tracking and auditing Notion database integration for documentation comparison Automated drift calculation (days since last update) Slack notifications for overdue documentation Requirements GitHub OAuth2 credentials Notion API credentials Google Sheets OAuth2 credentials Slack Bot token with chat:write permissions Target Audience Developer Relations (DevRel) and SDK engineering teams Product documentation and technical writing teams Project managers tracking SDK and doc release parity Step-by-Step Setup Instructions Connect your GitHub account and select your SDK repository. Replace YOURGOOGLESHEETID and YOURSHEET_GID with your tracking spreadsheet. Add your Notion FAQ database ID. Configure your Slack channel ID for alerts. Run once manually to validate setup, then enable automation.

Rahul JoshiBy Rahul Joshi
31