Quick Start

Install the plugin, create a first action, and verify the setup.

Install The Plugin

Community Plugin

Since this plugin isn't officially released in the Community Plugins store yet, the easiest way to install it is with Obsidian BRAT, which lets you install plugins directly from GitHub.

After BRAT is enabled:

Manual Install

Copy the plugin into vault/.obsidian/plugins/actions:

main.js
styles.css
manifest.json

Manual Install

Copy the plugin into <vault>/.obsidian/plugins/actions:

main.js
styles.css
manifest.json

Then enable Obsidian Actions in Community Plugins.

Create Your First Action

  1. Open Settings -> Actions.
  2. Click Create.
  3. Fill in the action:
FieldRequiredNotes
nameYesDisplay name shown in settings and commands
hookYesWhen the action runs
typeYesjs or shell
codeYesThe action body
scheduleFor interval onlyCron expression
enabledYesWhether the action is active
iconNoOptional Lucide icon name
descriptionNoOptional internal description
  1. Save the action.
  2. Restart Obsidian.

Create A Test Action

Start with a manual JavaScript action:

new Notice("Action ran");

Use these fields:

  • hook: manual
  • type: js
  • enabled: true

After restarting Obsidian, open the command palette and run the action by name.

You can also use the play button in the settings screen to test directly.

Add Runtime Variables

Action code is rendered before execution, so you can reference values from the current vault and editor state.

echo "Current file: {{{relative_path}}}"

Use triple braces when you want the raw value inserted directly.

Move To Automatic Hooks

Once a manual action behaves correctly, move it to startup, interval, or a file hook.

That keeps debugging simple and reduces the risk of noisy or repeated runs while you are still developing the action.

Changes Need A Restart

Adding, renaming, enabling, disabling, or retargeting an action does not fully re-register behavior live. Restart Obsidian before relying on the new command or hook.

On this page