Overview
This node integrates with a Fleeting Notes service to create and manage notes stored in a Supabase backend. It supports operations such as creating, deleting, retrieving, updating, and listing notes. The "Create" operation specifically allows users to add new notes with a title and content.
Common scenarios for this node include:
- Quickly saving textual information or ideas during workflows.
- Automating note-taking from other data sources or triggers.
- Managing personal or team notes programmatically within n8n.
For example, you could use this node to automatically create a note summarizing the results of a daily report or to capture user feedback collected via a form.
Properties
| Name | Meaning |
|---|---|
| Title | Title of the note (required) |
| Content | Content/body of the note (required) |
The "Title" is a string representing the note's heading, while "Content" is the main text of the note. Both fields are mandatory when creating a note.
Output
The node outputs an array of JSON objects, each representing a note record. For the "Create" operation, the output JSON includes:
id: Unique identifier of the created 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: Timestamp when the note was created.modified_at: Timestamp of the last modification.deleted: Boolean flag indicating if the note is deleted (should be false for newly created notes)._partition: User ID partitioning the note to the authenticated user.encrypted: Indicates whether the note's content is encrypted.
If an encryption key credential is set, the node encrypts the title and content before storing and decrypts them on output.
No binary data is output by this node.
Dependencies
- Requires connection to a Supabase backend service.
- Needs credentials including email, password, and optionally an encryption key for securing note contents.
- Uses the Supabase JavaScript client library for API interactions.
- Requires an API authentication token (email/password) configured in n8n credentials.
- Uses AES encryption/decryption for note content if an encryption key is provided.
Troubleshooting
- Authentication failed: Ensure that the provided email and password credentials are correct and have access to the Supabase project.
- Missing required credentials: The node requires valid credentials; verify they are properly configured.
- Title cannot be empty: When creating a note, the title must not be blank.
- Failed to encrypt/decrypt note: If using encryption, ensure the encryption key is correct and consistent.
- Note not found: Occurs when trying to get, update, or delete a note with an invalid or non-existent ID.
- Failed to create/update note: Could indicate issues with Supabase permissions or malformed input data.
To resolve errors, check credentials, input parameters, and network connectivity to the Supabase service.