Actions11
- Vault Actions
- Search Actions
- Periodic Note Actions
- Recent Actions
Overview
This node interacts with the Obsidian vault via the Local REST API to retrieve recently modified files. It is useful for workflows that need to track or process files changed within a certain timeframe, such as syncing recent notes, generating reports on recent activity, or triggering actions based on file modifications.
Use Case Examples
- Retrieve the 50 most recently modified files in the last 90 days to sync with another system.
- Get a list of files modified in the last 7 days to generate a summary report.
- Fetch recent changes with custom request options like batching or proxy settings for optimized API calls.
Properties
| Name | Meaning |
|---|---|
| Limit | Maximum number of recent modified files to return, between 1 and 100. |
| Days | Only include files modified within this many days, minimum 1 day. |
| Request Options | Advanced request settings including batching, SSL certificate validation, proxy configuration, and request timeout. |
Output
JSON
fileName- Name of the recently modified file.filePath- Path of the recently modified file within the vault.modifiedTime- Timestamp of when the file was last modified.fileSize- Size of the file in bytes.
Dependencies
- Requires an API key credential to authenticate with the Obsidian Local REST API.
Troubleshooting
- Ensure the Obsidian Local REST API is running and accessible at the configured host and port.
- Verify that the API key credential is valid and has necessary permissions.
- If SSL issues occur, consider enabling the 'Ignore SSL Issues' option, but be aware of security risks.
- Check proxy settings if requests fail due to network restrictions.
- Adjust timeout settings if the server response is slow or times out.