Back to Catalog

Clone and change your voice 🤖🎙️with Elevenlabs and Telegram

DavideDavide
379 views
2/3/2026
Official Page

This workflow creates a voice AI assistant accessible via Telegram that leverages ElevenLabs* powerful voice synthesis technology. Users can either clone their own voice or transform their voice using pre-existing voice models, all through simple voice messages sent to a Telegram bot.

*ONLY FOR STARTER, CREATOR, PRO PLAN

This workflow allows users to:

  1. Clone their voice by sending a voice message to a Telegram bot (creates a new voice profile on ElevenLabs)
  2. Change their voice to a cloned voice and save the output to Google Drive

For Best Results

Important Considerations for Best Results: For optimal voice cloning via Telegram voice messages:

1. Recording Quality & Environment

  • Record in a quiet room with minimal echo and background noise
  • Use a consistent microphone position (10-15cm from mouth)
  • Ensure clear audio without distortion or clipping

2. Content Selection & Variety

  • Send 1 voice messages totaling 5-10 minutes of speech
  • Include diverse vocal sounds, tones, and natural speaking cadence
  • Use complete sentences rather than isolated words

3. Audio Consistency

  • Maintain consistent volume, tone, and distance from microphone
  • Avoid interruptions, laughter, coughs, or background voices
  • Speak naturally without artificial effects or filters

4. Technical Preparation

  • Ensure Telegram isn't overly compressing audio (use HQ recording)
  • Record all messages in the same session with same conditions
  • Include both neutral speech and varied emotional expressions

How it works

  1. Trigger
    The workflow starts with a Telegram trigger that listens for incoming messages (text, voice notes, or photos).

  2. Authorization check
    A Code node checks whether the sender’s Telegram user ID matches your predefined ID. If not, the process stops.

  3. Message routing
    A Switch node routes the message based on its type:

    • Text → Not processed further in this flow.
    • Voice message → Sent to the “Get audio” node to retrieve the audio file from Telegram.
    • Photo → Not processed further in this flow.
  4. Two main options
    From the “Get audio” node, the workflow splits into two possible paths:

    • Option 1 – Clone voice
      The audio file is sent to ElevenLabs via an HTTP request to create a new cloned voice. The voice ID is returned and can be saved for later use.
    • Option 2 – Voice changer
      The audio is sent to ElevenLabs for speech-to-speech conversion using a pre-existing cloned voice (voice ID must be set in the node parameters). The resulting audio is saved to Google Drive.
  5. Output

    • Cloned voice ID (for Option 1).
    • Converted audio file uploaded to Google Drive (for Option 2).

Set up steps

  1. Telegram bot setup

    • Create a bot via BotFather and obtain the API token.
    • Set up the Telegram Trigger node with your bot credentials.
  2. Authorization configuration

    • In the “Sanitaze” Code node, replace XXX with your Telegram user ID to restrict access.
  3. ElevenLabs API setup

    • Get an API key from ElevenLabs.
    • Configure the HTTP Request nodes (“Create Cloned Voice” and “Generate cloned audio”) with:
      • API key in the Xi-Api-Key header.
      • Appropriate endpoint URLs (including voice ID for speech-to-speech).
  4. Google Drive setup (for Option 2)

    • Set up Google Drive OAuth2 credentials in n8n.
    • Specify the target folder ID in the “Upload file” node.
  5. Voice ID configuration

    • For voice cloning: The voice name can be customized in the “Create Cloned Voice” node.
    • For voice changing: Replace XXX in the “Generate cloned audio” node URL with your ElevenLabs voice ID.
  6. Test the workflow

    • Activate the workflow.
    • Send a voice note from your authorized Telegram account to trigger cloning or voice conversion.

👉 Subscribe to my new YouTube channel. Here I’ll share videos and Shorts with practical tutorials and FREE templates for n8n.

image


Need help customizing?

Contact me for consulting and support or add me on Linkedin.

ElevenLabs Voice Cloning and Transformation with Telegram

This n8n workflow allows you to interact with ElevenLabs for voice cloning and transformation directly through Telegram. You can send voice messages via Telegram, which will then be processed by ElevenLabs to clone or alter the voice, and the resulting audio will be sent back to you.

What it does

This workflow automates the following steps:

  1. Listens for Telegram Voice Messages: It acts as a Telegram bot, waiting for incoming voice messages from users.
  2. Downloads Voice Message: Upon receiving a voice message, it downloads the audio file from Telegram.
  3. Processes with ElevenLabs (Placeholder): The workflow is designed to integrate with ElevenLabs. Currently, the "HTTP Request" node is a placeholder for making API calls to ElevenLabs for voice cloning or transformation.
  4. Sends Transformed Audio to Google Drive (Placeholder): The "Google Drive" node is a placeholder for saving the processed audio to Google Drive.
  5. Sends Audio Back to Telegram: The transformed audio (or a confirmation) is sent back to the user via Telegram.
  6. Conditional Logic: A "Switch" node is included, suggesting potential branching logic based on the input or processing results, though its specific conditions are not defined in the provided JSON.
  7. Custom Logic (Placeholder): A "Code" node is present for implementing custom JavaScript logic, which could be used for advanced audio processing, ElevenLabs API interaction, or Telegram message formatting.

Prerequisites/Requirements

To use this workflow, you will need:

  • Telegram Bot Token: A Telegram bot configured and its API token.
  • ElevenLabs API Key: An ElevenLabs account and API key for voice synthesis and cloning.
  • Google Drive Account: A Google Drive account if you intend to save processed audio files.
  • n8n Instance: An active n8n instance to host and run the workflow.

Setup/Usage

  1. Import the workflow: Import the provided JSON into your n8n instance.
  2. Configure Telegram Trigger:
    • Set up your Telegram Bot credential in n8n.
    • Configure the "Telegram Trigger" node to listen for voice messages.
  3. Configure ElevenLabs (HTTP Request):
    • Edit the "HTTP Request" node to make the necessary API calls to ElevenLabs. This will involve:
      • Setting the correct ElevenLabs API endpoint for voice cloning or transformation.
      • Including your ElevenLabs API key in the headers or body.
      • Passing the downloaded audio file from Telegram as input to ElevenLabs.
      • Handling the response from ElevenLabs (e.g., extracting the transformed audio).
  4. Configure Google Drive (Optional):
    • Set up your Google Drive credential in n8n.
    • Configure the "Google Drive" node to upload the processed audio files to a specified folder.
  5. Configure Telegram (Send Audio):
    • Ensure the "Telegram" node is configured with your Telegram Bot credential.
    • Set it up to send the audio file received from ElevenLabs back to the original Telegram chat.
  6. Implement Custom Logic (Code Node - Optional):
    • If advanced logic is required, modify the "Code" node to process data, prepare API requests, or format messages.
  7. Define Switch Node Logic (Optional):
    • If you need conditional routing, define the conditions in the "Switch" node to direct the workflow based on specific criteria (e.g., message content, ElevenLabs response status).
  8. Activate the workflow: Once configured, activate the workflow in n8n. Your Telegram bot will now be ready to process voice messages.

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

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