Note → Create
AI-generatedOverview
This node integrates with a Fleeting Notes service to create and manage notes securely. It allows users to create, retrieve, update, delete, and search notes stored in a remote database. The node supports encryption of note titles and content using a provided encryption key, ensuring privacy and security of sensitive information.
A common use case is automating note-taking workflows where notes need to be programmatically created or updated based on triggers or other data sources. For example, automatically creating meeting notes from calendar events or updating project notes when tasks change status.
Specifically for the Create Note operation, the node creates a new note with a unique ID, title, and content, storing it securely in the backend. This is useful for capturing quick notes or logs during an automation process.
Properties
| Name | Meaning |
|---|---|
| Title | The title of the note to be created. |
| Content | The main content/body of the note. Supports multiline text input. |
Output
The output is an array of JSON objects representing the created note(s). Each note object contains fields such as:
id: Unique identifier of the note (UUID).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 (false for newly created notes)._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 the provided encryption key, the node encrypts the title and content before saving and decrypts them when returning data.
No binary data output is produced by this node.
Dependencies
- Requires an API key credential with email, password, and optionally an encryption key for secure access.
- 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 the email or password credentials are missing, the node will throw an error "Missing required credentials". Ensure that valid credentials are set up in n8n.
- Authentication Failure: Errors like "Authentication failed" indicate invalid login details or connectivity issues with the backend service.
- Empty Title: Creating a note with an empty title will cause an error "Title cannot be empty". Always provide a non-empty title.
- Encryption Errors: If encryption or decryption fails, errors like "Failed to encrypt note" or "Failed to decrypt note" may appear. Verify that the encryption key is correct and consistent.
- Backend Errors: Errors returned from the Supabase service (e.g., "Failed to create note") usually indicate issues with the database or network.
- Node Operation Errors: The node throws descriptive errors for invalid inputs or failed operations; enabling "Continue On Fail" can help handle these gracefully in workflows.