My Meeting-to-Obsidian Pipeline: From Audio to Linked Notes in 30 Seconds

If you're anything like me, you've spent real time building your knowledge system. Web clips go into your vault. Journal entries are linked to projects. Book highlights get processed into atomic notes. You've got templates, tags, MOCs, the whole setup.

But there's a gap. A massive one.

Meetings. The 15-20 hours a week you spend talking to people about the most important things happening at work? Gone. Evaporated the moment the call ends. Maybe you jotted a few bullets. Maybe you didn't. Either way, your knowledge graph has a meeting-shaped hole in it.

I finally fixed this, and the pipeline is embarrassingly simple. Here's exactly how it works.

The meeting gap in your second brain

Think about where your best information lives. Not in Slack messages or email threads. In conversations. The pricing decision that happened in a 1:1. The architecture call where someone explained why you can't use that API. The client meeting where they casually mentioned their real budget.

This stuff is high-signal, low-noise. And in most PKM systems, it's completely absent.

Manual notes don't cut it. You're either participating or transcribing; you can't do both well. And the cloud transcription tools? They send your conversations to someone else's server, which is exactly the kind of thing Obsidian users chose to avoid by going local-first in the first place.

The pipeline: meeting to linked note in 30 seconds

Here's what actually happens when I join a call now:

Total time from "meeting ends" to "note is in my vault, searchable, linkable": about 30 seconds. Most of that is me clicking Export.

What the Obsidian export actually looks like

This isn't some proprietary format. It's plain Markdown with YAML frontmatter, exactly what Obsidian expects. Here's a real example:

---
title: Q1 Planning Review
date: 2026-03-10
duration: 47m
source: MeetingVault
tags:
  - meeting
  - planning
  - q1-review
---

## Transcript

**You:** Let's start with the roadmap. Where are
we on the mobile launch?

**Them:** We're on track for April, but I think we
should prioritize the API integration first.
The partner demo is March 28th and they're
expecting a working endpoint.

**You:** That's tight. Can we parallelize?

**Them:** If we pull in another engineer, yes.
I'll send you the staffing request after this.

**You:** Do it. Let's also revisit the pricing
tiers. The feedback from the beta group was
pretty clear that the mid-tier isn't compelling.

That's it. A first-class note in your vault. From here, I link it to [[Q1 Roadmap]], tag the people involved, and add it to my Projects MOC. The meeting is now part of my knowledge graph, not a fading memory.

Why this changes your PKM game

Once meetings are in your vault, things compound fast:

• Link meeting notes to project pages. Your [[Project Alpha]] page now has backlinks to every conversation where it was discussed. Context you'd never reconstruct from memory.
• Search across every meeting. "What did we decide about pricing?" Now that's a search query that actually returns results. Across months of meetings. In seconds.
• Build people pages. Create a note for each key person you work with. Link their meeting notes. Now you have a history of every conversation, useful before your next 1:1 or when onboarding someone new.
• Knowledge compounds. Your vault gets richer over time. The meeting from three months ago that's suddenly relevant? It's there, searchable, linked. Your meeting knowledge stops evaporating.

Local-first meetings for local-first notes

Here's what always bugged me about the cloud transcription tools: I chose Obsidian specifically because I want my notes on my machine, in files I control, with no vendor lock-in. Then I'm supposed to pipe my most sensitive data through someone else's cloud? Live conversations with clients, colleagues, partners?

MeetingVault matches the Obsidian philosophy. Everything happens on your Mac. The transcription engine (WhisperKit) runs on Apple Silicon. No internet required after initial setup. No accounts. No servers to breach. And the output is plain Markdown files that you own.

If you uninstall MeetingVault, your notes are still there. They're just .md files. No export needed, no data liberation request, no waiting for a support ticket. That's what local-first actually means.