HumationHuman + Automation
Back to Catalog

Convert PDF articles to audio podcasts with Google TTS & Cloudflare R2

Dev DuttaDev Dutta
1002 views
2/3/2026
AIAssistantOpenAIChatbotFile Upload
Official Page

Convert PDF Articles to Podcast

Workflow Name: Convert PDF Articles to Podcast Author: Devjothi Dutta Category: Productivity, Content Creation, Automation Complexity: Medium Setup Time: 45-60 minutes

Convert PDF to Podcast N8N.png

📖 Description

Transform any PDF article, research paper, or document into a high-quality audio podcast automatically. This workflow extracts text from PDFs, converts it to natural-sounding speech using Google Cloud Text-to-Speech, stores the audio files in cloud storage, and generates an RSS feed compatible with all major podcast apps (Apple Podcasts, Spotify, Pocket Casts, etc.).

Perfect for consuming long-form content while commuting, exercising, or multitasking. Turn your reading list into a personal podcast feed.

👥 Who's it for

For Professionals:

  • Convert industry reports and whitepapers to audio
  • Listen to research papers during commutes
  • Stay updated with long-form articles hands-free

For Students:

  • Turn textbooks and study materials into audio
  • Create audio versions of lecture notes
  • Study while exercising or commuting

For Content Creators:

  • Repurpose written content into audio format
  • Create podcast episodes from blog posts
  • Reach audio-focused audiences

For Busy Readers:

  • Convert saved articles to a personal podcast
  • Listen to newsletters and essays on the go
  • Build a private audio library

✨ Key Features

  • 📄 PDF Text Extraction - Automatically extracts text from any PDF file
  • 🎙️ Natural Voice Synthesis - High-quality WaveNet voices from Google Cloud TTS
  • ☁️ Cloud Storage - Files hosted on Cloudflare R2 (S3-compatible) with public URLs
  • 📻 RSS Feed Generation - Full iTunes-compatible podcast feed with metadata
  • 📧 Email Notifications - Instant alerts when new episodes are ready
  • 🎨 Custom Branding - Configurable podcast name, artwork, and descriptions
  • ⚙️ Modular Configuration - Easy-to-update centralized config node
  • 🔄 Automated Workflow - Set it and forget it - fully automated pipeline

🛠️ Requirements

Required Services:

  1. n8n (self-hosted or cloud) - Workflow automation platform
  2. Google Cloud Platform - Text-to-Speech API access
    • Free tier: 1 million characters/month (WaveNet voices)
    • Paid: $16 per 1 million characters
  3. Cloudflare R2 - Object storage for audio files and RSS feed
    • Free tier: 10GB storage, unlimited egress
  4. Email Service - SMTP or email service for notifications

Required Community Nodes:

  • Cloudflare R2 Storage (n8n-nodes-cloudflare-r2-storage)
    • Install via: Settings → Community Nodes → Install
    • Search for: n8n-nodes-cloudflare-r2-storage
    • Important: Install this BEFORE importing the workflow

Optional:

  • Custom domain for podcast feed URLs
  • Podcast artwork (3000x3000px recommended)

📦 What's Included

This workflow package includes:

🚀 Quick Start

  1. Install community node (required):
    • Go to Settings → Community Nodes → Install
    • Search for: n8n-nodes-cloudflare-r2-storage
    • Click Install and wait for completion
  2. Import workflow into your n8n instance
  3. Configure credentials:
    • Google Cloud TTS API key
    • Cloudflare R2 credentials (Access Key ID + Secret)
    • SMTP email credentials
  4. Update Workflow Config node with your settings:
    • R2 bucket name and public URL
    • Podcast name and description
    • Artwork URL
    • Email recipient
  5. Test with a sample PDF to verify setup
  6. Add RSS feed URL to your podcast app

📊 Workflow Stats

  • Nodes: 10
  • Complexity: Medium
  • Execution Time: ~2-5 minutes per PDF (depends on length)
  • Monthly Cost: $0-20 (depending on usage and free tiers)
  • Maintenance: Minimal (set and forget)

🎨 Customization Options

  • Change TTS voice (20+ English voices available)
  • Adjust speech speed and pitch
  • Customize RSS feed metadata
  • Add custom intro/outro audio
  • Configure file retention policies
  • Set up webhook triggers for remote submission

🔧 How it Works

  1. User uploads PDF to n8n
  2. Text is extracted from PDF
  3. Text is sent to Google TTS API
  4. Audio file (.mp3) is generated
  5. Files uploaded to R2 storage:
    • Original PDF
    • Generated MP3 audio
  6. RSS feed is generated/updated with:
    • Episode title (from PDF filename)
    • Audio URL
    • Duration and file size
    • Publication date
    • Rich HTML description
  7. RSS feed uploaded to R2
  8. Email notification sent with episode details

💡 Pro Tips

  • Voice Selection: Test different WaveNet voices to find your preferred style
  • Batch Processing: Process multiple PDFs by running workflow multiple times
  • Quality vs Cost: WaveNet voices sound better but cost more than Standard voices
  • Storage Management: Set up R2 lifecycle rules to auto-delete old episodes
  • Custom Domains: Use Cloudflare for custom podcast feed URLs

🔗 Related Workflows

  • PDF to Email Summary
  • Document Translation to Audio
  • Blog RSS to Podcast
  • Multi-language Audio Generation

📧 Support & Feedback

For questions, issues, or feature requests:

📄 License

MIT License - Free to use, modify, and distribute

⭐ If you find this workflow useful, please share your feedback and star the workflow!

n8n PDF Article to Audio Podcast Converter with Google TTS and Cloudflare R2

This n8n workflow automates the process of converting PDF articles into audio podcasts using Google Text-to-Speech (TTS) and storing the resulting audio files on Cloudflare R2. It provides a convenient way to transform written content into an audible format, making it accessible as a podcast.

What it does

This workflow streamlines the creation of audio podcasts from PDF articles through the following steps:

  1. Triggers on Form Submission: The workflow starts when a user submits a form, likely providing the PDF article or its URL.
  2. Reads PDF Content: It extracts the text content from the submitted PDF file.
  3. Prepares Text for TTS: The extracted text is processed and prepared for Google Text-to-Speech, potentially splitting it into manageable chunks if the article is long.
  4. Converts Text to Speech (Google TTS): The prepared text is sent to Google Text-to-Speech to generate audio files.
  5. Uploads Audio to Cloudflare R2: The generated audio files are then uploaded to a Cloudflare R2 bucket for storage and distribution.
  6. Sends Email Notification: An email notification is sent to a specified recipient, likely with a link to the generated podcast or confirmation of the process.

Prerequisites/Requirements

To use this workflow, you will need:

  • n8n Instance: A running n8n instance.
  • Google Cloud Account: For Google Text-to-Speech (TTS) API access. You will need to enable the Cloud Text-to-Speech API and set up appropriate credentials (e.g., a Service Account key).
  • Cloudflare Account: With Cloudflare R2 enabled. You will need R2 API credentials (Access Key ID and Secret Access Key).
  • SMTP Credentials: For sending email notifications.

Setup/Usage

  1. Import the Workflow: Import the provided JSON into your n8n instance.
  2. Configure Credentials:
    • Google Cloud TTS: Set up a Google Cloud credential in n8n for the Google Text-to-Speech node.
    • Cloudflare R2: Configure a Cloudflare R2 credential in n8n with your Access Key ID and Secret Access Key.
    • SMTP: Set up an Email Send (SMTP) credential for sending notifications.
  3. Configure Nodes:
    • On form submission: Customize the form fields as needed for inputting the PDF article (e.g., file upload or URL).
    • Read PDF: Ensure this node is correctly configured to receive the PDF file from the form trigger.
    • Code: This node likely contains logic to process the PDF text. Review and adjust it if necessary, especially for handling large documents or specific formatting.
    • HTTP Request (Google TTS): Configure this node to use your Google Cloud TTS credentials and specify the desired voice, language, and audio format.
    • HTTP Request (Cloudflare R2): Configure this node to use your Cloudflare R2 credentials, specify your bucket name, and define the object key (filename) for the uploaded audio.
    • Edit Fields (Set): This node might be used to prepare data for subsequent steps, such as the audio file name or email content.
    • Merge: This node likely combines data from different branches of the workflow before the final email.
    • Send Email: Customize the recipient, subject, and body of the email notification, potentially including a link to the generated audio file on R2.
  4. Activate the Workflow: Once configured, activate the workflow.
  5. Trigger the Workflow: Submit the n8n form to initiate the PDF-to-podcast conversion process.

Related Templates

AI multi-agent executive team for entrepreneurs with Gemini, Perplexity and WhatsApp

This workflow is an AI-powered multi-agent system built for startup founders and small business owners who want to automate decision-making, accountability, research, and communication, all through WhatsApp. The “virtual executive team,” is designed to help small teams to work smarter. This workflow sends you market analysis, market and sales tips, It can also monitor what your competitors are doing using perplexity (Research agent) and help you stay a head, or make better decisions. And when you feeling stuck with your start-up accountability director is creative enough to break the barrier 🎯 Core Features 🧑‍💼 1. President (Super Agent) Acts as the main controller that coordinates all sub-agents. Routes messages, assigns tasks, and ensures workflow synchronization between the AI Directors. 📊 2. Sales & Marketing Director Uses SerpAPI to search for market opportunities, leads, and trends. Suggests marketing campaigns, keywords, or outreach ideas. Can analyze current engagement metrics to adjust content strategy. 🕵️‍♀️ 3. Business Research Director Powered by Perplexity AI for competitive and market analysis. Monitors competitor moves, social media engagement, and product changes. Provides concise insights to help the founder adapt and stay ahead. ⏰ 4. Accountability Director Keeps the founder and executive team on track. Sends motivational nudges, task reminders, and progress reports. Promotes consistency and discipline — key traits for early-stage success. 🗓️ 5. Executive Secretary Handles scheduling, email drafting, and reminders. Connects with Google Calendar, Gmail, and Sheets through OAuth. Automates follow-ups, meeting summaries, and notifications directly via WhatsApp. 💬 WhatsApp as the Main Interface Interact naturally with your AI team through WhatsApp Business API. All responses, updates, and summaries are delivered to your chat. Ideal for founders who want to manage operations on the go. ⚙️ How It Works Trigger: The workflow starts from a WhatsApp Trigger node (via Meta Developer Account). Routing: The President agent analyzes the incoming message and determines which Director should handle it. Processing: Marketing or sales queries go to the Sales & Marketing Director. Research questions are handled by the Business Research Director. Accountability tasks are assigned to the Accountability Director. Scheduling or communication requests are managed by the Secretary. Collaboration: Each sub-agent returns results to the President, who summarizes and sends the reply back via WhatsApp. Memory: Context is maintained between sessions, ensuring personalized and coherent communication. 🧩 Integrations Required Gemini API – for general intelligence and task reasoning Supabase- for RAG and postgres persistent memory Perplexity API – for business and competitor analysis SerpAPI – for market research and opportunity scouting Google OAuth – to connect Sheets, Calendar, and Gmail WhatsApp Business API – for message triggers and responses 🚀 Benefits Acts like a team of tireless employees available 24/7. Saves time by automating research, reminders, and communication. Enhances accountability and strategy consistency for founders. Keeps operations centralized in a simple WhatsApp interface. 🧰 Setup Steps Create API credentials for: WhatsApp (via Meta Developer Account) Gemini, Perplexity, and SerpAPI Google OAuth (Sheets, Calendar, Gmail) Create a supabase account at supabase Add the credentials in the corresponding n8n nodes. Customize the system prompts for each Director based on your startup’s needs. Activate and start interacting with your virtual executive team on WhatsApp. Use Case You are a small organisation or start-up that can not afford hiring; marketing department, research department and secretar office, then this workflow is for you 💡 Need Customization? Want to tailor it for your startup or integrate with CRM tools like Notion or HubSpot? You can easily extend the workflow or contact the creator for personalized support. Consider adjusting the system prompt to suite your business

ShadrackBy Shadrack
331

🎓 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

Send WooCommerce discount coupons to customers via WhatsApp using Rapiwa API

Who is this for? This workflow is ideal for WooCommerce store owners who want to automatically send promotional WhatsApp messages to their customers when new coupons are created. It’s designed for marketers and eCommerce managers looking to boost engagement, streamline coupon sharing, and track campaign performance effortlessly through Google Sheets. Overview This workflow listens for WooCommerce coupon creation events (coupon.created) and uses customer billing data to send promotional WhatsApp messages via the Rapiwa API. The flow formats the coupon data, cleans phone numbers, verifies WhatsApp registration with Rapiwa, sends the promotional message when verified, and logs each attempt to Google Sheets (separate sheets for verified/sent and unverified/not sent). What this Workflow Does Listens for new coupon creation events in WooCommerce via the WooCommerce Trigger node Retrieves all customer data from the WooCommerce store Processes customers in batches to control throughput Cleans and formats customer phone numbers for WhatsApp Verifies if phone numbers are valid WhatsApp accounts using Rapiwa API Sends personalized WhatsApp messages with coupon details to verified numbers Logs all activities to Google Sheets for tracking and analysis Handles both verified and unverified numbers appropriately Key Features Automated coupon distribution: Triggers when new coupons are created in WooCommerce Customer data retrieval: Fetches all customer information from WooCommerce Phone number validation: Verifies WhatsApp numbers before sending messages Personalized messaging: Includes customer name and coupon details in messages Dual logging system: Tracks both successful and failed message attempts Rate limiting: Uses batching and wait nodes to prevent API overload Data formatting: Structures coupon information for consistent messaging Google Sheet Column Structure A Google Sheet formatted like this ➤ sample The workflow uses a Google Sheet with the following columns to track coupon distribution: | name | number | email | address1 | couponCode | couponTitle | couponType | couponAmount | createDate | expireDate | validity | status | | ----------- | ------------- | --------------------------------------------------- | --------- | ---------- | -------------- | ---------- | ------------ | ------------------- | ------------------- | ---------- | -------- | | Abdul Mannan | 8801322827799 | contact@spagreen.net | mirpur-DOHS | 62dhryst | eid offer 2025 | percent | 20.00 | 2025-09-11 06:08:02 | 2025-09-15 00:00:00 | unverified | not sent | | Abdul Mannan | 8801322827799 | contact@spagreen.net | mirpur-DOHS | 62dhryst | eid offer 2025 | percent | 20.00 | 2025-09-11 06:08:02 | 2025-09-15 00:00:00 | verified | sent | Requirements n8n instance with the following nodes: WooCommerce Trigger, Code, SplitInBatches, HTTP Request, IF, Google Sheets, Wait 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) 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. Message Content: The current message template references the first coupon only (coupons[0]). Adjust if you need to handle multiple coupons. 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
110