Obsidian and Markdown

How do I get meeting transcripts into Obsidian as Markdown?

Record and transcribe on your computer, and LokalBot can write a note for each meeting straight into your vault: the summary, the action items, the people and projects involved as links, and the transcript. You can also export one meeting at a time, add a daily note, or write the notes with your own script.

Why plain files work best

An Obsidian vault is a folder of Markdown files. Anything that writes a .md file into that folder can feed it, and the notes keep working without an account, a plugin, or a sync service in between. If the transcript is a file you own, nothing upstream can change how you get to it.

Option 1: a note for every meeting

In Settings → Meetings → Meeting note export, turn on Export a note for each meeting, pick a folder in your vault, and set the format to Obsidian. LokalBot writes one note per meeting, including meetings you recorded before turning it on, named like 2026-10-14 Atlas release sync (4f7c2a91).md.

Each note starts with properties: date, time, duration, meeting app, and the people and tracked projects involved as [[links]], so they show up in backlinks and the graph. Then come the summary, the action items as checkboxes with the ones you finished checked off, and the transcript, unless you turn off Include the transcript. Detected passwords and keys are redacted.

Notes stay current: marking an action done, renaming a speaker, or regenerating a summary updates the note. A note keeps its first name when you rename the meeting, so your links to it keep working. Once you edit, move, or delete a note, it is yours: LokalBot leaves it alone and does not write that meeting again.

Option 2: export one meeting

Open a meeting and choose Share → Export as Markdown…, then save it into your vault. The file starts with the title, date, duration, and meeting app, followed by the summary and the full transcript. Share → Copy as Markdown puts the same text on the clipboard. This is fine for the occasional meeting and tedious for every one.

Option 3: a daily note in Obsidian format

In Settings → Daily Review → Daily note export on a Mac, or Settings → Day Memory → Daily note export on Windows and Linux, turn on Export a daily memory note, pick a folder in your vault, and set the format to Obsidian. Each evening (6 PM by default) LokalBot writes or refreshes one note for the day, with date and tags properties: the day's digest, a list of its meetings, app time, and saved moments. A day missed while the computer was asleep is written later. If you edit a generated note, LokalBot keeps your edits and pauses the export until you move that note or choose another folder.

The daily note lists meetings by time, title, and ID. It doesn't include their transcripts, so pair it with option 1 if you want the full text in the vault.

Option 4: your own script

If you want a different layout, the bundled lokalbot-cli prints any meeting as Markdown, so a few lines of shell can write the notes instead. The CLI is read-only and checks the same switch agents do, so first turn it on: on a Mac, Allow external agents to read your LokalBot data in Settings → External Agents, with Meetings ticked; on Windows and Linux, Allow external agents to read your meeting library in Settings → Privacy & Data. Then install the CLI from Settings → External Agents → Agent CLI on a Mac or Settings → Advanced → Agent CLI on Windows and Linux, save this as lokalbot-to-obsidian.sh, change the folder, and run it with sh lokalbot-to-obsidian.sh:

# Folder inside your vault
vault="$HOME/Documents/Obsidian/Meetings"
mkdir -p "$vault"

lokalbot-cli list \
  | jq -r '.[] | select(.has_summary) | "\(.id) \(.date | fromdateiso8601 | strflocaltime("%Y-%m-%d"))"' \
  | while read -r id day; do
      note="$vault/$day $id.md"
      [ -e "$note" ] || lokalbot-cli get "$id" > "$note"
    done

It uses jq, which ships with macOS 15 and later. On Linux, install jq with your package manager. On Windows, run the script in Git Bash with jq installed. Each meeting is written once its summary is ready, as a note named like 2026-10-14 ab12cd.md. Existing notes are never overwritten, so edits you make in Obsidian are safe; delete a note to have it written again, for example after you regenerate a summary. Run the script after meetings, or from a scheduled job if you want it hands-off.

Option 5: use the LokalBot Obsidian plugin

If you want to browse recent meetings, search transcripts, pull open action items into Daily Notes, or ask LokalBot's local model without leaving Obsidian, install the open-source LokalBot plugin for Obsidian (macOS, Windows, and Linux). It reads your local library strictly through the read-only lokalbot-cli with zero network requests.

Migrating existing exports from Granola, Otter.ai, Fireflies, Fathom, or Zoom into Obsidian Markdown first? Use our 100% offline browser converter at lokalbot.com/migrate—nothing leaves your computer.

Things to know

FAQ

Questions about this guide

Is there an Obsidian plugin for LokalBot?

Yes—an open-source LokalBot plugin for Obsidian (github.com/stevyhacker/obsidian-lokalbot) lets you search meetings, sync notes, insert open action items into Daily Notes, and ask LokalBot's local model inside Obsidian. You still don't need a plugin if you only want automatic Markdown note export straight into your vault folder.

Do the exported transcripts include speaker names?

Yes. Each transcript line starts with a timestamp and the speaker's name, or a default label such as Me when you haven't named that speaker.

Can I use Logseq instead?

Yes, with Logseq OG, which keeps a graph as Markdown files. Meeting notes and the daily note both come in a Logseq format, with page properties and TODO and DONE actions; choose your graph's pages folder for meeting notes. Logseq's newer database version imports Markdown instead of reading a folder, so it won't pick up new notes on its own.

Try it locally

Meeting notes that stay on your computer by default.

Free, open source, and no account. For Mac, with Windows and Linux in alpha.

Download for macOS

Apple Silicon · macOS 15+ · or with Homebrew: brew install --cask stevyhacker/tap/lokalbot

macOS · Windows · Linux (alpha) · requirements