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 is designed to interact with a Supabase Vector Store, providing extended support for database schema selection and document namespaces. It supports operations such as loading, inserting, retrieving, and updating documents in the vector store. However, based on the current implementation, none of these operations are yet implemented; the node returns placeholder messages indicating this.

In practical scenarios, once fully implemented, this node would be beneficial for managing vectorized document data stored in Supabase, especially when working with multiple schemas or logical partitions (namespaces). For example, it could be used to insert new documents into a specific table within a chosen schema, retrieve similar documents based on vector similarity, or update existing entries while respecting namespace boundaries.

Properties

Name Meaning
Use Custom Schema Whether to use a database schema different from the default "public" schema
Schema Name of database schema to use for table (shown only if "Use Custom Schema" is true)
Table Name Name of the table in your Supabase database
Namespace Logical partition for documents; uses a separate namespace column for filtering
Options Collection of additional options:
- Query Name Name of the query to use for matching documents (default: "match_documents")
- Clear Namespace Whether to clear the namespace before inserting new data (only available in Insert operation)

Output

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

  • operation: The name of the operation attempted (load, insert, retrieve, or update).
  • message: A placeholder message indicating that the operation is not yet implemented.
  • itemIndex: The index of the input item being processed.

No actual data manipulation or retrieval occurs currently. There is no binary output.

Example output JSON for an insert operation:

{
  "operation": "insert",
  "message": "Insert operation not yet implemented",
  "itemIndex": 0
}

Dependencies

  • Requires a Supabase API key credential configured in n8n to authenticate requests.
  • No external libraries beyond those bundled with n8n workflow environment are explicitly required.
  • The node expects access to a Supabase database with vector store capabilities.

Troubleshooting

  • Unsupported Operation Error: If an unsupported operation is specified, the node throws an error stating the operation is not supported. Ensure the operation parameter is one of: load, insert, retrieve, update.
  • Not Implemented Messages: Currently, all operations return a "not yet implemented" message. This indicates the node's core logic is incomplete and cannot perform real data operations yet.
  • Credential Issues: Failure to provide valid Supabase API credentials will prevent any interaction with the database.
  • Schema and Table Name: Providing incorrect schema or table names may cause errors once implemented. Verify these values correspond to your Supabase setup.

Links and References

Note: This summary is based solely on static analysis of the provided source code and property definitions. The node’s execute method currently contains placeholder implementations without functional logic.

Discussion