Actions11
- Vault Actions
- Search Actions
- Periodic Note Actions
- Recent Actions
Overview
This node interacts with an Obsidian vault via the Local REST API, specifically to create or update files within the vault. It allows users to specify the file path relative to the vault root and the content to write to the file. This is useful for automating note-taking, updating documentation, or managing files programmatically within an Obsidian vault.
Use Case Examples
- Automatically create or update a markdown note in the vault with new content from another workflow.
- Batch update multiple files in the vault with different content, using batching options to control request flow.
Properties
| Name | Meaning |
|---|---|
| File Path | Path to the file to create or update (relative to vault root) |
| Content | Content to write to the file |
| Request Options | Additional options for the request such as batching, SSL certificate validation, proxy settings, and timeout settings |
Output
JSON
filePath- The path of the file created or updated in the vault.content- The content written to the file.status- Status of the create or update operation, indicating success or failure.
Dependencies
- Requires an API key credential for the Obsidian Local REST API, including protocol, host, and port configuration.
Troubleshooting
- Ensure the Obsidian Local REST API is running and accessible at the configured host and port.
- Verify that the file path is correct and relative to the vault root to avoid file not found or permission errors.
- Check SSL certificate settings if using HTTPS and encountering SSL validation errors; consider enabling 'Ignore SSL Issues' if safe.
- If using a proxy, ensure the proxy URL and credentials are correct.
- Timeout errors may occur if the server is slow to respond; increase the timeout setting if needed.
Links
- Obsidian API Documentation - Official documentation for the Obsidian Local REST API used by this node.