Using the Obsidian Templater Plugin

Templater turns Obsidian notes into structured, semi-automated documents by letting users define reusable formats that can be filled in dynamically—far beyond simple copy-paste templates. Instead of manually typing the same headings, dates, and metadata every time, Templater can insert values based on the note’s title, frontmatter fields, the day of the week, or even which folder the note lives in. That shift matters because it reduces repetitive work while also enforcing consistent note layouts across meetings, people contacts, and even complex role-playing game logs.

A key distinction drives the workflow: Obsidian’s built-in Templates plugin is mostly static, with only a limited set of dynamic fields like date/time or title. Templater, by contrast, supports programmable replacements—so nearly anything can change depending on conditions. The tutorial demonstrates this with “single line templates,” which are written between special delimiters (left arrow, percent, percent, right arrow). One common example replaces the template line with the current file title (using a Templater expression like `tp.file.title`). Another pulls values from frontmatter parameters (for instance, inserting `tp.frontmatter.type` into a meeting note so the note automatically reflects metadata such as “type: meeting”).

From there, the workflow scales up. A meeting template is built as a reusable note skeleton that inserts the date and links the heading to the note title, keeping the heading consistent even if the underlying file name changes. A separate person template adds more automation: when a new person note is created, Templater can automatically move it into the `people` folder and populate a standard structure. It also includes a Dataview query that lists related meetings for that person, so the database updates as new notes appear.

The automation becomes “hands-off” through Templater settings. By enabling triggers on new file creation and assigning default folder templates, creating a new note in a specific folder automatically applies the right template. The result is a fast flow: create a meeting note and it already contains the date and structure; create a person note and it lands in the correct folder with the expected metadata and linked meeting list.

For a more advanced example, the tutorial showcases a tabletop role-playing (TTRPG) system that combines Templater with user scripts and multiple plugins, including Buttons, QuickAdd, Callouts, Fantasy Calendar, and Dataview. An index page tracks active campaigns (“worlds”). Clicking “Add New World” creates a new world page, then “Add Session” creates session notes that auto-increment numbering, pull in campaign/world context, and generate recap sections that summarize prior sessions. When new NPC/location notes are created during a session, Templater applies a frontmatter template automatically based on note type, so the system stays organized without manual tagging.

The approach is presented as niche and setup-heavy, but the payoff is speed and consistency: predefined fields save time, while repeatable structures keep notes comparable across weeks and campaigns. The tutorial also notes that Dataview won second place in the Obsidian Gems of the Year for 2021, positioning it as a powerful (and potentially overwhelming) complement to Templater’s automation.