Overview
The "Fleeting Notes" node allows users to create, retrieve, update, delete, and list 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 workflows that require dynamic note management, such as updating meeting notes, task descriptions, or any textual data that needs versioning or editing.
For example, you might use this node to:
- Update the content of a project note after receiving new information.
- Change the title of a note to reflect its current status.
- Automate note updates based on external triggers or events.
Properties
| Name | Meaning |
|---|---|
| Note ID | The unique identifier of the note to update. |
| Update Fields | Collection of fields to update in the note. Options: |
| - Title: New title of the note. | |
| - Content: New content of the note (supports multi-line text). |
Output
The output is an array of JSON objects representing the updated note(s). Each object contains the note's properties including:
id: Unique identifier of the note.title: The updated title of the note (decrypted if encryption is enabled).content: The updated content of the note (decrypted if encryption is enabled).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-specific partition key (usually user ID).
If encryption is configured, the node automatically decrypts the title and content before outputting them.
No binary data is output by this node.
Dependencies
- Requires an API key credential with email, password, and optional encryption key for authentication.
- Connects to a Supabase backend service for storing and managing notes.
- Uses AES encryption/decryption for note content if an encryption key is provided.
- Requires n8n credentials setup for the Fleeting Notes API (email, password, encryption key).
Troubleshooting
- Missing Credentials: If email or password credentials are missing, the node will throw an error indicating required credentials are not set.
- Authentication Failed: Errors during login to the backend service will result in an authentication failure message.
- Note ID Empty: When updating, the Note ID must be provided; otherwise, an error is thrown.
- No Update Fields Provided: At least one field (title or content) must be specified for update; otherwise, an error occurs.
- Note Not Found: If the note ID does not exist or is marked deleted, the node throws a "Note not found" error.
- Encryption Errors: If encryption or decryption fails (e.g., due to invalid encryption key), the node reports a relevant error.
- General API Errors: Any other errors from the backend service are surfaced with their messages.
To resolve these issues:
- Ensure all required credentials are correctly configured.
- Verify the Note ID exists and is not deleted.
- Provide at least one field to update.
- Confirm the encryption key matches the one used to encrypt notes.