Markdown note for the vault
The part you read in Obsidian: a clean transcript with timestamps and speaker labels.
Second-brain workflow
Your vault should keep the conversations, not just the conclusions.
Transcripted fits the way Obsidian users already work: one readable Markdown note per meeting for people, plus structured frontmatter and a capture-folder layout for the agents and automation you will want later.
The Obsidian angle
Obsidian is strongest when your notes stay portable, linkable, and under your control. Meeting tools usually break that by trapping the conversation in a cloud dashboard or making you export it after the fact.
Transcripted starts with local files, which means your vault can keep the readable meeting note while your broader system keeps the richer machine context right next to it.
What you actually get
YAML frontmatter for machines
The part that helps agents and scripts reason about timestamps, people, and meeting structure without scraping note text.
Capture-folder layout
A local map of the meeting history so your second brain can become a queryable corpus instead of a pile of isolated notes.
Persistent speaker identity
The same collaborator can stay linked across meetings, which makes linked people notes and cross-meeting questions more useful.
Why this is better than Markdown-only export
Readable Markdown is what makes the meeting feel native in Obsidian.
YAML frontmatter keeps the same meeting useful for agents later.
A local capture-folder layout is what turns your vault into something queryable across time.
All of it stays in local files you control instead of a vendor note service.
FAQ
How does Transcripted fit into an Obsidian workflow?
Transcripted gives Obsidian users readable Markdown meeting notes while also keeping YAML frontmatter and a capture-folder layout for richer machine workflows.
Do I need an Obsidian plugin?
No. Obsidian can read the Markdown transcript directly. The frontmatter metadata and capture folders stay alongside it for agents and automation.
Does Transcripted work with Dataview?
The Markdown transcript remains useful inside Obsidian, and the structured frontmatter makes deeper machine queries possible outside the note body.
Why is this better than a cloud sync plugin?
Because the meeting record starts as local files you control instead of a cloud note service that mediates access to your vault and your agent.
Make your vault the readable layer of a richer meeting corpus.
Keep the Markdown where you think, keep the structure where agents can use it, and keep both under your control.