Keep recording notes in your Obsidian vault
Copy a completed Eavesy brief into an Obsidian note, or place the recording files in a vault. Markdown files are compatible; this is a file workflow, not a native sync plugin.
How it works with Obsidian
- 1
Start with a copy: open a completed recording folder and inspect summary.md and transcript.md.
- 2
Copy the brief into a new Obsidian note, or copy the source folder into the vault.
- 3
Keep JSON metadata and audio as separate files; add your own YAML frontmatter if needed.
- 4
Link the note to your project and confirm any attachment references still open.
Frequently asked
- What format are the notes in?
- Plain Markdown plus JSON metadata and the audio file — fully compatible with Obsidian and any other Markdown tool.
More notes & knowledge integrations
Start with a copy of one completed capture
Open a finished recording folder in Eavesy. Read summary.md and transcript.md before moving anything. Copy the brief into a new Obsidian note, or copy the recording folder into your vault if you want to keep its source files nearby.
This is Markdown and file compatibility, not a native Obsidian synchronization plugin. Eavesy does not automatically create backlinks, tags, or YAML properties for you. Recording metadata is stored separately as JSON.
Keep the source readable
Give the note a useful project title and link it to the surrounding work. If you retain transcript and media files, check their relative references after copying. A local path from another Mac will not open automatically on this one.
The Mac recording folder can also be changed in Settings. If you point it at a vault, new captures go there; do not assume existing capture folders are relocated. Test with one capture and keep a backup before reorganizing a library.
Review before editing a synced file
Signed-in recording files can participate in Eavesy's synchronization workflow. Copying the brief to a separate Obsidian note is the simplest way to maintain your own project note without treating that copy as an automatically synced Eavesy artifact. Check the file reference before editing the original.
A portable decision note
Use the decision log template to separate an agreed choice, its source, and missing details. The worked meeting example includes a fictional transcript and hand-authored brief you can open directly in your vault. It does not require an account or a plugin.
A small vault structure you can maintain
Project/
Launch decision.md
Sources/
Launch planning/
summary.md
transcript.md
audio.m4aThis is a suggested organization, not an automatic Eavesy export layout. Keep your edited decision note separate from the source copy. Add a link to the source transcript and verify it opens from the note’s new location. If you also keep audio, preserve enough context to identify the recording and the relevant passage.
Before moving a large library, copy one completed capture and open its note, transcript, and media from the vault. Confirm which files your chosen sync service includes. A working Markdown link on this Mac does not establish that an absolute path works on a second device.
Capture it once. Use the context anywhere.
Capture on your Mac and keep normal files. Sign in for cloud transcripts and briefs, then share the context your AI needs.