How to Get Meeting Notes Into Obsidian on Mac

To get meeting notes into Obsidian, copy the notes as Markdown, paste them into a new note in your vault, then export the transcript as a Markdown file and drag it into Obsidian. Rebrief for Mac records the call and writes the transcript and notes on your Mac after it ends. The move into Obsidian is manual: Rebrief has no Obsidian plugin and does not sync with your vault, so you decide what goes in.

That manual step is useful. It gives you a moment to check the notes and link the meeting to the project it changed, instead of filling the vault with unreviewed summaries.

Can meeting notes go into Obsidian automatically?

Not with Rebrief. It gives you two Markdown outputs, and you add both to your vault yourself:

• The meeting notes, copied as Markdown: what happened, decisions, key points, action points and open questions.
• The transcript, exported as a Markdown file. It can also be exported as plain text, SRT or WebVTT, as described in Rebrief's export guidance.

Because nothing syncs, edits you make in Obsidian stay in Obsidian. Pasting a fresh copy from Rebrief over your note later would replace the corrections you made, so keep your reviewed version.

How to move meeting notes into Obsidian, step by step

1. Copy the meeting notes as Markdown from Rebrief. Create a note in your Obsidian vault and paste them in.
2. Give the note a title with the meeting date, project and subject, such as "2026-10-14 Atlas scope review". Make the corrections you found during review.
3. Export the transcript from Rebrief as Markdown and add the file to the vault as a separate note. You can drag it into Obsidian's file explorer or move it into the vault folder in Finder, as described in Obsidian's Markdown import instructions.
4. Link the meeting note to the transcript so you can find the source without searching the whole vault. In Obsidian, type [[ and pick the note from the suggestions, as shown in the internal links guide.
5. Link the meeting note from the project note it affects, and add a link back to the project in the meeting note.

Check your vault's sync settings before adding sensitive meetings. Obsidian vaults are local files, but Obsidian lists several ways to sync them, including Obsidian Sync, iCloud and other services, and a synced vault will copy the meeting there too.

An Obsidian meeting note template

Paste the Rebrief notes into a structure like this, then trim it to what the project needs. This is a suggested layout, not something Rebrief creates for you.

• Date and meeting: 2026-10-14, Atlas scope review
• Project: [[Atlas]]
• Transcript: [[2026-10-14 Atlas scope review transcript]]
• What changed: one or two sentences, checked against the transcript
• Decisions: each with its condition, if it had one
• Action items: task, owner, agreed date
• Open questions: what still needs an answer, and from whom

Review the notes before they go into your vault

Read Rebrief's notes beside your project plan. Start with the decisions and action points that affect your next step, and check the transcript for the exact agreement when a deadline, owner or condition would change the plan.

Keep open questions visible. A request to investigate something is not approval to build it, and a suggested date is not an agreed deadline. If the transcript leaves the meaning unclear, listen to that part of the recording before you change the project note.

You don't need to turn every discussion point into a task. Keep the reasoning behind a decision when it will help you later, and leave general discussion in the meeting note so the project plan stays readable.

Update the project note the meeting changed

Open the main project note and update the part that changed. Put an agreed scope change beside the current scope, or an accepted follow-up in the task list you already use, with a link to the meeting note and a short reason.

Keep agreement and progress apart. The meeting shows that someone accepted a task; it doesn't show they finished it. Mark it done in your task list when you have confirmation, and leave the meeting note as the record of the agreement.

Recording the meeting on Mac

Ask for permission before you record and follow your organization's rules. Tell people you're recording, as recording laws differ by place. Rebrief records your microphone and the call audio with no bot in the call, then transcribes on your Mac after the call ends. It needs Apple Silicon and macOS 15 or later; the support page covers setup. Free recordings stop at 15 minutes, and a one-time purchase removes that limit.

Finding the reason behind a change later

When you wonder why the plan changed, follow the link from the project note to the meeting and its transcript. If you can't remember which call it was, use Ask to search your past meeting transcripts with a question like "Why did we postpone the reporting work?" Check the passage it shows, then add the explanation to the project note with the meeting reference.

If you'd rather have an assistant read the meetings than copy them by hand, Rebrief can also serve your meeting transcripts to Claude through a local MCP server.

Try it with one short call tied to an active project: check the notes, move them into your vault, and update the work they affect.