Obsidian meeting notes: the template and the capture gap
Dylan de Heer
Obsidian is very good at what happens around a meeting and very little during one. It will link every note to the person who was in the room, surface the last four conversations you had with them, and let you query every open action item across your whole vault in one line. It will not turn the meeting into text. The core Audio recorder plugin will capture a microphone into a note, and that is where Obsidian stops. Everything from audio to usable notes is still on you, and it is the part every template guide skips past.
This covers the template that actually works, the person-note pattern that makes Obsidian worth the setup, how to make action items findable, and the honest state of getting a recording into a vault.
Why people use Obsidian for this at all
Worth being clear about the trade, because it explains every decision below.
An Obsidian vault is a folder of plain markdown files on your disk. There is no database and no account required to open them. That means your meeting notes will still be readable in ten years by any text editor, and it means nothing about them is legible to a vendor. People who take notes about clients, patients, candidates, or salaries tend to arrive at Obsidian for the second reason and stay for the first.
The cost is that Obsidian ships almost nothing. There is a calendar only if you add one, and no transcription or summary at all. You assemble it.
The template
Most working setups converge on roughly this. Frontmatter for the things you will filter on later, headings for the things you write during the meeting.
Four things about that template are doing real work.
Decisions are separated from notes. This is the single highest-value habit in the whole system. Six months later nobody rereads the notes, and everybody needs the decision. Keeping them apart means you can pull every decision on a project with one search.
Attendees are wikilinks, not text. [[Sarah Chen]] rather than Sarah Chen. This is what builds the person notes below, and it costs nothing at the time.
Actions are checkboxes. - [ ] carries a completion state a query can filter on. A plain bullet does not, so you can list it but never ask which ones are still open.
Context is written before the meeting, not after. One line. It is the only part of the template that takes discipline and the only part that reliably tells you, three weeks later, whether the meeting should have happened.
Use the core Templates plugin to insert it, or Templater if you want the date and title filled automatically. Both are fine. Templater is more capable and more fiddly.
One note per person
This is the pattern that makes Obsidian better than a notes app for meetings, and most people find it a year later than they should.
Create a People/ folder with an almost empty note for each person you meet regularly. It does not need content. Because your meeting notes link to [[Sarah Chen]], her note's backlinks pane becomes a complete chronological history of every conversation you have had with her, assembled with no effort from you.
Before a one to one, open the person note and read the last two entries. That is the whole workflow. It takes 40 seconds and it is the difference between "how have you been" and "you were blocked on the vendor contract last time, did that clear".
The same pattern works for projects and for clients. A Projects/ folder where each note is mostly backlinks gives you a project history nobody had to maintain.
Keep the folder structure flat. Meetings/ and People/, not Meetings/2026/Q3/Client/. Obsidian's search and backlinks make deep folders redundant and deep folders make filing a decision you have to take every time.
Making action items findable
The reason to write actions as - [ ] is that you can then collect them. With the Dataview plugin, still the standard for this even though its releases have slowed, a single note called Open actions holding this query inside a dataview code block lists every unchecked box across every meeting note:
The Tasks plugin does the same job with more syntax for due dates and recurrence, and Obsidian's own Bases core plugin now covers some of this ground too. Either way, the point is that you stop trusting yourself to remember which note the commitment is in.
If you want one habit from this whole piece: put the owner's wikilink inside the checkbox. - [ ] Send the revised scope [[Marc Doyle]] means the action shows up on Marc's person note too, so the next time you meet him it is in front of you.
Getting the meeting into the note
Here is the part the template guides skip.
Everything above assumes the words are already in the file. Typing while you run a client conversation is workable for a status call and a poor trade for anything where you also have to listen properly. So people reach for a recorder, and this is where the vault's whole premise starts to wobble.
The Obsidian community plugin registry had 6,793 plugins in it when this was counted, on 20 August 2026. Searching it for the meeting tools people actually use returns a clear picture: five separate plugins exist purely for getting Granola notes into a vault, two for Plaud, one each for Jamie and Meetily, plus a sixth that catches Granola, Fathom and Fireflies notes from a browser extension. The plumbing problem is solved several times over.
What almost all of that plumbing has in common is the direction it runs. The recording goes to a vendor's servers, the transcript and summary are produced there, and the plugin copies the finished text back down into your vault. The vault ends up as a faithful local mirror of notes that were made somewhere else, about a conversation that was uploaded.
For a sprint planning session that is a non-issue. For a therapy session, a legal consultation, a performance review, or a candidate debrief, it quietly undoes the reason the vault was a folder of plain files in the first place.
A handful do not work that way. Meetily's sync plugin describes itself as fully on-device with no cloud, and it is accurate: Meetily is genuinely local and open source. Several others drive a local Whisper model on your own machine rather than a vendor's. They are real options, and every one of them asks for more setup than most people want.
Where Weeve fits, and where it does not
Weeve records the Mac's own audio and produces the transcript and the summary on the device, using Parakeet for transcription and a local model for the summary. Nothing is uploaded, so there is no vendor copy of the conversation to worry about, and no bot appears in the call as a participant. For the confidential end of the meeting spectrum, that is the shape of tool an Obsidian user is usually looking for.
The honest part: there is no Weeve plugin in the Obsidian registry. The registry was checked live on 20 August 2026 and there are none. Granola has five. Getting a Weeve summary into a vault today means exporting it and saving the markdown into your Meetings/ folder, then adding the frontmatter and the wikilinks yourself. That is a manual step, and if a one-click sync is what you want, the tools listed above have it and Weeve does not.
The other limits worth knowing before you download anything: Weeve is Mac only and needs Apple Silicon on macOS 14 or later, so there is no Windows or mobile route. The free Starter plan covers 10 recordings a month, which is not enough for every call in a busy week. Accuracy drops on strong accents, crosstalk, and noisy rooms, the same as every system.
And it will not write your decisions section. That judgement, the sorting of what was said into what was decided, is the part of this workflow that is genuinely yours.
FAQ
Can Obsidian record meetings? It can record audio and nothing else. The core Audio recorder plugin captures a microphone into the active note as an embedded file, which is useful and is not a meeting note. There is no transcription and no summary. Turning that audio into text needs either a community plugin that connects to an external service, a plugin that drives a local speech model, or a separate application whose output you save into the vault.
What is the best Obsidian meeting note template? The one most working setups land on has frontmatter for date, attendees, and project, then headings for context, notes, decisions, actions, and follow up. The two details that matter more than the layout are keeping decisions in their own section and writing attendee names as wikilinks so person notes build themselves.
How do I link meeting notes to people in Obsidian? Write the attendee's name as a wikilink, [[Sarah Chen]], in the frontmatter or the body, and create a note at People/Sarah Chen. Her note's backlinks pane then lists every meeting she appeared in, in order, without you maintaining anything.
How do I track action items across all my meeting notes? Write them as markdown checkboxes, - [ ], then use the Dataview or Tasks plugin to query every unchecked box across the vault into a single note. Adding the owner as a wikilink inside the checkbox makes the action appear on their person note as well.
Is it safe to use an AI meeting notetaker with Obsidian? It depends where the audio is processed rather than where the note ends up. Most sync plugins copy finished notes down from a vendor's cloud, which means the recording was uploaded even though the file now sits locally. If the conversation is confidential, use a tool that transcribes on your own machine and put the output in the vault yourself.
Should I use Obsidian or a dedicated meeting notes app? Use both, for different halves. Dedicated apps are better at capture. Obsidian is better at everything that happens afterwards, because linking a conversation to a person, a project, and a decision is what it was built for and what the dedicated apps mostly do not do.
A vault only remembers what you managed to get into it.
If you want the capture to stay on your machine before it reaches the vault, Weeve's free Starter plan runs the transcription and the summary on your Mac. If you are not on a Mac, the browser transcriber turns a recording you already have into markdown you can paste straight in.
