Overview
This node integrates with a Fleeting Notes service to manage notes stored remotely. It supports operations such as creating, retrieving, updating, deleting, and listing notes. The node authenticates using user credentials and optionally encrypts note content for security.
A common use case is automating note management workflows, such as:
- Creating new notes from form submissions or other triggers.
- Retrieving specific notes by ID for display or processing.
- Updating existing notes with new information.
- Deleting notes without permanently removing them (soft delete).
- Fetching multiple notes with pagination support.
For example, you could use this node to automatically archive meeting notes created in another system or to fetch notes for review in a dashboard.
Properties
| Name | Meaning |
|---|---|
| Note ID | The unique identifier of the note to get, update, or delete. |
Output
The node outputs JSON objects representing notes with the following structure:
id: Unique identifier of the note.title: Title of the note (decrypted if encryption is enabled).content: 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 (soft delete)._partition: User ID partitioning the note to the authenticated user.encrypted: Boolean indicating whether the note's title and content are encrypted.
If encryption is enabled via an encryption key credential, the node transparently decrypts the title and content fields before outputting them.
No binary data output is produced 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 note storage and retrieval.
- Uses AES encryption/decryption for securing note content if an encryption key is provided.
- Requires n8n credentials configured with the necessary authentication details.
Troubleshooting
- Missing Credentials: If email or password credentials are missing, the node will throw an error "Missing required credentials".
- Authentication Failure: Errors during login to the backend service result in "Authentication failed" messages.
- Note Not Found: When fetching or updating a note by ID that does not exist or is deleted, the node throws "Note not found".
- Empty Note ID: Operations requiring a note ID will fail if the ID is empty.
- Encryption Errors: If encryption or decryption fails (e.g., due to an invalid encryption key), the node reports errors like "Failed to encrypt note" or "Failed to decrypt note".
- Update Validation: Update operations require at least one field to be provided; otherwise, an error is thrown.
- Soft Delete: Deletion marks notes as deleted but does not remove them permanently; ensure your workflow accounts for this.
To resolve these issues, verify credentials, provide valid note IDs, ensure encryption keys match those used to encrypt notes, and supply required input fields.