How to set up a "project folder blueprint"

Let’s say you have a certain way you set up your project folders, and you want a “project blueprint” so you don’t have to manually create that particular folder structure again and again.


  1. Built-in Ask for Input action: It prompts you for the project name.
  2. Get Vault Reference action to get a reusable reference to the target vault – should the target vault change, you’ll only have to change this one action, and not all the other AFO actions
  3. Create Folder action creates first project folder.
  4. Create Folder action creates another nested set of project folders.
  5. Built-in Text action containing your project note body.
  6. And a final Create Note action for creating the note using the note body.

This is just an example, obviously, and you’ll likely want to use a note template in (5). Go nuts!


When prompted (see action (1), above), I’ve entered “ActionsDotWork example”.



Adjusts vault handling to work with AFO 2024.1.

1 Like

Thanks for another great example. I was thinking about creating a “project blueprint” shortcut, and this got me started. Of course, I will experiment and extend this further. For example, I will probably also want to create an OmniFocus project and establish bi-directional links between them.

1 Like

Workflow updated: Adjusted vault handling to work with AFO 2024.1.

Hi Doug, great idea with the Omnifocus project with bi-directional links…any progress on that form your side to share?

Yes, I have done a lot on Obsidian Integration. This includes generating Efforts (or Projects) in Obsidian using prompted templates along with generated properties, title, navigation, and structure, including associated maps, canvas, folders, and OmniFocus links.

I have shared my progress with the LYT community during recent workshops, posts, and showcases. I’m currently working on getting these ready for publishing via my Ghost website and newsletter.

1 Like