talat writes every finished meeting (transcript, summary, notes, and optionally the audio) straight into your Obsidian vault. Every call, standup, and interview ends up as a Markdown note alongside the rest of your knowledge base, ready to link, query, and backlink like anything else in Obsidian.
Saving straight into your vault
An Obsidian vault is a folder of Markdown files, which means pointing a talat post-meeting action at that folder (or a subfolder such as Meetings) is all you need. Every finished meeting lands there as a Markdown file, named with the date and meeting title, already formatted for Obsidian.
Setup, once:
- Open talat’s Settings → Exports → Post-meeting actions.
- Click Add action and pick Markdown file.
- Click Choose folder and pick your Obsidian vault, or a folder inside it. A dedicated Meetings subfolder keeps the root of the vault tidy.
- Optionally give the action a subfolder rule, so meetings file themselves into a tree rather than piling up in one folder.
{year}/{month}puts an August 2026 meeting in Meetings/2026/08; the folders are created as they are needed. - Pick a document template. The template decides what each note contains and how it is laid out — Frontmatter note is the one to start from for a vault, since it opens with the YAML block Dataview reads. Edit it under Document templates to add or drop sections: a section appears in the note because its token (
{summary},{transcript:timestamps}) appears in the template. - Tick Copy audio alongside if you want the original recording saved into the vault too, next to each note.
Every meeting that finishes from this point onwards will drop into the folder you picked. Obsidian’s file tree picks the notes up automatically. No restart or refresh needed.
Working with the notes in Obsidian
Because talat writes plain Markdown, every Obsidian feature works on the exported notes:
- Backlinks. Wrap speaker names in
[[Alice]]to link each mention to a person note. - Dataview. Query meetings by date, speaker, or frontmatter.
- Daily notes. Embed the day’s meeting list from the Meetings folder with a simple Dataview or embed block.
- Graph view. Every meeting linked to participants, projects, and topics via
[[wikilinks]]shows up as an edge in the graph.
Participant names become real Obsidian links straight from the template: use {participants:wikilinks} in your frontmatter and each participant renders as [[Alice]], so every meeting shows up as an edge on the person’s note. Speaker names inside the transcript body stay plain text; wrap the ones you care about in [[double brackets]] by hand, or with a post-processor of your choice, to turn them into backlinks.
Alternative: webhook
If you run a plugin or local service that accepts HTTP requests (for example Advanced URI, Local REST API, or a self-hosted receiver), you can send finished meetings straight to that endpoint instead of (or as well as) writing to a folder. See the webhook integration for the payload format and setup. Most Obsidian users won’t need this. A folder action pointed at the vault is the path of least resistance.