Meeting notes into Obsidian, automatically

Last updated: August 31, 2026

If your notes live in Obsidian, Logseq, iA Writer or a folder of plain Markdown, Brieva can put every meeting summary there for you. Turn on Markdown export once, point it at your vault, and each summary arrives as a file the moment it is written. Everything happens on your Mac; no sync service, no plugin, no account.

Set it up

1. Open Brieva, then Settings, then Markdown Export.
2. Turn the switch on and choose the export folder: your Obsidian vault, or a folder inside it such as Meetings. Brieva creates it if it does not exist.
3. Click Save. From now on, every time a summary is generated or regenerated, its file is written.
4. Click Export All Summaries once to write the meetings you already have.

What the files look like

Each meeting gets a subfolder named after the meeting, so a recurring meeting collects its occurrences in one place. Every meeting produces two files named by date and title: the summary, and the full transcript alongside it:

Meetings/
  Q3 planning/
    2026-05-06 - Q3 planning.md
    2026-05-06 - Q3 planning - Transcript.md
    2026-05-20 - Q3 planning.md
    2026-05-20 - Q3 planning - Transcript.md
  1-1 with Sam Chen/
    2026-05-06 - 1-1 with Sam Chen.md
    2026-05-06 - 1-1 with Sam Chen - Transcript.md

Inside the summary file, a frontmatter block Obsidian reads as properties, then the summary:

---
title: "Q3 planning"
date: 2026-05-06
duration_minutes: 45
organizer: "sam.chen@northwindgrp.com"
attendees:
  - "sam.chen@northwindgrp.com"
  - "me@northwindgrp.com"
location: "Microsoft Teams"
recurring: true
tags:
  - meeting
---

## Summary
The analytics workstream moves to Q4 ...

## Key Topics
- Q3 roadmap reshuffle
- Partner-integration spike

## Key Discussion Points
- ...

## Action Items
- [ ] Sam to send the capacity numbers by Thursday
- [ ] Me to book the steering-committee slot

## Decisions
- ...

## Follow-ups
- ...

Action items are Markdown checkboxes, so Obsidian’s Tasks plugin and Dataview queries pick them up; the meeting tag and the date property let you build a meetings index or a daily-note query without any extra work.

What is exported, and what is not

• Exported: the summary for each meeting (quick summary, key topics, discussion points, action items, decisions and follow-ups, with the meeting details in the frontmatter) and the full transcript as a second file next to it, so a search across your vault finds what was actually said.
• Kept in sync: naming a voice or regenerating the summary in Brieva rewrites the files; the app remains the place to edit, the vault is the copy you read and link.
• Never exported anywhere else: the files are written to your folder by the app on your Mac. If your vault syncs (iCloud, Obsidian Sync, Git), that is your choice and your sync.

Ways people use it

• A Meetings folder in the vault, with a Dataview table of the last 30 days by date.
• Open action items across all meetings in one Tasks query: not done plus path includes Meetings.
• Linking a person’s note to every meeting they attended, by searching the attendees property.
• Pointing the export at a plain folder and reading it in any Markdown app; nothing here is Obsidian-specific.

How the summaries are produced without leaving your Mac is on the How Local AI works page. Ready to try it? Download Brieva and start the free trial.