Get AI summaries of any video or article — Sign up free
How I Quickly Capture Ideas using Obsidian MD and Fleeting Notes thumbnail

How I Quickly Capture Ideas using Obsidian MD and Fleeting Notes

John Mavrick Ch.·
5 min read

Based on John Mavrick Ch.'s video on YouTube. If you like this content, support the original creators by watching, liking and subscribing to their content.

TL;DR

Fleeting notes separate instant idea capture from later processing, reducing friction during real-time moments like walks and podcast listening.

Briefing

A fast capture workflow for Obsidian depends on “fleeting notes”: lightweight, temporary reminders that get processed later—so ideas can be captured instantly without slowing down during walks, podcast listening, or while browsing. The core claim is that direct note-taking inside Obsidian becomes too friction-heavy when the vault is large (the transcript cites 4,000+ notes and hundreds of megabytes), and copying into a separate tool like Google Keep creates extra manual steps. Fleeting notes solve that by letting ideas land quickly and then syncing them into a structured Obsidian vault when the user is ready.

The workflow centers on an app called Fleeting Notes, described as free and designed to integrate with Obsidian. It supports linking and automatic syncing with the vault, aiming to meet three criteria for quick capture: it works across devices, stays easy to use, and syncs smoothly into a “second brain.” Capture starts in multiple ways. On mobile or in a browser, users can share content to Fleeting Notes, which automatically creates a note and generates a link; if the capture comes from a video, it can also attach a timestamp. Users can then dictate text via keyboard voice-to-text, add a title, and later connect related ideas by sharing the same video again to create a new note that links back to the earlier one.

On desktop, Fleeting Notes also supports saving highlighted material. A Chrome extension can send selected text into a fleeting note while preserving a link to the source. If nothing is highlighted, the extension icon allows quick typing directly into a new fleeting note. Importantly, the notes can be interconnected inside Obsidian using standard link syntax (square brackets), letting later processing preserve the “thought process” rather than isolating each idea.

Once a batch of fleeting notes exists, the next step is syncing. In Obsidian, Fleeting Notes is installed as a community plugin and enabled, then configured with login details to activate syncing. Sync settings let users choose where notes land (a dedicated folder), whether syncing is automatic, and the directionality: one-way sync from Fleeting Notes to Obsidian, optional deletion of fleeting notes after syncing to keep the app clean, or two-way sync if Fleeting Notes is used as a knowledge base. A key feature is template customization for importing—using variables to populate fields like created date, tags, and source links. The transcript describes a template modeled after an Obsidian default note template, including statuses, tags, and a “seedling” tag to register imported items.

Processing is handled through Obsidian commands. One command inserts all unprocessed notes, which requires an ID tag to make them eligible; another inserts notes containing specific text, searching both front matter and content. After review, users can move notes into the correct Obsidian templates (e.g., turning an idea into an “input” note or a “thought” note), link them to relevant concepts, and then delete or relocate the original fleeting note depending on the chosen template strategy. The workflow functions as a filter: capture first, then decide later whether an idea is worth turning into a permanent note—typically at the end of the day and end of the week for brainstorming and writing.

Cornell Notes

Fleeting Notes is positioned as a low-friction capture layer for Obsidian: ideas get stored as temporary “fleeting notes” immediately, then synced and processed later. The workflow avoids the slowdown of typing directly into a large Obsidian vault and reduces manual transfer steps compared with tools like Google Keep. Fleeting Notes integrates via a Chrome extension and share actions that create notes with auto-generated links (and timestamps for videos). In Obsidian, a community plugin handles syncing, with options for folder destination, one-way vs two-way sync, optional deletion after sync, and customizable import templates using provided variables. Finally, Obsidian commands insert unprocessed notes or notes matching specific text, letting users convert selected items into permanent “input” or “thought” notes and link them to related ideas.

Why does the workflow treat “capture” and “processing” as separate steps instead of writing everything directly into Obsidian?

Directly typing into Obsidian is described as too slow once the vault is large (the transcript cites 4,000+ notes and hundreds of megabytes). The friction shows up during late-night walks, podcast listening, and browsing, where ideas appear unpredictably. Fleeting notes act as a fast landing zone: capture instantly in Fleeting Notes, then sync and decide later which ideas deserve permanent notes and where they belong in the vault.

How does Fleeting Notes capture sources quickly on mobile or in a browser?

Users can share an item to the Fleeting Notes app. The app creates a note automatically and generates a link. For video sources, it can also attach a timestamp. After that, the user can dictate the idea using keyboard voice-to-text and add a title, then later capture related content from the same video and link the new note back to the earlier one.

What desktop capture methods are used, and how do they preserve context?

On desktop, users can highlight text and save it into Fleeting Notes via a Chrome extension; the saved note includes a link to the source. If nothing is highlighted, clicking the extension icon opens a quick typing interface for recording the idea directly. Both approaches keep the origin attached so later processing can trace where the idea came from.

What sync controls matter most when moving fleeting notes into Obsidian?

In Obsidian, the Fleeting Notes community plugin is installed and enabled, then configured with login information. Sync settings include choosing the destination folder (default: “fleeting notes app”), enabling or disabling automatic sync, selecting sync type (one-way from Fleeting Notes to Obsidian or two-way), and optionally deleting notes from Fleeting Notes after syncing to keep the app clean. Template customization is also central: import templates use variables to populate fields like created date, tags (e.g., “seedling”), and clickable source links.

How do Obsidian commands help turn fleeting notes into permanent notes?

Commands insert notes for processing. One inserts all unprocessed notes, but only notes with an ID tag appear—so missing IDs prevent them from showing up. Another inserts notes containing specific text by searching front matter metadata and the note content. After insertion, users open the notes, move them into the appropriate Obsidian templates (like “input” or “thought”), add links to related ideas, and then delete or move the original fleeting note depending on the workflow.

How does the workflow act as a “filter” rather than a pure archive?

Capture is intentionally broad, but processing is selective. By reviewing fleeting notes in a second pass—often at the end of the day and end of the week—users decide which ideas are worth converting into permanent vault entries. Notes that don’t merit storage can be deleted or left unpromoted, preventing the vault from becoming a dumping ground.

Review Questions

  1. What specific friction does the workflow try to eliminate compared with typing directly into a large Obsidian vault or using Google Keep?
  2. Which sync options (direction, deletion, folder, templates) would you adjust if you wanted fleeting notes to remain temporary until you review them?
  3. How do the “unprocessed notes” and “specific text” commands differ in what they insert and what tags or search terms they rely on?

Key Points

  1. 1

    Fleeting notes separate instant idea capture from later processing, reducing friction during real-time moments like walks and podcast listening.

  2. 2

    Fleeting Notes integrates with Obsidian through linking and automatic syncing, aiming for cross-device accessibility and minimal capture effort.

  3. 3

    Share actions and the Chrome extension can auto-create notes with source links, and video captures can include timestamps.

  4. 4

    Obsidian sync settings allow one-way or two-way syncing, optional deletion after sync, and choosing the destination folder for imported notes.

  5. 5

    Custom import templates using Fleeting Notes variables help populate tags, created dates, statuses, and source links so imported notes fit existing vault structure.

  6. 6

    Obsidian commands insert either all unprocessed notes (requiring an ID tag) or notes matching specific text across front matter and content.

  7. 7

    A second-pass review turns the system into a filter—only selected ideas become permanent “input” or “thought” notes with links to related concepts.

Highlights

Fleeting Notes is positioned as a quick-capture layer that avoids the slowdown of typing into a large Obsidian vault and the manual transfer burden of tools like Google Keep.
Captures can preserve context automatically: share actions generate links (and video timestamps), while the Chrome extension saves highlighted text with its source.
Sync isn’t just a checkbox—direction (one-way vs two-way), deletion behavior, destination folder, and template variables determine how fleeting notes become structured Obsidian entries.
Processing relies on Obsidian commands that insert unprocessed notes (ID-tag dependent) or notes matching specific text, enabling targeted review and promotion.

Mentioned