Supabase Vector Store Extended icon

Supabase Vector Store Extended

Work with your data in Supabase Vector Store with Schema and Namespace support

Actions4

Update

AI-generated

Overview

This node, named "Supabase Vector Store Extended," is designed to interact with a Supabase vector store database, supporting operations such as loading, inserting, retrieving, and updating documents. It extends basic functionality by allowing users to specify a custom database schema and use namespaces for logical partitioning of documents.

The Update operation (the focus here) is intended to update documents in the vector store. Although the actual update logic is not implemented in the provided source code, the node structure suggests it would allow updating existing entries within a specified table, optionally filtered or organized by namespace and schema.

Practical scenarios where this node is beneficial:

  • Managing vectorized document stores for semantic search or machine learning applications.
  • Updating metadata or vector embeddings of documents stored in Supabase.
  • Organizing documents into namespaces for multi-tenant or segmented data access.
  • Using custom database schemas to separate environments or datasets within the same Supabase instance.

Properties

Name Meaning
Use Custom Schema Boolean flag to decide whether to use a non-default database schema instead of "public".
Schema The name of the database schema to use if "Use Custom Schema" is enabled. Defaults to "public".
Table Name The name of the table in the Supabase database where documents are stored or updated. Required.
Namespace A string representing a logical partition for documents; used for filtering via a namespace column.
Options Collection of additional options:
- Query Name Name of the query to use for matching documents. Default is "match_documents".
- Clear Namespace Boolean option indicating whether to clear the namespace before inserting new data (only present in some contexts).

Output

The output JSON object for the Update operation currently contains placeholder fields:

{
  "operation": "update",
  "message": "Update operation not yet implemented",
  "itemIndex": <index_of_input_item>
}
  • operation: Indicates the operation performed ("update").
  • message: Status message indicating the operation is not implemented.
  • itemIndex: Index of the input item processed.

No binary data output is defined or expected based on the current implementation.

Dependencies

  • Requires a valid connection to a Supabase database with appropriate API credentials.
  • Needs an API key credential configured in n8n for authenticating with Supabase.
  • The node depends on the Supabase client library (implied but not explicitly shown).
  • No other external services or environment variables are indicated.

Troubleshooting

  • Common issues:

    • Attempting to run the Update operation will not perform any real update since the logic is not implemented; users will only receive a placeholder message.
    • Misconfiguration of the table name or schema may lead to errors once the operation is implemented.
    • Incorrect or missing API credentials will prevent connection to Supabase.

  • Error messages:

    • "The operation \"<operation>\" is not supported!" — This error occurs if an unsupported operation is selected.
    • Other runtime errors related to connectivity or permissions would depend on the underlying Supabase client behavior (not shown here).

  • Resolution tips:

    • Ensure all required properties (especially Table Name) are correctly set.
    • Verify that the API key credential is properly configured in n8n.
    • Wait for future updates of the node to have full support for the Update operation.

Links and References

Discussion