MurmrMurmr

Guide

Templates & destinations

How Murmr turns voice into workflow-ready output — and how to route that output to Obsidian or the Share Sheet.

Murmr has two ideas that work together:

  • Templates format your transcript using a prompt you can edit.
  • Destinations decide what happens next (open Obsidian, or present the Share Sheet).

The prompt is yours. If you don't like the result, tweak the template until it feels right.

1) Flow

From voice to destination

A high-level view of what happens after you record.

Data flow from voice to destination

Transcription turns audio into text on-device.

Templates turn that text into a structured format (usually Markdown).

Destinations route the formatted output.

Choose Share Sheet for maximum flexibility, or Obsidian for direct “send to vault” behavior.

2) Templates

How templates work (and why the prompt is yours)

A template is a name, a prompt, optional variables, and optional context.

Template prompt basics

The template prompt tells Murmr how to format your transcript. You can make it strict (“output only Markdown”) or flexible (“keep it short, but include action items”).

If you don't like the output, don't fight it — edit the prompt. Add constraints, change tone, or change the structure until it matches your workflow.

Variables you can use

You can reference variables in your prompt using {{variableName}}.

Common variables:
- {{cleanTranscript}} (the text Murmr will format)
- {{rawTranscript}} (optional: the original raw transcript)
- {{date}} (entry timestamp)
- {{title}} (if you titled the entry)

Optional context (if enabled for the template):
- {{currentDateTime}}
- {{currentLocation}}
- {{currentWeather}}
- {{currentCoordinates}}

Tip: If your prompt doesn't include any placeholders, Murmr can attach a simple Context block automatically (date/location/weather), so you can keep prompts clean.

Best practice

End prompts with: “Output only the formatted text. No preamble.”

Best practice

If you want consistent headings, specify the exact structure (headings + bullets).

Best practice

Keep templates small and specific. One workflow per template beats “do everything” prompts.

3) Obsidian

Obsidian destination setup (best practices)

Send formatted output directly into your Obsidian vault using the Obsidian URL scheme.

Step-by-step

  1. Open Murmr → Templates.
  2. Create a new template (or duplicate a bundled one).
  3. Set Destination to Obsidian.
  4. Enter your Vault name (must match your Obsidian vault name).
  5. Pick a note target + file strategy (recommended recipes below).
  6. Try it from History: long-press an entry → “Share via template…” → pick your template.

Screenshot placeholders

Recipe: One rolling Inbox note

Best for quick capture into a single file you review later.

  • Note target: File Path
  • File strategy: Fixed Path
  • Path: Inbox/Voice Notes.md
  • Write mode: Append
  • Open after send: Off (optional)

Recipe: New note per capture

Best when you want each capture as its own timestamped note.

  • Note target: File Path
  • File strategy: Timestamped
  • Folder: Murmr
  • Prefix: Murmr (optional)
  • Write mode: New
  • Open after send: On (optional)

Recipe: Daily note

Best when your workflow lives in a single daily page.

  • Note target: Daily Note
  • Write mode: Append
  • Obsidian tip: ensure your Daily Notes feature is enabled and working on mobile
  • Template tip: keep the prompt focused on content; Append/Prepend can add the timestamp header for you

Obsidian best practices

  • Use a vault name that matches your Obsidian vault exactly.
  • Prefer relative file paths like Inbox/Voice Notes.md (not absolute file system paths).
  • Create the folder in Obsidian first (for example Murmr) so links don't surprise you.
  • If you choose Append or Prepend, Murmr may add a ## HH:mm timestamp header automatically. Keep your template prompt simple to avoid duplicate headings.
  • Deep links are URL-based and can hit size limits for very long text. For long captures, use the Share Sheet or copy/paste.

4) Share Sheet

Share Sheet destination setup (best practices)

The Share Sheet is the most flexible destination: Murmr formats the text, then iOS lets you choose where it goes.

Step-by-step

  1. Open Murmr → History.
  2. Long-press an entry → “Share via template…”
  3. Choose a template whose destination is Share Sheet.
  4. Pick the app you want (Obsidian, Notes, Mail, Slack, Things, etc).

Share Sheet is ideal when you don't want to commit to a single destination — or when you want to route differently depending on context.

Screenshot placeholders

Share Sheet best practices

  • Pin your favorite destinations to the top of the Share Sheet for faster sharing.
  • Use Share Sheet as a “universal adapter”: any app that accepts shared text is compatible.
  • If you want automation, build a Shortcut that receives text and saves it where you want — then share to Shortcuts.

5) Prompt examples

Copy‑paste prompts you can customize

These are starting points. Tweak them until they match your voice and workflow.

Action items (tasks-first)

You are an action-item extractor.
Turn the transcript into a short task list:
- First line: one-sentence summary
- Then 3–10 bullet points, each starting with a verb
- If dates/times are mentioned, include them in parentheses

Transcript:
{{cleanTranscript}}

Output only Markdown. No preamble.

Meeting notes (structured)

You are a meeting-note formatter.
Format the transcript into exactly this structure:

# Meeting Notes
Date: {{currentDateTime}}

## Summary
1–2 sentences.

## Decisions
- Bullets (or "None")

## Action Items
- [ ] Bullets with owners if mentioned (or "None")

## Open Questions
- Bullets (or "None")

Transcript:
{{cleanTranscript}}

Output only Markdown. No preamble.

Dev log (today → next)

You are a developer log formatter.
Create a concise devlog entry:

## ✅ Done
- Bullets

## 🧠 Notes
- Bullets (decisions, gotchas, context)

## 🎯 Next
- Bullets

Transcript:
{{cleanTranscript}}

Output only Markdown. No preamble.

Obsidian inbox (time-stamped)

You are a structured note formatter for Obsidian.
Format the transcript as an Obsidian inbox entry:
- Write a short paragraph
- Then optional bullets (max 6)
- End with tags: #voice #inbox

If your destination write mode is Append/Prepend, do not add your own HH:mm heading.

Transcript:
{{cleanTranscript}}

Output only Markdown. No preamble.

6) Troubleshooting

If something doesn’t work

Fast fixes for the most common issues.

Obsidian didn’t open

  • Confirm Obsidian is installed on this device.
  • Double-check the vault name (spelling/case).
  • Try switching the destination to Share Sheet as a fallback.

Output format feels wrong

  • Edit the template prompt. Make the structure explicit (exact headings, exact bullet rules).
  • Add “Output only the formatted text. No preamble.” to reduce unwanted chatter.
  • If you want consistency, reduce the prompt scope: one workflow per template.

AI transform unavailable

Structured templates require on-device AI availability. If structured transforms fail, try again later, use Light Cleanup, or share the raw transcript via Share Sheet.