Fleeting Notes icon

Fleeting Notes

Create and manage Fleeting Notes

Note → Delete

AI-generated

Overview

This node allows you 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 user-generated content with a reversible delete mechanism.

Example: You could use this node in a workflow triggered by a user action to delete a specific note by its ID, ensuring the note is no longer visible or accessible in subsequent operations.

Properties

Name Meaning
Note ID The unique identifier of the note to delete. Must be provided and non-empty.

Output

The output JSON object for the Delete operation contains:

  • success: A boolean indicating if the deletion was successful (true).
  • id: The ID of the note that was marked as deleted.

Example output:

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

No binary data is produced by this operation.

Dependencies

  • Requires an API key credential with email, password, and optionally an encryption key for authentication against a Supabase backend.
  • Uses the Supabase JavaScript client to interact with the database.
  • Encryption/decryption of note content and title is supported via AES if an encryption key is provided.
  • The node expects a Supabase project URL and anon key hardcoded internally (in this code snippet).

Troubleshooting

  • Missing credentials error: If the email or password credentials are missing, the node will throw an error. Ensure these are configured correctly.
  • Authentication failed: Occurs if the provided credentials are invalid. Verify the email and password.
  • Note ID cannot be empty: The delete operation requires a non-empty note ID. Provide a valid ID.
  • Failed to update note: Could indicate the note does not exist or is already deleted. Check the note ID correctness.
  • Supabase errors: Any errors returned from Supabase (e.g., network issues, permission denied) will be surfaced. Review the error message for details.

Links and References

Discussion