Note → Get Many
AI-generatedOverview
This node integrates with the Fleeting Notes service, allowing users to manage notes stored in a Supabase backend. The "Get Many" operation retrieves multiple notes from the user's account, supporting options to either return all notes or limit the number of results.
Common scenarios for this node include:
- Fetching a list of recent notes for display or further processing.
- Synchronizing notes from Fleeting Notes into another system.
- Exporting notes data for backup or analysis.
For example, a user might use this node to retrieve their latest 50 notes to generate a summary report or to feed them into a text analysis workflow.
Properties
| Name | Meaning |
|---|---|
| Return All | Whether to return all available notes (true) or only up to a specified limit (false). |
| Limit | Maximum number of notes to return when "Return All" is false. Must be at least 1. |
Output
The output is an array of JSON objects, each representing a 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 as deleted notes are filtered out)._partition: User ID partitioning the note to the authenticated user.encrypted: Boolean indicating whether the note's title and content are encrypted.
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 connection to a Supabase backend service.
- Needs user credentials: email, password, and optionally an encryption key for secure note storage.
- Requires an API authentication token (credential) configured in n8n to authenticate with the Fleeting Notes service.
- Uses the Supabase JavaScript client library internally.
Troubleshooting
- Authentication failed: Ensure that the email and password credentials are correct and that the user exists in the Fleeting Notes system.
- Failed to fetch notes: Could indicate network issues or misconfiguration of the Supabase project URL or API key.
- Decryption errors: If an encryption key is provided but incorrect, decryption of note titles or content will fail. Verify the encryption key matches the one used to encrypt the notes.
- Limit and Return All settings: Setting "Return All" to false without specifying a valid positive "Limit" may cause unexpected behavior; ensure "Limit" is at least 1.
- Empty results: If no notes are returned, verify that notes exist for the authenticated user and that none are marked as deleted.