What is a "known vault"?

Every time one of AFO's actions calls Obsidian, and its companion plugin Actions URI answers from within the requested vault, this is considered a successful vault connection.

Starting in 1.3, Actions for Obsidian remembers those successful vault connections, and shows you a list of those vaults when you need to specify a vault in a Shortcuts action. These are called "known vaults".

For example, this screenshot shows that AFO knows about two of my vaults, "Gewerbe" and "Workbench", and so it lets me select from them in a Create Note action:

Screenshots of a "Create Note" action, with the `Vault` parameter offering a selection of two known vaults, "Gewerbe" and "Workbench".

How do I make a vault known to Actions for Obsidian?

There are two ways:

  1. Run the vault setup in AFO, i.e. the "Link Actions for Obsidian with a Vault" onboarding process.
  2. If you have existing, working workflows, just run them — AFO will notice successful actions and add the vault(s) to the list.

How can I delete a known vault?

Open the app, find your list of known vaults in the "Settings" tab. A vault can be deleted by clicking the trashcan icon next to the name (macOS) or by swiping (iOS).

Good to know

If you want an action to use a vault which you know was set up for use with Actions for Obsidian already but which isn't known to AFO yet, you can also manually enter a name in this selection list.

  1. Enter the name
  2. The name will be added temporarily to the selection list (i.e., for this one action only)
  3. Click/tap the name in the list to use it.

Step 3 is crucial — Shortcuts can be a bit weird at times.

In the GIF below, I tell the action to call a vault it hasn't seen before, "Another vault":

(For this to work, Actions URI must be active in this particular vault.)

When the action is successful, the vault will of course be added to the list of known vaults, and you'll see it the next time you need to specify a vault.

Did this answer your question? Thanks for the feedback There was a problem submitting your feedback. Please try again later.