Actions23
- Files Actions
- Notes Actions
- Metadata Actions
- Vault Actions
- Agent Actions
Overview
The node interacts with an Obsidian Vault via its REST API, specifically allowing retrieval of a "Daily Note" based on a given date. This is useful for users who want to programmatically access daily notes stored in their Obsidian Vault, enabling automation workflows such as fetching journal entries or logs for specific days.
A practical example would be automating the extraction of your daily note for "today" or any specific date (e.g., "2024-06-01") to process or analyze its content further in n8n.
Properties
| Name | Meaning |
|---|---|
| Date | Specifies which daily note to retrieve. Accepts values like today, yesterday, tomorrow, or a specific date in YYYY-MM-DD format. |
Output
The node outputs JSON data representing the content and metadata of the requested daily note from the Obsidian Vault. The exact structure depends on the API response but typically includes fields such as the note's text content, creation date, and possibly other metadata related to the note.
If the node supports binary data output (not explicitly shown here), it would represent file contents or attachments related to the daily note.
Dependencies
- Requires access to an Obsidian Vault REST API endpoint.
- Needs an API host URL configured in credentials.
- Optionally requires an API authentication token or key to authorize requests to the Vault API.
Troubleshooting
- Common issues:
- Incorrect or missing API host URL can cause connection failures.
- Invalid date formats may result in errors or empty responses.
- Lack of proper authentication might lead to authorization errors.
- Error messages:
- Connection refused or timeout errors indicate network or host configuration problems.
- 401 Unauthorized or 403 Forbidden errors suggest missing or invalid API credentials.
- 404 Not Found may occur if the specified daily note does not exist for the given date.
To resolve these, verify the API host URL, ensure correct date formatting, and confirm that valid credentials are provided.
Links and References
- Obsidian Vault REST API Documentation (example link; replace with actual if available)
- n8n Documentation on HTTP Request Nodes (for understanding API calls)