Complete Guide to Obsidian Automation

What it is

A 62-page guide to automating your Obsidian vault, in three layers. Layer 1 is inside Obsidian: the seven jobs plugins should do for you (notes born correct, 3-second capture, automatic filing, formatting, queries, state machines in frontmatter, commands and buttons). Layer 2 is around the vault: Git, the command line, REST and MCP, URIs, backup and sync, scheduled jobs, publishing pipelines, ingestion, mobile, batch operations. Layer 3 is AI agents on the vault: instruction files, skills, hooks, multi-agent workflows, self-maintaining vaults, and the risks. It ends with the production setup I run on 20,000+ notes and an adoption path to start today.

The biggest mistake it warns about is the one I see most: automating too early. That’s why it sits after the Starter Kit on every path, not before.

Where to find it

Anyone: grab it from the landing page; the PDF arrives by email.

Got it on Gumroad or the store: in your purchase email and your Gumroad library.

Newsletter subscriber: the download link was in the delivery email; search your inbox for “automation”.

Do this first

Read Part I only (the mental model and the four stages). Then look at your vault and name which stage you’re at. Most people are at stage one and about to skip to stage three. Don’t.

Then

• If you use the Starter Kit: Part II describes what the kit already does for you. Read it to understand why, not to rebuild it.
• Part III when you have a real recurring chore (backup, publishing, capture from another app). One automation per chore, not a framework.
• Part IV once you’ve done the AI Master Prompt workshop and the MCP masterclass. Before that it will read as science fiction.

Skip it if

You’ve been running scripts and plugins against your vault for years. Then Part V (the production setup) is the only part with news for you.

What it leads to

Back to your path. Automation is a multiplier on a system that already works; it multiplies nothing otherwise.