Portable output

Publish files you can keep.

Use Share for deliberate one-off exports, or publish Markdown automatically into a plain folder or Obsidian vault with controlled naming and collision-safe ownership.

Audio, transcript, notes, ZIP Plain folder or Obsidian Collision safe

Export from Share

Open a meeting and choose Share beside its title. Each action appears only when that artifact exists.

Action Suggested filename Contents
Export Audio <safe title> - Audio.m4a Converted portable audio
Export Transcript <safe title> - Transcript.md Timestamped, speaker-mapped Markdown
Export Notes <safe title> - Notes.md The currently visible note version or editor draft
Export Zip of All <safe title>.zip Source audio, transcript, and current visible notes under a safe-title folder

The ZIP retains the source audio extension and does not include every historical note version. Copy, Export Notes, and Export Zip of All use the unsaved note editor draft when it is visible. A failed audio conversion or ZIP build preserves an existing destination.

Edit details before exporting

Use Edit Details to correct the title, customer, category, subcategory, or topics first. Future exports use the saved details where applicable; files already published outside Meeting Maid are not renamed or rewritten.

Turn on automatic publishing

  1. Open Settings > Export. Turn on Save notes to a folder after they're generated.
  2. Choose a destination. Select a plain writable folder or the top level of an Obsidian vault.
  3. Confirm Save as. Use automatic detection, force Plain folder, or force Obsidian vault.
  4. Optionally include transcripts. Select exact or AI-tidied output only after reviewing the privacy implications.

Notes remain inside Meeting Maid even when publishing is off. The export destination contains published copies, not the app's only copy.

Organize a plain folder

By default, a note is saved as Meeting title.md. Add categories and optional subcategory hints to create a predictable folder tree. For classification, the model receives the meeting title and a bounded transcript excerpt: at most the first 30 segments and 3,000 characters. 

MeetingNotes/
  Customers/
    AcmeCorp/
      Acme Q1 Review.md
  Internal/
    Engineering/
      Sprint Planning.md

If no category matches, the note stays at the export root. Classification uses the Quick model when selected, otherwise the Notes model.

Publish into Obsidian

A detected vault contains a .obsidian directory. Vault notes receive a dated filename, YAML frontmatter, and available calendar, attendee, customer, category, subcategory, and topic context.

  • Automatic placement chooses only from existing folders shown to the selected model.
  • Folders to Consider can exclude archives, imports, or hand-managed areas.
  • If placement cannot be determined, the note uses the vault's default location for new notes.
  • An explicit naming-convention folder pattern may create its named relative folders, confined to the selected vault.
  • Regenerating notes republishes the file Meeting Maid owns for that meeting.
Republishing replaces the note Meeting Maid wrote

If you edit that published vault note outside Meeting Maid, preserve those edits before regenerating. Meeting Maid does not replace unrelated files, but it does update its owned copy.

Open a saved vault note

The Saved to your notes row shows a vault-relative path with separate Open and Reveal in Finder actions. Direct Obsidian opening requires Obsidian 1.12.7 or later with Settings > General > Command line interface enabled.

  • Settings > Export shows Install Obsidian CLI only while publishing is on, the destination is a vault, and the CLI is unavailable.
  • If the CLI is unavailable, rejects the path, fails, or exceeds 15 seconds, Meeting Maid uses the default Markdown app.
  • Plain-folder notes always open in the default app.
  • Reveal in Finder remains available independently of the Obsidian CLI.

Choose transcript output

Also save the transcript is off by default because a verbatim transcript is more sensitive than a summary. When enabled, it is published only when notes are published and is replaced on the next export rather than accumulated.

Mode Behavior Provider request
Exactly as transcribed Speaker names, timestamps, and all transcript text No additional model request
Tidied up by the AI Asks the Notes model to remove filler and repair obvious mis-hearings without summarizing Sends the entire transcript as an additional request

Tidying falls back to exact text when it fails, returns nothing, takes longer than four minutes, changes speaker-and-timestamp turn identities, or, for same-language cleanup, returns less than half the verbatim length. A translation may be shorter when those turn identities still match. The meeting shows Cleaning Transcript while this additional request runs.

Define naming conventions

Open Naming Conventions in Settings > Export, or choose a convention under a prompt in Settings > Prompts. A convention can use:

  • <CustomerName>
  • <MeetingType>
  • <MeetingTitle>
  • <Date> with a separately selected date format
  • <DocumentType>

Apply PascalCase, camelCase, kebab-case, or snake_case transformations to variables. Assign one convention to several prompts or use distinct conventions per prompt. An empty folder pattern keeps automatic placement; a nonempty pattern explicitly allows those relative folders to be created.

Understand export ownership

  • Regeneration replaces only the path already owned by that meeting.
  • If an unrelated file already uses the desired name, Meeting Maid creates a numbered sibling such as Acme Review (2).md.
  • Changing destinations creates a new owned export and leaves the previous destination untouched.
  • Deleting a meeting sends managed internal files to Trash but does not delete published external copies.