Every meeting in talat can be exported as a Markdown file, a PDF, or copied straight to the clipboard. You can do it per-meeting on demand, or configure talat to write every finished meeting to a folder automatically.
Manual export
Click the download button on any meeting to open the export menu. Pick the document template you want the file laid out with, then choose one of three destinations:
- Copy. Puts the formatted Markdown on your clipboard.
- Save as Markdown. Writes a .md file to a location you pick.
- Save as PDF. Renders the same content to PDF.
Document templates
A template decides what an exported file contains and how it is laid out. There are no per-export tick boxes: a section appears in the file because its token appears in the template. Write {summary} and you get the summary, under whatever heading you put above it; leave it out and the summary is not exported.
talat ships three to start from — Default note (a title, the meeting details, then each section under its own heading), Frontmatter note (the same, opening with a YAML block that Obsidian and other PKM tools read), and Transcript only. Edit them, duplicate them, or add your own under Settings → Exports, where a live preview shows the result against a sample meeting as you type. The template selected there is the one the export menu opens on.
Wrap a section in {#if summary} … {/if} and it renders only when there is something to show — put the heading inside and a meeting with no action points exports no empty Action points heading. Nothing is ever dropped that you did not wrap, so what you write is what you get.
Dates render long-form by default; write {date:iso} for ISO 8601 instead.
Saving every meeting to a folder
A post-meeting action is something talat does when a recording ends. The Markdown file action writes every finished meeting to a folder of your choice, without you having to open each meeting. It runs once post-processing is complete, so the exported file always contains the final summary and title.
To set one up, open Settings → Exports → Post-meeting actions:
- Click Add action and pick Markdown file.
- Choose the destination folder. This can be any folder on your machine, including a subfolder of your Obsidian vault. See Obsidian for that setup.
- Pick the document template each file is rendered with. This is independent of the one the manual export menu uses, so a vault can take frontmatter while a one-off copy stays plain.
- Optionally tick Audio recording to copy the original audio file to the export folder next to each Markdown file. This requires audio recording to be enabled under Settings → Recordings.
- Optionally have talat rename exported files when a meeting’s title changes, so a file exported before its auto-generated title lands stays in step once the title settles.
You can add more than one. Two folder actions with different templates give you a summary in one place and a full transcript in another, from the same meeting. Each runs independently, and each can be switched off without losing its setup.
Filenames
The filename is a template you control in Settings → Exports, defaulting to the date, time, and title. You can rearrange it with tokens for the date, individual date parts, and the title, with a live preview and a reset to the default. It applies everywhere talat writes a file: manual saves, folder actions, and batch export alike, and a folder action can override it with a filename rule of its own. If audio is copied too, it gets the same base filename with the matching audio extension.
Filing meetings into subfolders
A folder action writes into the one folder you picked, which piles every meeting up as siblings once you have a few hundred. Give the action a subfolder rule and it files each meeting into a tree beneath that folder instead: a rule of {year}/{month} puts an August 2026 meeting in Meetings/2026/08/. The folders are created as they are needed, and copied audio lands in the same place as its note.
The rule takes the same date tokens as the filename — {date}, {time}, {year}, {month}, {day}, {hour}, {minute} — mixed with any literal folder names you want, and / separates one level from the next. It does not take {title}: renaming a meeting renames its file where it sits, and a title in the folder rule would mean moving the file somewhere else instead. A rule talat can’t make sense of is refused as you type it, with the reason, rather than scattering files somewhere you have to go looking for them.
A new rule applies to meetings from that point on. Files already exported stay where they are: Export all below will write every finished meeting into the new tree, but it copies rather than moves, so the flat originals are still there and are yours to delete once you are happy with the result.
Exporting your whole history at once
If you add a folder action after you’ve already recorded a stack of meetings, its Export all button writes every finished meeting to that folder in one go, using the same template, filename rule and subfolder rule, so your back catalogue matches what new meetings produce. Each meeting is filed under its own date, so a back catalogue spanning months lands across the months it happened in.
Pushing to an HTTP endpoint instead
If you want finished meetings delivered to a web service rather than a folder, use the webhook integration instead. It is another post-meeting action, firing on the same event, and supports either Markdown or a structured JSON payload.