Moving Files with the Auto Note Mover Community Plugin

Auto Note Mover is positioned as a practical way to automate where Obsidian notes land—moving them between folders based on YAML frontmatter tags, title text, and an explicit rule order. The payoff is straightforward: treat an inbox-like folder as the starting point, then let rules push notes into “ideas,” “drafts,” “published,” and even deeper subfolders (like platform-specific locations) as soon as the right metadata appears.

Setup begins with installing the community plugin from Obsidian’s Community Plugins area and tuning two key behaviors. First, the trigger mode can be automatic or manual; manual mode is recommended for testing because it requires running the “move note” command from the command palette (Command P on macOS, Ctrl P on Windows). Second, the plugin can exclude folders—most notably the templates folder—so template notes don’t get caught by the same tag/title rules that should apply to real working notes.

The workflow then hinges on templates and metadata. A “writing ideas” template is created in the templates folder and includes YAML frontmatter tags such as status and other fields. In the demo vault, “writing ideas” acts as an inbox, while “ideas,” “drafts,” and “published” are destination folders. Rules are added in Auto Note Mover so that notes with tags like status/ideas, status/drafts, and status/published get moved accordingly. When manual mode is used, inserting the template alone doesn’t move the note; the user must run the Auto Note Mover command to trigger the move. Once triggered, notes leave the vault root and land in the correct folder, and subsequent tag changes can move them through the pipeline.

A major emphasis lands on rule precedence. When multiple rules match a note, the order of rules in the plugin’s rule list—not the order in which tags are typed—determines the final destination. A concrete example shows a note that should go into published/medium: platform rules initially fail because the “published” rule runs first, sending the note back to the published folder. Fixing it requires moving the platform-specific rules above the published rule so platform routing happens before the broader published move.

The same precedence logic applies when routing by file title instead of tags. A meeting-notes template uses a phrase in the title (e.g., “meeting notes”) to move notes into a meeting notes folder. The transcript highlights a common pitfall: title matching is exact, so missing words (like “notes”) prevents the rule from firing. Another safeguard is the disable mechanism: adding disable next to auto note mover in frontmatter prevents any movement, useful for notes that must stay put.

Finally, the transcript broadens the use of tags beyond movement. Tags can also support retrieval and grouping—such as tagging meetings and projects so a Dataview query can surface related notes later. The overall message is that Auto Note Mover becomes most reliable when templates generate consistent metadata, rules are ordered intentionally (often grouping tag rules before title rules), and manual triggering is used to validate behavior before switching to automatic mode for real workflows.