Note → Search
AI-generatedOverview
The node enables searching notes stored in a Fleeting Notes system. It supports two search modes:
- Server-Side Search: Performs a direct database query to find notes whose titles or content contain the search keyword. This mode is faster but does not support encrypted notes.
- Client-Side Search: Retrieves all notes and performs filtering locally, allowing search within encrypted notes by decrypting them first.
This node is useful when you want to quickly find relevant notes by keywords in their title or content. For example, you could use it to locate meeting notes containing a specific project name or to filter personal notes by topic.
Properties
| Name | Meaning |
|---|---|
| Search Query | Keyword to search for in note titles and content. |
| Search Mode | Search mode to use: - Client-Side (Works With Encryption) - Server-Side (Faster, No Encryption) |
| Return All | Whether to return all matching results or limit the number of results returned. |
| Limit | Maximum number of results to return if "Return All" is false. |
Output
The output consists of an array of JSON objects representing notes that match the search criteria. Each note object includes fields such as:
id: Unique identifier of the note.title: Title of the note (decrypted if encryption is used and client-side search).content: Content of the note (decrypted if applicable).created_at: Timestamp when the note was created.modified_at: Timestamp of the last modification.deleted: Boolean flag indicating if the note is deleted._partition: User ID partition key.
If encryption is enabled and client-side search is used, the node decrypts the note titles and content before returning them. If server-side search is used, notes must not be encrypted.
No binary data is output by this node.
Dependencies
- Requires an API key credential with email, password, and optionally an encryption key.
- Uses Supabase as the backend service for storing and querying notes.
- Requires n8n credentials configured with the necessary authentication details.
- The encryption/decryption uses AES via the CryptoJS library.
Troubleshooting
Error: "Search query cannot be empty"
Ensure the "Search Query" property is provided and not just whitespace.Error: "Server-side search does not support encrypted notes. Please use client-side search mode."
If your notes are encrypted, you must select the client-side search mode because server-side queries cannot decrypt data.Authentication failures
Verify that the API credentials (email and password) are correct and have access to the Fleeting Notes backend.Decryption errors
If decryption fails, check that the encryption key is correct and matches the one used to encrypt the notes.Limit and Return All conflicts
When "Return All" is false, ensure the "Limit" is set to a positive integer to avoid unexpected empty results.
Links and References
- Supabase Documentation – For understanding the backend service used.
- CryptoJS AES Documentation – For details on encryption and decryption methods used.
- n8n Node Development Guide – For general information on creating custom nodes.