Bring meeting notes into your Obsidian project work
Your project plan is in Obsidian, but the conversation that changed it is somewhere else. Rebrief for Mac records the call and creates a transcript and meeting notes afterward. Review those notes, copy them as Markdown into your vault, and link them to the project. The transfer is manual, so you decide what becomes part of your working knowledge.
Give each meeting a place in the project it affects. A useful note should let you see what changed, follow up on an agreed task, and return to the explanation when you need it. Rebrief supplies the conversation and initial notes; you connect the checked result to the work already in Obsidian.
Capture the conversation while you take part
Before the call, obtain the required recording permission and follow your organization's rules. Start Rebrief and confirm it is recording. You can keep your Obsidian project note open for questions you want to raise, without trying to type every answer as people speak.
Rebrief captures your microphone and the call audio, then transcribes the conversation on your Mac after recording ends. Once the transcript is ready, it creates notes covering decisions, action items, key points and open questions. That gives you a starting point for updating the project. See how Rebrief turns calls into notes.
For your first attempt, choose a short call: free recordings stop at 15 minutes. A one-time purchase removes that cap for longer meetings. Rebrief requires Apple Silicon and macOS 15 or later; the support page covers setup.
Review what the meeting changed
When processing finishes, read Rebrief's notes alongside your existing project plan. Start with the decisions and action items that affect what you'll do next. Check the transcript for the exact agreement, especially when a deadline, owner or condition would change the plan.
Keep unanswered 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 uncertain, listen to that part of the recording before changing your project note.
You don't need to turn every discussion point into a task. Preserve the explanation behind a decision when it will help you understand the choice later. Leave general discussion in the meeting note so the project plan stays readable.
Move the notes into your vault
Rebrief lets you copy meeting notes as Markdown and export the transcript as Markdown. These are separate operations, described in its export guidance. Use the notes for your reviewed recap and keep the transcript available as its source.
- Copy the meeting notes as Markdown from Rebrief. Create a note in your Obsidian vault and paste them into it.
- Give the note a title containing the meeting date, project and subject. Make the corrections you identified during review.
- Export the transcript from Rebrief as Markdown and add it to the vault as a separate note. You can drag the file into Obsidian's file explorer, as described in its Markdown import instructions.
- Link the reviewed meeting note to the transcript so you can find the source without searching through the whole vault.
The complete transfer has not been tested for this guide. [Evidence needed: an actual Rebrief Markdown transcript and copied notes opened and linked in Obsidian.]
Keep your reviewed note when you return to the meeting later. Rebrief and Obsidian don't automatically exchange these edits, so pasting a fresh copy over your note would replace the corrections you made. Also check your vault's sync settings before adding sensitive material: Obsidian can sync notes to other devices and services.
Connect the meeting to the work it affects
Open the main project note in Obsidian 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. Add a link to the reviewed meeting note beside the update, with a short explanation of why it changed.
Obsidian lets you link to an existing note by typing [[ and choosing it from the suggestions. Use that to connect the project update to the meeting, then add a project link in the meeting note too. The internal links guide explains the same method for linking the transcript.
Keep the distinction between agreement and progress. The meeting records that someone accepted a task; it doesn't establish that they finished it. Update completion in your normal task list when you have confirmation, while leaving the meeting note as a record of the agreement.
Return to the explanation when the question comes up again
When you wonder why the plan changed, follow the link from the project note to the reviewed meeting and its transcript. If you can't remember which call contained the discussion, use Rebrief's Ask with a question such as "Why did we postpone the reporting work?" Ask searches recorded meetings and shows supporting passages that open the source meeting at that moment.
Check the passage, then add the useful explanation to your Obsidian project note with its meeting reference. Try this with one short call connected to an active project: review the notes, move them into your vault, and update the work they affect.