Overview
The "Fleeting Notes" node allows users to create, retrieve, update, delete, and list notes stored in a Supabase backend. Specifically, the "Get Many" operation fetches multiple notes that are not marked as deleted, optionally returning all or limiting the number of results.
This node is useful for workflows that need to manage collections of notes, such as syncing notes with other apps, generating reports from note content, or displaying user notes in dashboards.
Example use cases:
- Retrieve all active notes for a user to display in a custom app.
- Fetch a limited number of recent notes for quick review.
- Integrate notes data into other systems by exporting many notes at once.
Properties
| Name | Meaning |
|---|---|
| Return All | Whether to return all matching notes or only up to a specified limit (true/false). |
| Limit | Maximum number of notes to return if "Return All" is false. Must be at least 1. |
Output
The output consists of an array of JSON objects, each representing a single note with the following fields:
id: Unique identifier of the note.title: Title of the note (decrypted if encryption key is provided).content: Content of the note (decrypted if encryption key is provided).created_at: ISO timestamp when the note was created.modified_at: ISO timestamp when the note was last modified.deleted: Boolean flag indicating if the note is deleted (always false here since only non-deleted notes are fetched)._partition: User ID partitioning the note to a specific user.encrypted: Boolean indicating whether the note's title and content are encrypted (false in output).
If an encryption key credential is set, the node automatically decrypts the title and content fields before outputting them.
No binary data is output by this operation.
Dependencies
- Requires a Supabase backend configured with a "notes" table.
- Needs credentials including user email, password, and optionally an encryption key.
- The node uses the Supabase JavaScript client library to authenticate and query the database.
- Encryption/decryption uses AES via the CryptoJS library.
Troubleshooting
- Authentication failed: Check that the provided email and password credentials are correct.
- Failed to get user ID after authentication: Ensure the user exists and has proper permissions.
- Note not found: Occurs if a requested note ID does not exist or is marked deleted.
- Failed to fetch notes: Could indicate network issues or misconfigured Supabase project.
- Failed to decrypt note: Usually caused by an incorrect encryption key; verify the key matches what was used to encrypt notes.
- If the node throws errors related to limits or parameters, verify that "Limit" is a positive integer and "Return All" is correctly set.
Using the "Continue On Fail" option can help workflows proceed even if some notes fail to load.