Automating Workflows with Templater in Obsidian

Enabling the Templater plugin in Obsidian turns meeting-note templates into a more automated workflow: it can generate dated notes from a template and then automatically place each new note into the correct folder. The setup starts by switching Obsidian out of restricted/safe mode so community plugins can be installed, then installing “templater” and enabling it. After that, the key configuration is setting the “template folder location” to the vault’s templates folder—because any file placed there becomes available as a template.

With Templater enabled, the workflow shifts from the core Templates plugin’s simpler placeholders to Templater’s template language. The first upgrade replaces a static “title” field with a dynamic header that stays synchronized with the file name. Using Templater command syntax (wrapped in <%%>), the template pulls in the file name and injects today’s date automatically. A test note created in the meetings folder—named like “2022.0901 staff meeting”—shows the payoff immediately: the note is generated with the correct title and date without manual entry.

The automation then goes further by creating a specialized “team meeting template.” A copy of the original meeting template is renamed and edited to include team-specific structure: agenda sections, links to project lists, and an attendee checklist. The template also includes a reminder to distribute notes after the meeting and a small formatting element for readability.

Finally, the template becomes folder-aware. A new subfolder under meetings—“team meetings”—is created, and the template is modified with a command line that moves the newly created note into that folder automatically. This is done by adding a line at the bottom of the template that uses Templater’s file module to move the file upon creation to “meetings/team meetings/” while preserving the generated title. When a new note is created from the team meeting template, it appears in the correct folder immediately, and the move command line disappears from the resulting note because it has already executed.

Overall, the core finding is practical: Templater doesn’t just fill in fields like a basic template system—it can generate content dynamically (like dates and file-linked headers) and enforce organizational rules (like routing notes into the right meeting subfolder) at creation time. That combination reduces repetitive steps and keeps meeting notes consistently structured and filed.