npm package discovery and stats viewer.

Discover Tips

  • General search

    [free text search, go nuts!]

  • Package details

    pkg:[package-name]

  • User packages

    @[username]

Sponsor

Optimize Toolset

I’ve always been into building performant and accessible sites, but lately I’ve been taking it extremely seriously. So much so that I’ve been building a tool to help me optimize and monitor the sites that I build to make sure that I’m making an attempt to offer the best experience to those who visit them. If you’re into performant, accessible and SEO friendly sites, you might like it too! You can check it out at Optimize Toolset.

About

Hi, 👋, I’m Ryan Hefner  and I built this site for me, and you! The goal of this site was to provide an easy way for me to check the stats on my npm packages, both for prioritizing issues and updates, and to give me a little kick in the pants to keep up on stuff.

As I was building it, I realized that I was actually using the tool to build the tool, and figured I might as well put this out there and hopefully others will find it to be a fast and useful way to search and browse npm packages as I have.

If you’re interested in other things I’m working on, follow me on Twitter or check out the open source projects I’ve been publishing on GitHub.

I am also working on a Twitter bot for this site to tweet the most popular, newest, random packages from npm. Please follow that account now and it will start sending out packages soon–ish.

Open Software & Tools

This site wouldn’t be possible without the immense generosity and tireless efforts from the people who make contributions to the world and share their work via open source initiatives. Thank you 🙏

© 2026 – Pkg Stats / Ryan Hefner

n8n-nodes-obsidian-cli-api

v0.2.7

Published

n8n community nodes for the Obsidian API Docker service backed by the official Obsidian CLI.

Readme

n8n-nodes-obsidian-cli-api

n8n community-node package for the Obsidian API Docker service.

It talks to the HTTP API, which then runs the official Obsidian CLI against mounted vaults. The node sends structured args arrays only. It does not send shell commands.

Nodes

Obsidian API

Resources:

  • Note
    • Create
    • Read
    • Append
    • Prepend
    • Delete
    • Rename
    • List Files
  • Property
    • Set
    • Read
    • Remove
    • List
  • Daily Note
    • Append
    • Prepend
    • Read
    • Path
  • Search
    • Search
    • Search With Context
  • Vault
    • Info
    • List Vaults
  • Raw Command
    • Safe args-array escape hatch for any official CLI command

Credentials

Credential type: Obsidian API

Fields:

  • Base URL: URL of your Obsidian API service, e.g. http://localhost:8080
  • API Token: JWT created with scripts/create_jwt.py
  • Default Vault: optional, e.g. work

Multi-vault

Set the Vault field on a node to override the credential default vault.

The node sends this as the official CLI prefix:

vault=work

Raw command example:

["vault=work", "read", "path=Inbox/Note.md"]

Properties / frontmatter

The official Obsidian CLI supports property/frontmatter commands. The n8n node exposes them as the Property resource:

  • Set sends property:set path=<note> name=<property> value=<value> type=<type>
  • Read sends property:read path=<note> name=<property>
  • Remove sends property:remove path=<note> name=<property>
  • List sends properties name=<optional> format=<yaml|json|tsv>

Examples:

path=00 Kontext/Feedback Browser CLI Tests.md
name=tags
value=kontext, feedback-browser-cli-tests
type=list
path=00 Kontext/Feedback Browser CLI Tests.md
name=date
value=2026-06-24
type=date

Local install in self-hosted n8n

From this repo:

cd packages/n8n-nodes-obsidian-api
npm install --ignore-scripts
npm run build
npm pack

Then install the generated .tgz in your n8n custom extensions setup.

For Docker-based n8n, one common setup is mounting this package into n8n's custom extensions directory and setting:

N8N_CUSTOM_EXTENSIONS=/home/node/.n8n/custom

Exact installation depends on your n8n deployment.

Development

npm install --ignore-scripts
npm run typecheck
npm run build

--ignore-scripts avoids local native builds from n8n transitive dependencies on unsupported bleeding-edge Node versions. Use the Node version recommended by your n8n release for production builds.