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.

## Auto-export to your vault

An Obsidian vault is a folder of Markdown files, which means pointing talat’s auto-export 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:

1. Open talat’s _Settings → Exports_.
2. Tick **Auto-export**.
3. Click **Choose folder** and pick your Obsidian vault, or a folder inside it. A dedicated _Meetings_ subfolder keeps the root of the vault tidy.
4. Tick the sections you want each note to contain (typically **Summary** and **Transcript**). Add **Timestamps** if you want per-utterance times in the transcript.
5. 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.

Speaker names in the transcript are written as plain text by default. 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](/content/docs/integrations/webhook/index.html) for the payload format and setup. Most Obsidian users won’t need this. Auto-export to a vault folder is the path of least resistance.