Fleeting Notes icon

Fleeting Notes

Create and manage Fleeting Notes

Actions5

Overview

This node allows users to manage "Fleeting Notes" stored in a Supabase backend. Specifically, the Delete Note operation marks a note as deleted by setting its deleted flag to true and updating its modification timestamp. This soft-delete approach keeps the note data but excludes it from active queries.

Common scenarios for this node include:

  • Automating cleanup of notes that are no longer needed.
  • Integrating with workflows where notes are created, updated, and eventually removed.
  • Managing personal or team notes programmatically within n8n workflows.

Example use case: After processing a note's content elsewhere in your workflow, you can delete the note automatically to keep your notes database tidy.

Properties

Name Meaning
Note ID The unique identifier of the note to delete

Output

The output JSON contains a simple confirmation object indicating success and the ID of the deleted note:

{
  "success": true,
  "id": "note-id-string"
}

No binary data is output by this operation.

Dependencies

  • Requires connection to a Supabase backend service.
  • Needs credentials including an email, password, and optionally an encryption key for note content.
  • The node uses an API key credential to authenticate with Supabase.
  • Encryption/decryption of note content is supported if an encryption key is provided.

Troubleshooting

  • Missing required credentials: The node requires valid email and password credentials to authenticate with Supabase. Ensure these are configured correctly.
  • Note ID cannot be empty: The Note ID property must be provided and non-empty; otherwise, the node will throw an error.
  • Authentication failed: If the email or password is incorrect, authentication will fail. Verify credentials.
  • Failed to update note: If the note ID does not exist or is already deleted, the node may throw a "Note not found" error.
  • Supabase client initialization errors: Network issues or invalid API keys can cause failures when connecting to Supabase.

To resolve errors:

  • Double-check all input parameters.
  • Confirm credentials and API keys are correct.
  • Make sure the note ID exists and is not already deleted.

Links and References

Discussion