Convert Text to Speech Using OpenAI TTS API

Overview

This workflow converts any text into natural-sounding speech using OpenAI's Text-to-Speech (TTS) API. It is ideal for generating audio content for accessibility, voiceovers, podcasts, or language learning. The workflow is triggered manually for testing, but can easily be adapted to run on a schedule, via webhook, or as part of a larger automation.

Node-by-Node Breakdown

  • When clicking "Test workflow" (Manual Trigger) — No auth. This node starts the workflow when you click the "Execute Workflow" button in the n8n editor. It has no parameters and is used for testing.
  • Set input text and TTS voice (Set) — No auth. This node defines the text to be converted and the voice to use. It outputs a JSON object with two fields:
    • input_text: The text you want to turn into speech (e.g., "The quick brown fox jumped over the lazy dog.")
    • voice: The voice model to use (e.g., "alloy"). Other options include "echo", "fable", "onyx", "nova", and "shimmer".
  • Send HTTP Request to OpenAI's TTS Endpoint (HTTP Request) — API Key auth (via OpenAI credential). This node sends a POST request to https://api.openai.com/v1/audio/speech with the following body parameters:
    • model: tts-1 (the TTS model)
    • input: The text from the previous node (using expression {{ $json.input_text }})
    • voice: The voice from the previous node (using expression {{ $json.voice }}) The request is authenticated using an OpenAI API key stored in an n8n credential. The response is a binary MP3 audio file.

Setup Instructions

  1. OpenAI Account: You need an OpenAI account with API access. Obtain an API key from the OpenAI dashboard.
  2. n8n Credential: In n8n, create a new credential of type "OpenAI". Paste your API key into the credential.
  3. Configure the HTTP Request Node: The node is already set to use the OpenAI credential. Ensure the credential is selected in the node's settings.
  4. Customize Text and Voice: Modify the input_text and voice values in the Set node as needed. The maximum input length is 4,000 tokens.

Use Cases and Variations

  • Automated Podcast Generation: Replace the manual trigger with a Schedule Trigger to generate daily audio summaries from a news feed.
  • Accessibility: Use a Webhook Trigger to accept text from a form or chat, then return the audio file to the user.
  • Language Learning: Combine with a Translate node to convert foreign language text into speech.
  • Content Creation: Integrate with a Google Drive node to save the generated MP3 files automatically.
  • Voice Customization: Experiment with different voice options (alloy, echo, fable, etc.) to match the tone of your content.
8 nodesmanual triggerAI
SetHTTP RequestSticky Note

Workflow JSON

{
  "id": "6Yzmlp5xF6oHo1VW",
  "meta": {
    "instanceId": "173f55e6572798fa42ea9c5c92623a3c3308080d3fcd2bd784d26d855b1ce820"
  },
  "name": "Text to Speech (OpenAI)",
  "tags": [],
  "nodes": [
    {
      "id": "938fedbd-e34c-40af-af2f-b9c669e1a6e9",
      "name": "When clicking \"Test workflow\"",
      "type": "n8n-nodes-base.manualTrigger",
      "position": [
        380,
        380
      ],
      "parameters": {},
      "typeVersion": 1
    },
    {
      "id": "1d59db5d-8fe6-4292-a221-a0d0194c6e0c",
      "name": "Set input text and TTS voice",
      "type": "n8n-nodes-base.set",
      "position": [
        760,
        380
      ],
      "parameters": {
        "mode": "raw",
        "options": {},
        "jsonOutput": "{\n  \"input_text\": \"The quick brown fox jumped over the lazy dog.\",\n  \"voice\": \"alloy\"\n}\n"
      },
      "typeVersion": 3.2
    },
    {
      "id": "9d54de1d-59b7-4c1f-9e88-13572da5292c",
      "name": "Send HTTP Request to OpenAI's TTS Endpoint",
      "type": "n8n-nodes-base.httpRequest",
      "position": [
        1120,
        380
      ],
      "parameters": {
        "url": "https://api.openai.com/v1/audio/speech",
        "method": "POST",
        "options": {},
        "sendBody": true,
        "sendHeaders": true,
        "authentication": "predefinedCredentialType",
        "bodyParameters": {
// ... truncated (copy to see full JSON)

How to Import This Workflow

  1. 1Copy the workflow JSON above using the Copy Workflow JSON button.
  2. 2Open your n8n instance and go to Workflows.
  3. 3Click Import from JSON and paste the copied workflow.

Don't have an n8n instance? Start your free trial at n8nautomation.cloud

Related Templates

AI-Powered Unsplash to Pinterest Workflow with RAG

Overview This workflow provides an intelligent pipeline for processing and storing data related to Unsplash images for Pinterest. It uses a Retrieval-Augmented Generation (RAG) architecture to automatically ingest content, generate embeddings, store them in a vector database (Supabase), and then process queries using an AI agent. The workflow is triggered via a webhook, making it suitable for integration with external applications or manual testing. Node-by-Node Breakdown Sticky Note — A visual note for documentation purposes. It displays the title "Automated workflow: Unsplash to Pinterest" on the canvas. No authentication required. Webhook Trigger — Listens for incoming HTTP POST requests at the path . This is the entry point for the workflow. When triggered, it passes the incoming data to the next nodes. (No auth) Text Splitter — Splits incoming text into chunks of 400 characters with a 40-character overlap. This prepares the data for embedding by breaking it into manageable pieces. (No auth) Embeddings (Cohere) — Generates vector embeddings for each text chunk using the model from Cohere. These embeddings represent the semantic meaning of the text. (API Key auth — requires a Cohere API key) Supabase Insert — Inserts the generated embeddings into a Supabase vector store named . This stores the data for later retrieval. (API Key auth — requires Supabase credentials) Supabase Query — Queries the same Supabase vector store () to retrieve relevant vectors based on similarity search. This is used by the RAG agent to find context. (API Key auth — requires Supabase credentials) Vector Tool — Wraps the Supabase vector store as a tool that the AI agent can use to retrieve context. It's labeled "Vector context" for clarity. (No auth — uses the Supabase connection from the previous nodes) Window Memory — Provides a buffer window memory for the AI agent, allowing it to maintain conversation context across multiple interactions. (No auth) Chat Model (OpenAI) — The language model that powers the AI agent. It uses OpenAI's chat model to process queries and generate responses. (API Key auth — requires an OpenAI API key) RAG Agent — The core AI agent that combines the chat model, vector tool, and memory. It processes incoming data with the prompt: "Process the following data for task 'Unsplash to Pinterest':" and includes a system message: "You are an assistant for Unsplash to Pinterest". (No auth — uses connections to other nodes) Append Sheet (Google Sheets) — Appends the AI agent's output to a Google Sheet. It writes to a sheet named "Log" in a document identified by . The column "Status" is populated with the agent's response text. (OAuth2 — requires Google Sheets API credentials) Slack Alert — Sends an error notification to the Slack channel if the RAG Agent encounters an error. The message includes the error details. (OAuth2 — requires Slack API credentials) Setup Instructions To use this workflow, you'll need accounts and API keys for the following services: Cohere: Sign up at cohere.com and generate an API key for the embeddings model. Supabase: Create a project at supabase.com and set up a vector store with the name . You'll need your Supabase URL and service role key. OpenAI: Get an API key from platform.openai.com for the chat model. Google Sheets: Create a Google Sheet with a sheet named "Log" and note the Sheet ID from the URL. Set up OAuth2 credentials in the Google Cloud Console. Slack: Create a Slack app, add it to your workspace, and obtain OAuth tokens. Create a channel named for error notifications. Configure each node's credentials in n8n by clicking on the node and selecting "Add Credential" or selecting existing ones. Use Cases and Variations This workflow is ideal for: Content Curation: Automatically process and store descriptions of Unsplash images for later retrieval and Pinterest posting. Knowledge Base: Build a searchable database of image metadata with semantic search capabilities. Automated Content Moderation: Use the AI agent to analyze image descriptions and flag inappropriate content before posting. Possible Adaptations: Replace the webhook trigger with a Schedule Trigger to run the workflow at regular intervals. Swap the Cohere embeddings with OpenAI embeddings or Hugging Face embeddings. Instead of Google Sheets, output to Airtable, Notion, or PostgreSQL. Add an HTTP Request node after the RAG Agent to post processed data directly to Pinterest's API. Use a different vector store like Pinecone or Qdrant instead of Supabase.

12 nodes

Telegram AI Chatbot with OpenAI GPT

Overview This workflow turns your Telegram bot into a smart AI assistant powered by OpenAI's GPT models. Every time someone sends a message to your bot, the workflow forwards it to GPT, generates a context-aware reply, and sends it back — all in a few seconds. It's a cost-effective alternative to paid chatbot platforms, giving you full control over the personality and rules via a system prompt. How It Works The workflow is triggered by an incoming Telegram message, processes it through an AI model, and replies to the same chat. Here are the nodes and their roles: Telegram Message In (Telegram Bot Token auth) — Watches for new messages in your bot's chat. Configured to listen for updates only. No additional parameters. AI Reply (OpenAI API Key auth) — Sends the user's message to OpenAI's GPT model (here as a placeholder – you can choose any available model). The request includes a system prompt that defines the bot's behavior (e.g., "You are a helpful, concise assistant...") and the user message from the Telegram trigger. This node has retry on fail enabled (3 retries, 5 seconds apart) to handle transient errors. Send Reply (Telegram Bot Token auth) — Takes the AI's response (from ) and sends it back to the original chat, using the from the trigger. No retry is configured to avoid duplicate messages. Setup Instructions Create a Telegram Bot: Open Telegram, search for , and send . Follow the prompts to get a bot token (e.g., ). Get an OpenAI API Key: Sign up at platform.openai.com, create an API key, and ensure it has access to the GPT model you want to use. Configure Credentials in n8n: - For the Telegram nodes (Trigger and Send), create a new credential of type "Telegram API" and paste your bot token. - For the AI Reply node, create a credential of type "OpenAI" and paste your API key. Edit the System Prompt: Open the AI Reply node and modify the system message to change the bot's personality, tone, or knowledge constraints. For example, you can make it a support agent, a tutor, or a sarcastic friend. Activate the Workflow: Once saved, toggle the workflow to "Active". Send a message to your bot on Telegram to test it. Use Cases & Variations Customer Support: Replace the system prompt with your FAQ and company policies to create a 24/7 support bot. Personal Assistant: Add a directive to remember context (requires additional memory nodes like Window Buffer Memory) or integrate with calendars/tasks. Multi‑language Translator: Change the system prompt to "Translate the user's message to Spanish" and use the AI reply as a translation service. Content Generator: Have the bot generate blog posts, jokes, or summaries based on user requests. Error Handling: The workflow includes retries on the AI node only. If you want to be notified of failures, add an Error Trigger workflow that sends alerts to Slack or email.

6 nodes

Telegram AI Bot with DALL-E Image Generation using LangChain

Overview This workflow creates an intelligent Telegram bot that leverages OpenAI's GPT-4o and DALL-E 3 models through n8n's LangChain integration. The bot can hold context-aware conversations (remembering the last 10 messages per user) and generate images on demand—all via simple Telegram messages. It's ideal for building personal assistants, creative bots, or customer support agents that need visual output. Node-by-Node Walkthrough Here's every node in the workflow, along with its authentication method and key configuration: Listen for incoming events (Telegram Trigger — No auth; bot token set in node credential) – Listens for all types of Telegram updates (messages, commands, etc.). No authentication parameters are required directly on the node; the Telegram bot token is configured via the node's credential settings. AI Agent (LangChain Agent — No auth; relies on connected sub‑nodes) – The core of the workflow. It receives the incoming message text and uses the attached language model (OpenAI Chat Model), memory (Window Buffer Memory), and tools (Send back an image / Generate image in Dalle) to decide what action to take. OpenAI Chat Model (LangChain Chat Model — API Key auth via credential) – Uses with a temperature of 0.7 and frequency penalty of 0.2. This model powers the agent's text responses. Window Buffer Memory (LangChain Memory — No auth) – Stores the last 10 messages per user (keyed by Telegram chat ID) to maintain conversational context. Generate image in Dalle (LangChain HTTP Request Tool — API Key auth via credential) – A custom tool that sends a POST request to with model and a prompt (provided by the AI agent). The tool description tells the agent to call it when the user asks to draw something. Send back an image (Telegram Tool — API Key auth via Telegram credential) – Sends a file (image URL from the DALL-E response) to the user's chat ID using the operation. This is exposed as a tool the AI agent can call. Send final reply (Telegram Node — API Key auth via Telegram credential) – Sends the AI agent's text output (from ) back to the user. Note: On error, the workflow continues to the error output (useful for debugging). Detailed Flow The Telegram Trigger catches any incoming message from your bot. The message text is passed to the AI Agent. The agent uses the OpenAI Chat Model to understand the request and generate a response. It also checks the Window Buffer Memory for recent conversation history. If the user asks for an image, the agent calls the Generate image in Dalle tool, which returns an image URL. The agent then uses the Send back an image tool to send that image to the user. For all other requests, the agent produces a text response, which is sent via the Send final reply node. Setup Instructions Telegram Bot – Create a bot via @BotFather and get the API token. In n8n, create a Telegram credential and paste the token. OpenAI Account – Obtain an API key from OpenAI's platform. Create an credential in n8n and paste the key. This credential is used by both the Chat Model and the DALL-E tool. Workflow Activation – After configuring the credentials, activate the workflow. n8n will automatically set up the webhook for the Telegram trigger (no manual URL needed—n8n handles it internally). Test – Send a message to your bot on Telegram. Try asking a question or say “Draw a cat wearing a hat” to trigger image generation. Use Cases & Variations Personal Assistant – Extend with additional tools (web search, calendar lookup, weather API) to make a full‑fledged chatbot. Customer Support – Replace the OpenAI model with a fine‑tuned model or add a fallback to a human agent using n8n's error handling. Image Editor – Modify the DALL-E tool to accept style parameters or multiple images. Multi‑Language – Add a translation node before the AI agent to support multiple languages. Logging – Insert a database node (e.g., Google Sheets, PostgreSQL) to store conversation logs for analysis.

8 nodes

Ready to automate with n8n?

Get affordable managed n8n hosting with 24/7 support.