To connect Obsidian to OpenClaw, configure the path to your Obsidian vault in OpenClaw's config file — no API key required. OpenClaw reads and writes markdown files in your vault directory directly via the local filesystem. Once configured, OpenClaw can create notes, search across your vault, append to daily notes, and read existing content. This is a local-first integration with no network calls to third-party services.
Why Connect Obsidian to OpenClaw?
Obsidian's strength is its local-first architecture — all your notes live as plain Markdown files on your filesystem. There are no server APIs to authenticate against, no rate limits to worry about, no account required. This is also what makes the OpenClaw integration unusually simple: OpenClaw reads and writes .md files in your vault directory the same way any other program would, using standard filesystem operations.
The integration enables powerful knowledge management workflows. You can instruct OpenClaw to research a topic and automatically save the findings as a structured note in your vault. You can have OpenClaw append task summaries to your daily note at end-of-session. You can search across thousands of notes using OpenClaw's natural language processing to find relevant content without remembering exact filenames or tags. Because Obsidian's file format is plain text, there is no data transformation needed — OpenClaw writes valid Markdown and Obsidian displays it immediately.
This integration shines for personal knowledge management, research workflows, and developers who use Obsidian as a local second brain. It does not require an active internet connection for vault operations, which makes it reliable even offline. The main limitation is that both OpenClaw and Obsidian must be on the same machine — if your vault is synced via Obsidian Sync or iCloud, OpenClaw can still access it as long as the sync folder is locally available at the configured path.
Integration method
Obsidian stores all notes as plain Markdown files in a local folder called a vault. OpenClaw integrates with Obsidian by reading and writing these .md files directly — no API key, no Obsidian account, no network requests. You configure the vault path in OpenClaw's config, and OpenClaw uses standard filesystem operations to create notes, search content, read files, and append to existing notes. This makes the integration simple and extremely fast, but it requires OpenClaw to be running on the same machine where your vault is stored.
Prerequisites
- Obsidian installed with at least one vault created on your local machine
- The full filesystem path to your Obsidian vault directory (e.g., /Users/username/Documents/MyVault or ~/Documents/MyVault)
- OpenClaw installed and running on the same machine as your Obsidian vault
- Basic knowledge of Markdown syntax and Obsidian's note structure (folders, tags, frontmatter)
- No API key or Obsidian account required for this integration
Step-by-step guide
Find Your Obsidian Vault Path
Find Your Obsidian Vault Path
Before configuring OpenClaw, you need the exact filesystem path to your Obsidian vault. The vault is a regular folder on your computer — Obsidian just opens it as a special folder containing your notes. To find the path in Obsidian: open Settings (Cmd+, on Mac or Ctrl+, on Windows), then go to 'About' at the top of the settings sidebar. You will see 'Current vault' with the full path listed — for example `/Users/yourname/Documents/MyVault` or `C:\Users\yourname\Documents\MyVault`. Alternatively, right-click on the vault name at the bottom of the Obsidian sidebar and choose 'Reveal in Finder' (Mac) or 'Show in Explorer' (Windows). The path shown in the file manager's address bar is your vault path. Note the path exactly — including the correct case for folder names, since OpenClaw's filesystem operations are case-sensitive on Linux and macOS. On macOS, you can use `~` as shorthand for your home directory in OpenClaw's config (e.g., `~/Documents/MyVault`).
1# Find your vault path in Terminal (macOS/Linux):2# Method 1: Drag the vault folder from Finder into Terminal to print the path34# Method 2: Search for .obsidian hidden folders (marks vault root)5find ~/Documents -name '.obsidian' -type d 2>/dev/null6# Output example: /Users/yourname/Documents/MyVault/.obsidian7# Your vault path is: /Users/yourname/Documents/MyVault (without /.obsidian)89# Verify the vault exists and contains .md files:10ls ~/Documents/MyVault/*.md 2>/dev/null || ls ~/Documents/MyVault/11# Should list your note filesPro tip: If you use Obsidian Sync to keep your vault synced across devices, the vault folder still exists on each device at a local path — OpenClaw uses the local path on the machine where it runs. The sync service will pick up any files OpenClaw creates and propagate them to your other devices.
Expected result: You have the full filesystem path to your Obsidian vault, verified that .md files exist in it, and confirmed that the path is accessible from the command line.
Configure the Obsidian Vault Path in OpenClaw
Configure the Obsidian Vault Path in OpenClaw
Open your OpenClaw config file at `~/.openclaw/config.yaml` and add the Obsidian integration under the `integrations` key. The `vault_path` field is the most important setting — it tells OpenClaw where your vault lives on the filesystem. The `notes_folder` setting is optional but recommended — it specifies a subdirectory within the vault where OpenClaw creates new notes by default. This prevents OpenClaw from cluttering the vault root. Common values are `Inbox`, `OpenClaw`, or `AI Notes`. The `daily_notes_folder` setting maps to the folder your Obsidian daily notes plugin uses — set this to match Obsidian's configuration (Settings > Core Plugins > Daily Notes > New file location). The default in Obsidian is the vault root. The `daily_notes_format` must exactly match the date format Obsidian uses for daily note filenames — the default is `YYYY-MM-DD`. If you changed this in Obsidian's settings, update this field to match. Run `clawhub reload` after saving to apply the config.
1# ~/.openclaw/config.yaml2integrations:3 obsidian:4 vault_path: "~/Documents/MyVault" # Full path to your vault5 notes_folder: "Inbox" # Where to create new notes (relative to vault root)6 daily_notes_folder: "Daily Notes" # Folder for daily notes (match Obsidian setting)7 daily_notes_format: "YYYY-MM-DD" # Filename format (match Obsidian setting)8 frontmatter:9 auto_add: true # Auto-add frontmatter to created notes (default: true)10 tags: ["openclaw"] # Default tags added to all OpenClaw-created notes11 author: "OpenClaw" # Default author field12 create_folders: true # Create subdirectory if notes_folder doesn't existPro tip: Set `create_folders: true` so OpenClaw automatically creates the `notes_folder` if it does not exist yet — this prevents errors on first use if the `Inbox` folder does not exist in your vault.
Expected result: `clawhub reload` runs without errors and OpenClaw's config shows the Obsidian vault path correctly resolved.
Test Note Creation and Reading
Test Note Creation and Reading
Verify the integration by having OpenClaw create a test note in your Obsidian vault. The test creates a .md file in your configured `notes_folder`, adds frontmatter (title, date, tags), and writes test content. Open Obsidian and verify the note appears in the file list. The note content OpenClaw writes must be valid Obsidian Markdown — frontmatter at the top enclosed in `---` delimiters, followed by the note body. Obsidian reads the frontmatter as metadata (visible in Properties view) and displays the body as formatted text. Also test reading an existing note to confirm OpenClaw can retrieve vault content. Reading uses the note's file path relative to the vault root. Wikilinks in the format `[[Note Title]]` are preserved as-is when OpenClaw reads them — OpenClaw does not resolve backlinks during reads, it returns the raw Markdown.
1# Test note creation — creates a file at YOUR_VAULT/Inbox/OpenClaw-Test.md2# This is the Markdown format OpenClaw writes to your vault:34---5title: OpenClaw Integration Test6date: 2026-03-307tags: [openclaw, test]8author: OpenClaw9---1011# OpenClaw Integration Test1213This note was created by OpenClaw to verify the Obsidian vault integration.1415## Summary1617- Vault path configured correctly18- Note creation working19- Frontmatter parsed by Obsidian2021## Related Notes2223- [[Daily Notes/2026-03-30]]2425---26*Created by OpenClaw on 2026-03-30*Pro tip: After OpenClaw creates the test note, switch to Obsidian and press Cmd+R (Mac) or Ctrl+R (Windows) to refresh the file list if the new note does not appear immediately. Obsidian usually picks up new files within a few seconds, but a manual refresh forces immediate detection.
Expected result: A new .md file appears in your Obsidian vault's Inbox folder with correct frontmatter and body content. Reading the file via OpenClaw returns the full Markdown text.
Configure Automated Vault Workflows
Configure Automated Vault Workflows
With basic read/write confirmed, configure OpenClaw workflows that automate vault operations. Common patterns include: appending to daily notes at session end, creating research notes after web search tasks, and tagging notes based on content type. The daily note append workflow constructs the current day's note path dynamically using the date format from your config. If the daily note does not exist yet, OpenClaw creates it with a basic template. If it does exist, OpenClaw appends to the end of the file without overwriting existing content. For research note creation, the workflow triggers after search tasks complete and creates a structured note with the query as the title, a summary section, and source URLs in the frontmatter. Notes are saved to the configured `notes_folder` and immediately visible in Obsidian. The vault search workflow scans .md files for keyword matches using filesystem search, then reads the matching files and synthesizes a summary. This is slower than a true search index but requires no additional setup.
1# ~/.openclaw/config.yaml — Obsidian automation workflows2workflows:3 daily-note-append:4 trigger:5 type: session-end6 actions:7 - type: obsidian-append8 integration: obsidian9 path: "Daily Notes/{{date:YYYY-MM-DD}}.md"10 create_if_missing: true11 content: |12 ## OpenClaw Session — {{timestamp}}1314 **Tasks completed:** {{session.task_count}}15 **Searches run:** {{session.search_count}}1617 {{session.summary}}1819 research-note-create:20 trigger:21 type: task-complete22 task_type: web-search23 actions:24 - type: obsidian-create25 integration: obsidian26 filename: "Research/{{trigger.query|slugify}}.md"27 frontmatter:28 title: "{{trigger.query}}"29 date: "{{date:YYYY-MM-DD}}"30 tags: ["research", "openclaw"]31 sources: "{{trigger.sources}}"32 body: |33 # {{trigger.query}}3435 ## Summary3637 {{trigger.summary}}3839 ## Sources4041 {{trigger.sources_list}}Pro tip: Use Obsidian's 'Templates' core plugin to create a base template for each note type OpenClaw generates. While OpenClaw writes the frontmatter directly, keeping a matching Obsidian template makes it easy to manually create consistent notes when not using OpenClaw.
Expected result: OpenClaw automatically creates and updates Obsidian notes based on your configured workflow triggers, and the notes appear correctly formatted in Obsidian.
Common use cases
Auto-Save Research Findings to Vault
After OpenClaw completes a web research task, automatically create a new Markdown note in a designated 'Research' folder in your Obsidian vault. The note includes frontmatter with date, tags, and source URLs, and the body contains OpenClaw's synthesized summary. The file appears in Obsidian immediately after OpenClaw writes it.
Build an OpenClaw config that creates a new note in my Obsidian vault under 'Research/' after every search task, using the query as the filename and including source URLs in the frontmatter
Copy this prompt to try it in OpenClaw
Daily Note Journaling Integration
Configure OpenClaw to append a structured end-of-day summary to your Obsidian daily note — tasks completed, decisions made, and open questions. OpenClaw constructs the note path from the current date (matching Obsidian's daily note naming convention) and appends the formatted content to the existing file.
Set up OpenClaw to append a daily summary section to my Obsidian daily note at VAULT_PATH/Daily Notes/YYYY-MM-DD.md after each session, including completed tasks and key decisions
Copy this prompt to try it in OpenClaw
Vault Search and Cross-Reference
Ask OpenClaw to search your Obsidian vault for notes related to a topic, summarize what you have already written, and identify gaps in your notes. OpenClaw scans the vault directory for .md files matching a query, reads the relevant files, and synthesizes a response — useful for quickly recalling research you completed weeks ago.
Configure OpenClaw to search my Obsidian vault at ~/Documents/ObsidianVault for all notes mentioning 'machine learning' and summarize the key points I have already written
Copy this prompt to try it in OpenClaw
Troubleshooting
OpenClaw shows 'vault path not found' or 'permission denied' when accessing the vault
Cause: The `vault_path` in the config is incorrect (wrong folder name, typo, or uses a path that does not exist), or the path uses Windows backslashes on a system expecting forward slashes.
Solution: Verify the vault path exists by opening it in your file manager or running `ls YOUR_VAULT_PATH` in the terminal. On macOS, paths are case-sensitive — `MyVault` and `myvault` are different. On Windows, use forward slashes in the config (`C:/Users/name/Documents/MyVault`) — backslashes cause YAML parsing issues.
1# Verify vault path is accessible:2ls -la ~/Documents/MyVault/ # macOS/Linux3# or for Windows path in WSL:4ls -la '/mnt/c/Users/yourname/Documents/MyVault/'56# Check .obsidian folder exists (confirms it is a valid vault):7ls ~/Documents/MyVault/.obsidian/Notes created by OpenClaw do not appear in Obsidian's file list
Cause: Obsidian's file watcher has not detected the new files yet, or the notes were created in a folder that Obsidian is excluding via its 'Excluded files' setting.
Solution: In Obsidian, press Ctrl+P (Cmd+P on Mac) to open the command palette and run 'Reload app without saving' to force a full file system rescan. If notes still do not appear, check Settings > Files & Links > Excluded files and ensure the folder OpenClaw is writing to is not excluded.
Frontmatter tags are not appearing in Obsidian's tag panel
Cause: OpenClaw wrote tags in an incorrect YAML format — for example, as a comma-separated string instead of a YAML list, or with inconsistent spacing in the frontmatter block.
Solution: Obsidian requires tags in frontmatter to be a YAML list: `tags: [openclaw, research]` or multi-line `tags:\n - openclaw\n - research`. A plain string like `tags: openclaw` is not recognized. Open the note in a text editor and verify the frontmatter YAML syntax is correct.
1# Correct frontmatter format for Obsidian tags:2---3title: Note Title4date: 2026-03-305tags:6 - openclaw7 - research8---910# Incorrect (will not show in tag panel):11---12tags: openclaw, research13---clawhub reload errors with 'obsidian integration: vault_path is required'
Cause: The `vault_path` field is missing or empty in the YAML config, or the `obsidian` key is indented incorrectly under `integrations`.
Solution: Verify the YAML structure uses exactly two spaces for indentation at each level. The `vault_path` must be a non-empty string. Check that the `obsidian` key is a child of `integrations`, not at the top level of the config.
1# Correct YAML structure:2integrations:3 obsidian:4 vault_path: "~/Documents/MyVault"56# Incorrect (obsidian at wrong indent level):7integrations:8obsidian: # wrong — this is top-level9 vault_path: "~/Documents/MyVault"Best practices
- Always use relative paths for note creation within the vault (e.g., `Research/my-note.md` not `/Users/name/Vault/Research/my-note.md`) — relative paths work correctly when the vault is moved or synced to a new machine.
- Add `openclaw` as a default tag in your config's frontmatter settings so you can easily filter OpenClaw-created notes in Obsidian's tag panel and distinguish them from manually written notes.
- Use a dedicated `Inbox` or `OpenClaw` subfolder for all automatically created notes — this keeps the vault organized and gives you a single folder to review and process AI-generated content.
- Never configure OpenClaw to write directly to `.obsidian/` (the hidden config folder) — that folder contains Obsidian's internal configuration and workspace state, not user notes.
- Back up your vault before enabling automated note creation workflows — test with a copy of your vault first to ensure OpenClaw's note format integrates well with your existing templates and folder structure.
- Match the `daily_notes_format` exactly to Obsidian's daily note filename format (check Settings > Core Plugins > Daily Notes) — a mismatch causes OpenClaw to create duplicate daily notes with slightly different filenames.
- If you use Obsidian Sync across multiple devices, let the sync service propagate OpenClaw-created notes — do not try to read notes from the vault on a different machine simultaneously, as this can cause sync conflicts.
Alternatives
Notion is cloud-based with a proper API and works from any device — use it instead of Obsidian if your notes need to be accessible across machines without a local vault sync setup.
Bear Notes uses the x-callback-url scheme rather than direct filesystem access — use Bear if you prefer a polished macOS/iOS native app but do not need OpenClaw to write raw Markdown files.
Apple Notes integrates with macOS via AppleScript for richer metadata and search — use it if you are already using Apple Notes as your primary note app on macOS.
Google Sheets is better for tabular, structured data that multiple people need to access — use it instead of Obsidian when your notes are really data records rather than freeform Markdown documents.
Frequently asked questions
How do I connect Obsidian to OpenClaw?
Set the `vault_path` under `integrations.obsidian` in `~/.openclaw/config.yaml` to the full path of your Obsidian vault folder. No API key or Obsidian account is needed — OpenClaw reads and writes .md files directly. Run `clawhub reload` after saving the config and test by having OpenClaw create a note.
Does OpenClaw Obsidian integration require an API key?
No — Obsidian is a local application with no server API. OpenClaw accesses your vault by reading and writing Markdown files in the vault directory directly. The only configuration required is the vault path in OpenClaw's config file.
Can OpenClaw access my Obsidian vault from a different machine?
Only if the vault is accessible on that machine's filesystem. If you use Obsidian Sync, iCloud, or Dropbox to sync your vault, OpenClaw on another machine can access the local sync folder. OpenClaw cannot access Obsidian vaults over the network directly — it uses local filesystem operations only.
Will OpenClaw overwrite my existing Obsidian notes?
By default, OpenClaw's `obsidian-append` action appends to existing notes without overwriting them, and `obsidian-create` creates new files with a unique timestamp in the filename to avoid collisions. Configure `overwrite: false` (the default) in your workflow actions to ensure existing notes are never overwritten.
Does the Obsidian integration support wikilinks and backlinks?
OpenClaw can write wikilinks in the `[[Note Title]]` format and Obsidian will recognize them correctly. OpenClaw does not resolve backlinks during reads — when reading a note, it returns the raw Markdown including wikilink syntax. Backlink resolution is handled by Obsidian's graph engine, not OpenClaw.
Can RapidDev help configure Obsidian vault workflows in OpenClaw?
Yes — RapidDev can help design OpenClaw workflows that integrate with complex Obsidian vault structures, including multi-folder hierarchies, template-based note creation, and automated tagging systems. Reach out if your vault has custom folder structures or you need notes to cross-reference specific existing content.
Talk to an Expert
Our team has built 600+ apps. Get personalized help with your project.
Book a free consultation