← Back to directory
Personal Productivity Medium to set up AI workflow Repurpose/Transform

Obsidian Notes To Podcast Feed

Source reviewed Updated 2026-07-07

Converts Obsidian text notes into natural-sounding audio episodes and publishes them to a standard RSS feed for Apple and Spotify.

freelancers and consultantsdevelopers and engineers

What it does

Turn your Obsidian text notes into natural-sounding audio episodes that automatically publish to an RSS feed ready for Apple and Spotify. You simply write in Obsidian, and the agent handles generating the audio with OpenAI, storing files on Cloudinary, and delivering a compatible podcast feed.

Step by step

  1. Set up an Obsidian webhook to trigger a POST request with note content and metadata upon saving.
  2. Configure OpenAI TTS API calls with specific voice IDs and output formats like MP3 or WAV.
  3. Upload generated audio files to Cloudinary using their upload API with predefined folder structures.
  4. Generate the RSS XML structure by mapping Google Sheets columns to standard podcast feed tags.

Where the LLM does the work

  • Refine raw Obsidian notes into engaging, spoken-word scripts suitable for natural TTS delivery.
  • Generate compelling episode titles and descriptions that adhere to SEO best practices for podcasts.
  • Create show notes summaries that bridge the gap between dense markdown text and audio context.

Watch out for

Obsidian webhooks may fire multiple times for a single save event so implement idempotency checks or debounce logic in your serverless function.
OpenAI TTS can struggle with complex markdown syntax like bolding or italics so strip these formatting characters before sending the text to the audio model.
Cloudinary storage costs can escalate quickly if you do not set up lifecycle rules to delete temporary intermediate files after successful upload.
Apple Podcasts requires specific metadata standards for episode artwork and duration so validate your RSS feed against their guidelines before submission.

Tools that fit

Obsidian Service Source notes via webhook
OpenAI LLM Text to audio conversion
Cloudinary Service Audio storage and attachment
Google Sheets Service Podcast metadata management

The agent brief

Everything your agent needs, including the gotchas. Copy it and go.
agent-brief.md
You are helping me build the following AI agent workflow.

## Goal
Obsidian Notes To Podcast Feed: Converts Obsidian text notes into natural-sounding audio episodes and publishes them to a standard RSS feed for Apple and Spotify.

## Specification
- What it does: Turn your Obsidian text notes into natural-sounding audio episodes that automatically publish to an RSS feed ready for Apple and Spotify. You simply write in Obsidian, and the agent handles generating the audio with OpenAI, storing files on Cloudinary, and delivering a compatible podcast feed.
- Trigger: Triggered by an event (Manual · on webhook)
- Autonomy: Fully hands-off
- Expected setup effort: about an afternoon
- Tools/services involved:
  - Obsidian: Source notes via webhook
  - OpenAI: Text to audio conversion
  - Cloudinary: Audio storage and attachment
  - Google Sheets: Podcast metadata management

## Known pitfalls, handle each one explicitly in your implementation
1. Obsidian webhooks may fire multiple times for a single save event so implement idempotency checks or debounce logic in your serverless function.
2. OpenAI TTS can struggle with complex markdown syntax like bolding or italics so strip these formatting characters before sending the text to the audio model.
3. Cloudinary storage costs can escalate quickly if you do not set up lifecycle rules to delete temporary intermediate files after successful upload.
4. Apple Podcasts requires specific metadata standards for episode artwork and duration so validate your RSS feed against their guidelines before submission.

## Reference implementation
https://n8n.io/workflows/2699 (workflow template)
Fetch and inspect this before building. If it matches my stack, adapt it;
if not, rebuild the pattern with my tools.

## Process requirements
1. Before building: ask me which of the listed tools I actually use and
   what my platform is (n8n / Make / code / other). Do not assume.
2. Adapt the pattern to my answers; do not force the reference stack.
3. Address every pitfall above; tell me how you handled each.
4. Provide a test plan I can run before letting this touch real data.
5. Ask before any step that sends messages, modifies data, or spends money.

Source: https://usecasesforagents.com/use-case/obsidian-notes-to-podcast-feed/ via usecasesforagents.com

Frequently asked questions

Can I use a different Notes & Docs than Obsidian?

Yes. Obsidian is only the example notes & docs in this recipe. The same flow works with Figma, Google Docs, Google Slides and Microsoft SharePoint. Swap the notes & docs connection and keep the rest of the setup as written.

Want this running in your business?

This is what I do. I design and build AI agents like this one, and keep them running. If you want it set up for your team instead of doing it yourself, get in touch.
Get in touch →

Who it's for

Built for freelancers and consultants juggling this across every client, not just one.

Developers can adapt this to their own repo or ticket queue with the same trigger and tools.

Seen in the wild

← Back to directory