Platform edition
Obsidian for Windows
Save workflow results through the Save to Obsidian action target as new Markdown notes in your vault.
- Version
- 1.0.0
- Plugin ID
- com.
typewhisper. obsidian - Requirements
- TypeWhisper 1.1.0 or newer · Windows 10 or newer · An Obsidian vault in a folder on your PC
Inside this edition

Features in this edition
- Workflow action target Save to Obsidian
- A new Markdown note with YAML frontmatter for every run
- Custom note folder and filename template
- Existing notes are never overwritten
Overview
The Windows edition provides the Save to Obsidian workflow action target. A workflow can use it to save its final processed text as a new Markdown note inside your vault instead of inserting the text into the foreground application.
Dictation → workflow → Save to Obsidian → Markdown note in the vault
The add-on writes the note file directly into the vault folder. It does not open Obsidian, and Obsidian does not need to be running.
Source: Obsidian plugin for Windows
Setup
- In TypeWhisper for Windows, open Settings > Discover plugins and install Obsidian. The add-on then appears in the Settings sidebar, and its page opens.
- In Vault directory, enter the full path of your vault folder, for example
C:\Users\<name>\Documents\Notes. The folder must already exist. - Optionally change Note folder and Filename template.
- Leave Note mode at
new-noteand select Save settings. - Create or edit a workflow under Workflows and select Save to Obsidian under Action Target.
The add-on does not detect vaults and has no folder picker. TypeWhisper checks the vault path when you save the settings.
Settings in the Windows edition
The settings are labelled in English, also when TypeWhisper runs in another language.
| Setting | Effect |
|---|---|
| Vault directory | The absolute path of an existing local vault folder. It must be an ordinary folder, not a link. |
| Note folder | The destination folder inside the vault, relative to the vault. The default is TypeWhisper. Missing folders are created when a note is saved. Links and .. are not allowed. |
| Filename template | Sets the name of each note. Supports {{date}}, {{time}}, and {{app}}. |
| Note mode | Only new-note is supported. Every run creates a separate note. |
The default filename template is:
{{date}} {{time}} Transcription
This creates a filename such as 2026-08-21 11-42-08 Transcription.md. If that name already exists, the add-on appends a number instead of overwriting the existing file.
Note format
Every workflow run creates a separate Markdown file. The add-on places YAML frontmatter before the processed text:
---
date: 2026-08-21 11:42:08
source: TypeWhisper
app: "Microsoft Word"
language: en
---
Final processed workflow text
app and language appear only when TypeWhisper passes those values to the action target.
Example: structured meeting notes
Create a workflow that organizes a spoken meeting record into Summary, Decisions, and Action Items. Then select Save to Obsidian as its action target. The Windows edition saves the exact Markdown text produced by the workflow and adds the frontmatter automatically.
Current limitations
- Export is triggered through the workflow action target; there is no automatic export for every completed transcription.
- Daily notes are not available, and the
daily-notenote mode is not accepted. If an earlier version had daily notes turned on, the action fails until you set Note mode tonew-noteand save. - The add-on cannot append to existing notes.
- Note bodies do not have a freely configurable note template.
- YAML frontmatter is generated automatically and has no custom tag settings.
- Later edits in TypeWhisper History are not synchronized with files that have already been exported.