Obsidian Meeting Transcription: Record Meetings into Notes

What you will get

A repeatable pipeline from spoken meeting to searchable Obsidian note: a capture setup that works for in-person and remote meetings, transcription configured inside your vault, and a transcript note template that keeps the summary, decisions, action items, and raw transcript in one place.

Inputs (copy/paste)

Have these ready before the first run:

• A microphone you trust. Built-in is fine for in-person meetings.
• Consent to record, wherever attendees or local law expect it.
• A transcription provider: a managed service, a Whisper-compatible API, or a local Whisper server.
• A vault folder for meeting notes, for example Meetings/2026/.

Step 1: Choose how you capture audio

Match the capture method to the meeting type:

• In-person meetings and solo voice notes: record directly in Obsidian. With SystemSculpt, the recorder toggles with Cmd/Ctrl + R and shows a waveform preview so you can confirm the microphone is actually live.
• Remote calls (Zoom, Meet, Teams): use the meeting app's own recording so every speaker is captured cleanly, then transcribe the exported audio file afterwards.
• Phone calls: record a voice memo on the phone and sync or AirDrop the file into your vault.

The rule of thumb: capture wherever the audio is cleanest, transcribe in Obsidian so the text lands next to your notes.

Step 2: Configure transcription once

Pick a provider and microphone in your plugin settings. SystemSculpt supports three setups:

• SystemSculpt transcription: chunked uploads, automatic retries, and live progress in the recorder. No extra keys to manage.
• Custom endpoint: point at OpenAI, Groq, or any Whisper-compatible API with a base URL, key, and model.
• Local Whisper server: keep audio on your own network, for example a LAN instance on localhost:9000.

Run a 30-second test clip end to end before a real meeting. Full setup details live in the audio transcription docs.

Step 3: Transcribe the recording

Two paths, same pipeline:

• Live recording: stop the recorder and let automatic transcription submit the audio. The transcript pastes into your active note when it finishes.
• Existing file: open any audio file already in your vault and run "Transcribe with SystemSculpt" to push it through the same pipeline without re-recording.

Long recordings are normalized and resampled automatically before upload, so an hour-long meeting does not need manual splitting.

Meeting transcript note template (copy/paste)

Paste this into a new note, or save it as a template file for the Templates core plugin:

---
tags:
  - meeting
  - transcript
date: {{date}}
attendees:
  -
project: "[[ ]]"
source: recording
---

# Meeting: {{title}} ({{date}})

## Summary

-

## Decisions

-

## Action items

- [ ] Task / owner / due date

## Open questions

-

## Transcript

> Machine transcription from {{date}}. Verify names, numbers, and dates against the audio before quoting.

(paste transcript here)

Keep the raw transcript at the bottom under its own heading. Summaries change as you edit; the transcript is the record you check against.

Step 4: Summarize and extract action items

A transcript by itself is an archive, not a meeting note. Run one AI pass to make it useful:

• "Summarize this transcript in five bullets. Then list decisions and action items separately. For each action item include owner and due date if stated; mark missing dates as TBD. Do not invent details."

For the full extraction loop with approval gates, follow Turn meeting notes into action items. If you want to refine the extraction prompt itself, build it with the Obsidian AI prompts builder.

Failure modes + fixes

• Failure mode: A remote call recorded through the laptop microphone only captures your side clearly. Fix: record inside the meeting app and transcribe the exported file instead of relying on an open mic.
• Failure mode: Transcription stalls at processing on long files. Fix: enable automatic audio resampling, or use a provider that chunks uploads automatically.
• Failure mode: Names, numbers, and dates come out wrong in the transcript. Fix: keep the raw transcript under its own heading and verify against it before quoting. Never let the AI summary become the only record.
• Failure mode: Transcripts pile up as orphan notes nobody revisits. Fix: link every meeting note from your daily note or project note, and keep action items as checkboxes so they show up in task queries.

Definition of done

A meeting transcription pass is complete when:

• The audio is transcribed and the raw text sits under the Transcript heading.
• The note has a short summary you could forward without editing.
• Action items have owners, and the note is linked from a daily note or project note.

Next step based on your intent

• To automate this with SystemSculpt, with the recorder, transcription, and AI summaries running inside Obsidian, get SystemSculpt Pro.
• If you want this implemented as a governed business workflow for your team, book an AgentOps workflow build.

Related template

For recurring meetings where you type notes instead of recording, start from the Obsidian meeting notes template.