Obsidian
Integrate Obsidian vault with AINexLayer
Obsidian Integration Guide
This guide explains how to connect your Obsidian vault to AINexLayer for note search and AI-powered insights.
This connector requires direct file system access and only works with self-hosted AINexLayer installations.
How It Works
The Obsidian connector scans your local Obsidian vault directory and indexes all Markdown files. It preserves your note structure and extracts metadata from YAML frontmatter.
- For subsequent indexing runs, the connector uses content hashing to skip unchanged files for faster sync.
- Configure periodic indexing to ensure updates appear in your search results within minutes.
What Gets Indexed
| Content Type | Description |
|---|---|
| Markdown files | Note content (.md) |
| Frontmatter | YAML metadata like title, tags, aliases, dates |
| Wiki links | Linked notes ([[note]]) |
| Tags | Inline and frontmatter tags |
| Vault metadata | Vault and path metadata used for deep links and sync state |
Quick start
- Open Connectors in SurfSense and choose Obsidian.
- Install the plugin (recommended via BRAT) using the steps below.
- In Obsidian, open Settings → SurfSense.
- Paste your SurfSense API token from the user settings section.
- Paste your Server URL in the plugin setting: either your SurfSense main domain (if
/api/v1rewrites are enabled) or your direct backend URL. - Choose the Search Space in the plugin, then the first sync should run automatically.
- Confirm the connector appears as Obsidian - <vault> in SurfSense.
Install via BRAT (recommended)
- In Obsidian, open Settings → Community plugins and install BRAT.
- Open BRAT settings and click Add beta plugin button.
- Paste the repository:
https://github.com/MODSetter/SurfSense/. - Select the latest plugin version, then click "Add plugin".
- Open Settings → SurfSense to finish setup.
Migrating from the legacy connector
If you previously used the legacy Obsidian connector architecture, migrate to the plugin flow:
- Delete the old legacy Obsidian connector from SurfSense.
- Install and configure the SurfSense Obsidian plugin using the quick start above.
- Run the first plugin sync and verify the new Obsidian - <vault> connector is active.
Binary files and attachments are not indexed by default. Enable "Include Attachments" to index embedded files.
Step 1: Quick Start (Local Installation)
- Navigate to Connectors → Add Connector → Obsidian
- Enter your vault path:
/Users/yourname/Documents/MyVault - Enter a vault name (e.g.,
Personal Notes) - Click Connect Obsidian
Find your vault path: In Obsidian, right-click any note → "Reveal in Finder" (macOS) or "Show in Explorer" (Windows).
Periodic Sync
Enable periodic sync to automatically re-index notes when content changes. Available frequencies: Every 5 minutes, 15 minutes, hourly, every 6 hours, daily, or weekly.
Docker Setup
For Docker deployments, you need to mount your Obsidian vault as a volume.
Step 2: Docker Setup
Step 2.1: Update docker-compose.yml
Add your vault as a volume mount to the AINexLayer backend service:
services:
AINexLayer:
# ... other config
volumes:
- /path/to/your/obsidian/vault:/app/obsidian_vaults/my-vault:roThe :ro flag mounts the vault as read-only, which is recommended for security.
Deleting the legacy connector also deletes all documents that were indexed by that connector. Always finish and verify plugin sync before deleting the old connector.
Troubleshooting
Vault not found / Permission denied
- Verify the path exists and is accessible
- For Docker: ensure the volume is mounted correctly in
docker-compose.yml - Check file permissions: AINexLayer needs read access to the vault directory
Self-hosted URL issues
- Use a public or LAN backend URL that your Obsidian device can reach.
- If your instance is behind TLS, ensure the URL/certificate is valid for the device running Obsidian.
Unauthorized / 401 errors
- Regenerate and paste a fresh API token from SurfSense.
- Ensure the token belongs to the same account and workspace you are syncing into.
Cannot reach server URL
- Check that the backend URL is reachable from the Obsidian device.
- For self-hosted setups, verify firewall and reverse proxy rules.
- Avoid using localhost unless SurfSense and Obsidian run on the same machine.
