Voice Memos to Obsidian: Four Prompts

Voice memos are easy to record and hard to retrieve. This workflow turns a batch of Talkie memos into linked Obsidian Markdown files. It uses four prompts to find topics across the batch, create topic files, create daily notes, and build an index.

Talkie stores the source transcripts on your Mac. A hosted model receives any transcript text that you paste into it. Use a local model if the transcript text must stay on your Mac.

Use the Voice memo to Obsidian workflow to process one memo automatically. Use the batch method below when you want to find themes across several memos.

Download the four-prompt Markdown template.

The problem

I record voice memos on walks. Five minutes, sometimes ten. Inside any one of them I'll touch three projects, a marketing idea, and a decision I've been chewing on for a week.

Then the file sits there. Titled by date. Buried under the next memo, and the one after that.

A week later I remember I said something useful about a project direction. I can't remember which recording. I scrub through four of them and give up.

The memos aren't the problem. The lack of any index across them is.

What's actually in there

I took ten consecutive memos from two weeks of recordings and read them as one document instead of ten.

Seven distinct threads showed up. Not seven memos — seven topics that wove through multiple recordings across multiple days:

• A project idea mentioned Monday, refined Wednesday, given a deadline Friday
• A pricing thought that started as a throwaway line and turned into a decision by the second week
• A health goal that kept surfacing as a footnote to work planning

None of those lived in a single memo. They were spread across recordings, devices, and weeks. Each memo on its own looked like rambling. All ten read together had a clear shape.

The shape hiding in stream of consciousness

Voice memos feel chaotic but they aren't. When I talk through my day I'm doing four things in roughly the same order:

1. Set context — "Okay, today is Tuesday and I want to talk about..."
2. Explore — branching, comparing, weighing
3. Decide — "I think the move is to..."
4. Assign next steps — "So the game plan is..."

That's an outline in a hoodie.

The workflow

The whole thing takes about ten minutes for a week of memos. Four prompts, one LLM, one folder of markdown files at the end.

Step 1: Pull your recent memos

You get a list with titles, durations, word counts. Grab the past week or two.

Step 2: Read them as a batch, not one by one

This is the part most people skip. Don't read each memo in isolation. Read all of them together and look for threads — ideas that appear more than once or that connect to each other.

In my ten memos:

Step 3: Generate topic files

Each thread becomes its own file. Not a summary — a working document with the core idea, how it evolved, open questions, and links to the other topics it touches.

Here's what one looks like:

Step 4: Generate daily notes as anchors

Each day's memos become a daily note that links into the topic files. This preserves the timeline so I can trace how an idea went from a throwaway line to a concrete plan.

Step 5: Open it in Obsidian

The [[wikilinks]] light up. Graph view shows which ideas cluster, which ones are orphans, and which days produced the most connections.

Two weeks of memos end up looking like this:

Not seven recordings. Seven ideas, tracked across time, linked to each other.

topics/
  API Redesign.md
  Mobile App.md
  Product Launch.md
  Marketing Strategy.md
  Pricing Model.md
  Onboarding Flow.md
  Health & Sustainability.md

daily/
  2026-03-15.md  →  links to 3 topics
  2026-03-14.md  →  links to 4 topics
  2026-03-10.md  →  links to 3 topics
  2026-03-09.md  →  links to 3 topics

The prompts

These are the four prompts I use. Paste the required transcripts or topic lists after each prompt. You can use a local model or a hosted model.

Prompt 1: Extract topics

The big one. Feed it all your transcripts at once.

Prompt 2: Generate topic files

Once you have a topic list, this writes the Obsidian-ready file for each one.

Prompt 3: Generate daily notes

Anchors the topics to specific days.

Prompt 4: Generate the index

A master file that ties the topics together.

Tips

• Batch. Five to ten memos at once. Single-memo summaries miss the threads that cross recordings, which is the whole point.
• Don't clean the transcripts. Leave the "um"s and "uh"s. The LLM handles them, and they tend to cluster around the parts where I'm actually thinking.
• Run it weekly. Sunday evening, pull the week, run the prompts, update the vault. It works as a ritual better than as a one-off.
• Let topics merge. After a few weeks you'll spot topics that should fold into each other. That's a signal — the thinking is converging.

Why this works

Most knowledge systems fail because they ask you to be organized at the moment of capture. Pick a folder, write a title, add tags. That's friction, and friction kills capture.

Voice memos invert it. Capture is messy and fast. Organization happens later, in batch, by a model that's good at exactly that.

What's next

The Voice memo to Obsidian workflow automates the single-memo path. The batch method remains useful when a topic appears across several recordings.

You can also download all four prompts as Markdown and keep the file in your vault.