Supabase Vector Store Extended icon

Supabase Vector Store Extended

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

Actions4

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 with additional support for custom database schemas and namespaces. However, based on the current implementation of the execute() method, none of these operations are actually implemented yet; instead, the node returns placeholder messages indicating that each operation is not yet available.

In practical scenarios, once fully implemented, this node would be beneficial for managing vectorized document data stored in Supabase, allowing users to organize data by schema and namespace, perform similarity searches, and maintain up-to-date document vectors. For example, it could be used in applications involving semantic search, recommendation systems, or AI-powered document retrieval where vector embeddings are stored in a Supabase database.

Properties

Name Meaning
Use Custom Schema Boolean flag to indicate whether to use a database schema other than the default "public" schema.
Schema The name of the database schema to use for the table (shown only if "Use Custom Schema" is true).
Table Name The name of the table in the Supabase database where vector data is stored.
Namespace A logical partition for documents, using a separate namespace column for filtering data.
Options Collection of options:
- Query Name Name of the query to use for matching documents (default: "match_documents").
- Clear Namespace Boolean option to clear the namespace before inserting new data (only available for insert operation).

Output

The node outputs JSON objects containing at least the following fields:

  • operation: The operation requested (e.g., "load").
  • message: A string indicating that the operation is not yet implemented.
  • itemIndex: The index of the input item being processed.

No actual data from Supabase or vector store operations is returned currently. There is no binary output.

Example output JSON snippet:

{
  "operation": "load",
  "message": "Load operation not yet implemented",
  "itemIndex": 0
}

Dependencies

  • Requires a Supabase API key credential configured in n8n to authenticate requests.
  • Depends on the Supabase service for storing and querying vector data.
  • No external libraries beyond those bundled with n8n workflow environment are explicitly required.

Troubleshooting

  • Since the core operations are not implemented, users will receive messages indicating this status.
  • Common error: If an unsupported operation is specified, the node throws an error stating the operation is not supported.
  • To resolve errors related to unsupported operations, ensure the operation parameter is set to one of the supported values ("load", "insert", "retrieve", "update").
  • Users should verify that the Supabase credentials are correctly configured to avoid authentication issues once operations are implemented.

Links and References

Discussion