Convert blog posts to audio content with Eleven Labs & GPT-4
How It Works: Your Automated Audio Content System
This n8n workflow streamlines the entire process of turning your written articles into engaging audio, distributing them, and tracking their performance. Here's a step-by-step breakdown:
- New Content Detection: The workflow starts by monitoring your blog's RSS feed. As soon as you publish a new article, the system automatically detects it.
- Text Extraction & Cleaning: It extracts the article's title and its main content directly from the RSS feed. Basic cleaning is performed to ensure the text is ready for high-quality voice synthesis.
- Audio Generation with Eleven Labs: The cleaned text is sent to Eleven Labs, a leading AI voice platform. Here, your article is transformed into a natural-sounding MP3 audio file using a voice of your choice.
- Secure Audio Storage: The newly generated MP3 audio file is then uploaded to your Google Drive. This provides a reliable, secure storage solution and generates a shareable public link for easy distribution.
- AI-Powered Metadata Creation: OpenAI steps in to generate compelling metadata for your audio. Based on your article's content, it automatically creates a catchy title, a concise description, and relevant tags or hashtags, perfect for podcast notes or social media captions.
- Centralized Logging: All essential details about the generated audio—including the original article's URL, the audio file's link, and the AI-generated metadata—are logged into a Google Sheet. This gives you a clear, centralized record for tracking and analysis.
- Automated Distribution: The workflow then proceeds to distribute your audio content. This can include sending an email notification (via Gmail) to your subscribers or marketing list with the audio link, or sending an internal alert via Slack to your team. The specific distribution channel can be configured based on your needs.
- Robust Error Handling: The entire workflow is built with Try/Catch blocks. If any part of the process encounters an error, the system will gracefully handle it and send an immediate notification to you via Slack, ensuring you're always aware of the workflow's status.
Setup Steps
To get this powerful automated audio content system up and running in your n8n instance, follow these steps:
-
Prepare Your Cloud Services & API Credentials:
- Eleven Labs: Create an account and obtain your API Key.
- OpenAI: Get your API Key.
- Google Drive: Ensure you have a Google account. In n8n, set up a Google Drive credential. Create a dedicated folder in your Google Drive for your audio files and note its Folder ID (found in the URL when you open the folder).
- Google Sheets: Set up a Google Sheets credential in n8n. Create a new Google Sheet for logging with these exact column headers:
Article URL,Article Title,Audio File URL,Generated Audio Title,Generated Audio Description,Generated Audio Tags,Status,Timestamp. - Gmail / SMTP: Set up your Gmail credential or a generic Email credential in n8n.
- Slack: Set up your Slack credential in n8n. Identify the Channel IDs where you want to receive general updates and error alerts.
-
Identify Your Text Content Source:
- Ensure your blog or content platform has an accessible RSS Feed. The content within this feed (specifically the
descriptionorcontentfield) should be relatively clean text, as this will be directly processed for audio generation.
- Ensure your blog or content platform has an accessible RSS Feed. The content within this feed (specifically the
-
Build the n8n Workflow:
- Open your n8n instance and create a new, blank workflow.
- Add each node as described in the "How It Works" section and the previous detailed explanations. Connect them sequentially.
- Configure Each Node's Parameters:
- RSS Feed: Enter your blog's RSS feed URL.
- Set (Extract & Clean Article Data): Use expressions to extract
title,link, and clean thedescriptionorcontentfrom the RSS feed. - ElevenLabs: Select your Eleven Labs credential, specify your chosen
Voice ID(you can find this in your Eleven Labs dashboard), and ensure theTextfield points to your cleaned article content. - Google Drive: Select your Google Drive credential and enter the Folder ID you noted earlier. Ensure
Allow Anyone to Readis set toTrue. - OpenAI: Select your OpenAI credential. Configure the "Chat Completion" node with appropriate system and user prompts to generate JSON output for
audioTitle,audioDescription, andaudioTags. - Set (Combine All Metadata): Use expressions to neatly collect and organize all the data from previous nodes into a single item.
- Google Sheets: Select your Google Sheets credential. Enter your Spreadsheet ID and Sheet Name. Map the data from the previous "Set" node to match your Google Sheet's column headers precisely.
- If: Set up your condition for email distribution (e.g., based on specific tags in
generatedAudioTags). - Gmail / Slack: Configure the
Toaddress/Chat IDand the message content for your notifications. - Try/Catch & Error Slack: Connect the
Trybranch to your very first node (RSS Feed) and theCatchbranch to the error Slack notification. Configure the error message in Slack to include relevant details.
-
Test and Activate:
- Manual Test: Before activating, run the workflow manually in n8n. This lets you observe each step's execution and verify that data flows correctly between nodes.
- Verify Outputs: After a successful test run, check your Google Drive for the uploaded audio file, open your Google Sheet to confirm the data has been logged correctly, and check your email/Slack for the notifications.
- Activate: Once you've thoroughly tested and confirmed the workflow is functioning as intended, activate it in n8n to enable automatic execution.
Convert Blog Posts to Audio Content with Eleven Labs & GPT-4
This n8n workflow automates the process of converting blog post content into audio, leveraging AI for content summarization and text-to-speech generation. It monitors an RSS feed for new blog posts, processes them using OpenAI's GPT-4 for summarization, generates audio using Eleven Labs, and then stores the audio in Google Drive while notifying relevant teams via Slack and email.
What it does
- Monitors RSS Feed: Triggers on new entries in a specified RSS feed (e.g., a blog).
- Summarizes Blog Post: Uses OpenAI (GPT-4) to summarize the content of the new blog post.
- Generates Audio: Converts the summarized text into an audio file using Eleven Labs' text-to-speech capabilities.
- Uploads to Google Drive: Stores the generated audio file in a designated folder within Google Drive.
- Notifies via Slack: Sends a notification to a Slack channel with details about the new audio content.
- Sends Email Notification: Dispatches an email via Gmail to inform stakeholders about the newly created audio.
- Logs to Google Sheets: Records details of the processed blog post and generated audio in a Google Sheet.
Prerequisites/Requirements
- n8n Instance: A running instance of n8n.
- RSS Feed URL: The URL of the blog's RSS feed to monitor.
- OpenAI API Key: For GPT-4 summarization.
- Eleven Labs API Key: For text-to-speech generation.
- Google Drive Account: For storing audio files.
- Google Sheets Account: For logging workflow activity.
- Slack Account: For sending notifications.
- Gmail Account: For sending email notifications.
Setup/Usage
- Import the workflow: Download the provided JSON and import it into your n8n instance.
- Configure Credentials:
- OpenAI: Set up your OpenAI API key credential.
- Eleven Labs: Set up your Eleven Labs API key credential.
- Google Drive: Configure your Google Drive OAuth2 or API key credential.
- Google Sheets: Configure your Google Sheets OAuth2 or API key credential.
- Slack: Configure your Slack OAuth2 or API key credential.
- Gmail: Configure your Gmail OAuth2 or API key credential.
- Update Node Settings:
- RSS Feed Trigger: Enter the URL of the RSS feed you wish to monitor.
- OpenAI: Ensure the correct model (e.g.,
gpt-4) and summarization prompt are configured. - Eleven Labs: Select your desired voice and other text-to-speech settings.
- Google Drive: Specify the target folder ID where audio files should be uploaded.
- Slack: Configure the Slack channel ID and message content.
- Gmail: Set the recipient email address, subject, and body for the notification email.
- Google Sheets: Specify the Spreadsheet ID and Sheet Name for logging.
- Activate the Workflow: Once all configurations are complete, activate the workflow. It will now automatically process new blog posts as they appear in the RSS feed.
Related Templates
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.
Transform Readwise highlights into weekly content ideas with Gemini AI
Turn Your Reading Habit into a Content Creation Engine This workflow is built for one core purpose: to maximize the return on your reading time. It turns your passive consumption of articles and highlights into an active system for generating original content and rediscovering valuable ideas you may have forgotten. Why This Workflow is Valuable End Writer's Block Before It Starts: This workflow is your personal content strategist. Instead of staring at a blank page, you'll start your week with a list of AI-generated content ideas—from LinkedIn posts and blog articles to strategic insights—all based on the topics you're already deeply engaged with. It finds the hidden connections between articles and suggests novel angles for your next piece. Rescue Your Insights from the Digital Abyss: Readwise is fantastic for capturing highlights, but the best ones can get lost over time. This workflow acts as your personal curator, automatically excavating the most impactful quotes and notes from your recent reading. It doesn't just show them to you; it contextualizes them within the week's key themes, giving them new life and relevance. Create an Intellectual Flywheel: By systematically analyzing your reading, generating content ideas, and saving those insights back into your "second brain," you create a powerful feedback loop. Your reading informs your content, and the process of creating content deepens your understanding, making every reading session more valuable than the last. How it works This workflow automates the process of generating a "Weekly Reading Insights" summary based on your activity in Readwise. Trigger: It can be run manually or on a weekly schedule Fetch Data: It fetches all articles and highlights you've updated in the last 7 days from your Readwise account. Filter & Match: It filters for articles that you've read more than 10% of and then finds all the corresponding highlights for those articles. Generate Insights: It constructs a detailed prompt with your reading data and sends it to an AI model (via OpenRouter) to create a structured analysis of your reading patterns, key themes, and content ideas. Save to Readwise: Finally, it takes the AI-generated markdown, converts it to HTML, and saves it back to your Readwise account as a new article titled "Weekly Reading Insights". Set up steps Estimated Set Up Time: 5-10 minutes. Readwise Credentials: Authenticate the two HTTP Request nodes and the two Fetch nodes with your Readwise API token Get from Reader API. Also check how to set up Header Auth AI Model Credentials: Add your OpenRouter API key to the OpenRouter Chat Model node. You can swap this for any other AI model if you prefer. Customize the Prompt: Open the Prepare Prompt Code node to adjust the persona, questions, and desired output format. This is where you can tailor the AI's analysis to your specific needs. Adjust Schedule: Modify the Monday - 09:00 Schedule Trigger to run on your preferred day and time.
Generate Weather-Based Date Itineraries with Google Places, OpenRouter AI, and Slack
🧩 What this template does This workflow builds a 120-minute local date course around your starting point by querying Google Places for nearby spots, selecting the top candidates, fetching real-time weather data, letting an AI generate a matching emoji, and drafting a friendly itinerary summary with an LLM in both English and Japanese. It then posts the full bilingual plan with a walking route link and weather emoji to Slack. 👥 Who it’s for Makers and teams who want a plug-and-play bilingual local itinerary generator with weather awareness — no custom code required. ⚙️ How it works Trigger – Manual (or schedule/webhook). Discovery – Google Places nearby search within a configurable radius. Selection – Rank by rating and pick the top 3. Weather – Fetch current weather (via OpenWeatherMap). Emoji – Use an AI model to match the weather with an emoji 🌤️. Planning – An LLM writes the itinerary in Markdown (JP + EN). Route – Compose a Google Maps walking route URL. Share – Post the bilingual itinerary, route link, and weather emoji to Slack. 🧰 Requirements n8n (Cloud or self-hosted) Google Maps Platform (Places API) OpenWeatherMap API key Slack Bot (chat:write) LLM provider (e.g., OpenRouter or DeepL for translation) 🚀 Setup (quick) Open Set → Fields: Config and fill in coords/radius/time limit. Connect Credentials for Google, OpenWeatherMap, Slack, and your LLM. Test the workflow and confirm the bilingual plan + weather emoji appear in Slack. 🛠 Customize Adjust ranking filters (type, min rating). Modify translation settings (target language or tone). Change output layout (side-by-side vs separated). Tune emoji logic or travel mode. Add error handling, retries, or logging for production use.