Fleeting NotesInstall

Overview

The node "Fleeting Notes" allows users to create, retrieve, update, delete, and search notes stored in a remote database service. Specifically, the Update Note operation modifies existing notes by changing their title and/or content. This node is useful for managing personal or shared notes programmatically within an automation workflow.

Typical use cases include:

• Updating meeting notes or task descriptions dynamically.
• Modifying content of notes based on external triggers or inputs.
• Keeping notes synchronized with other systems by updating them automatically.

For example, you could automate updating a note's content after receiving new information from another app or user input.

Properties

Output

The output is an array of JSON objects representing the updated note(s). Each object contains the note's properties such as:

• id: Unique note identifier.
• title: Updated title of the note (decrypted if encryption key is provided).
• content: Updated content of the note (decrypted if encryption key is provided).
• created_at: Timestamp when the note was created.
• modified_at: Timestamp when the note was last modified.
• deleted: Boolean flag indicating if the note is deleted.
• _partition: User ID partitioning the note.

If encryption is enabled via credentials, the node transparently encrypts the title and content before sending updates and decrypts them on retrieval.

No binary data output is produced by this node.

Dependencies

• Requires an API key credential with email, password, and optionally an encryption key.
• Connects to a Supabase backend service for authentication and data storage.
• Uses AES encryption/decryption for note content if an encryption key is provided.
• Requires n8n credentials configured with the necessary API authentication details.

Troubleshooting

• Missing Credentials: If email or password credentials are missing, the node will throw an error indicating required credentials are not set.
• Authentication Failure: Errors during login to the backend service will result in an authentication failure message.
• Empty Note ID: The node requires a non-empty Note ID for update operations; otherwise, it throws an error.
• No Update Fields Provided: At least one field (title or content) must be specified to update; otherwise, an error is thrown.
• Encryption Errors: If encryption or decryption fails (e.g., due to invalid encryption key), the node reports detailed errors about encryption issues.
• Note Not Found: If the note ID does not exist or is marked deleted, the node returns a "Note not found" error.
• Supabase Errors: Any backend errors from the Supabase service are surfaced with their messages.

To resolve these issues:

• Ensure all required credentials are correctly configured.
• Provide valid Note ID and at least one update field.
• Verify the encryption key matches the one used to encrypt existing notes.
• Confirm the note exists and is not deleted before attempting update.

Links and References

• Supabase Documentation
• AES Encryption with CryptoJS
• n8n Node Development Guide