Automate Your Vault With Templater - How to Use Templater in Obsidian

Templater for Obsidian turns static templates into automated, context-aware workflows—at the cost of a longer setup. Instead of manually inserting the same template every time, Templater can generate note content dynamically using variables like the day of the week and where a note was created. Once configured, it becomes a fast way to keep daily notes, weekly planning, and folder-specific documents consistent without repeating the same work.

A key distinction from the Template plugin is automation. The Template plugin mostly provides reusable blocks, while Templater can apply templates based on conditions and parameters. That flexibility is why the setup takes longer: users must learn the syntax and configure when templates trigger. Internally, Templater functions are split into internal functions and user functions; the walkthrough focuses on internal functions, including access to date/time logic and file metadata. (User functions and the Moment object are mentioned as topics for a future, more advanced video.)

The tutorial starts with the core syntax pattern: every Templater function is wrapped between “<%” and “%>” (shown as left arrow percentage and percentage right arrow). A practical friction point appears immediately: after inserting the syntax, results don’t show in preview mode. To apply changes, users must run “Replace templates in the active file” from the command palette—or assign a hotkey to trigger it. The walkthrough recommends setting a hotkey (for example, Option+R) so activation becomes a single keystroke.

For date automation, the most used functions are “tpdate” and “tpfile.” With “tpdate,” users can generate dates in different formats and relative offsets. The examples show how to produce today’s date, yesterday/tomorrow, and dates in the past or future using offsets like “-1m” (one month back), “+2” (two months forward), and “-1y” (one year back). A major upgrade comes when date outputs are turned into links: wrapping the function in square brackets can create clickable references to daily notes for the computed date, assuming those notes exist in the vault.

The walkthrough then uses this to build “on this day” links inside daily notes, so each entry can jump back to the same date from last year. It also adds navigation breadcrumbs for adjacent days (day before/day after) and weekly shortcuts that link to the current week’s Monday. For the weekly link, “tpdate weekday” uses a numeric mapping where 0 represents Monday and other numbers represent subsequent weekdays.

Beyond dates, “tpfile” pulls file-level metadata. It can insert the file’s creation time, last modified time, and the folder path the file currently lives in—useful for templates that adapt to where notes are stored. Another internal function, “tpweb,” can fetch a daily quote (and optionally random images) from the web; the example uses daily quotes to add low-effort variety to journal entries.

Finally, the tutorial shows how to scale this approach across a vault: folder templates apply specific templates automatically to new files created inside designated folders, while hotkeys provide quick access to templates without relying on folder structure. A “default template” hotkey (triggered via Command+M after Command+N) demonstrates how spontaneously created notes can still receive consistent YAML fields like tags, aliases, created/last modified timestamps, and a title prompt. The guide closes by pointing to Templater’s active GitHub community for inspiration, with a warning not to copy snippets blindly without understanding how they fit a vault’s structure.