Supabase Vector Store node

Use the Supabase Vector Store to interact with your Supabase database as vector store. You can insert documents into a vector database, get many documents from a vector database, and retrieve documents to provide them to a retriever connected to a chain.

Use the Supabase Vector Store to interact with your Supabase database as vector store. You can insert documents into a vector database, get documents from a vector database, retrieve documents to provide them to a retriever connected to a chain, or connect it directly to an agent to use as a tool. You can also update an item in a vector store by its ID.

On this page, you'll find the node parameters for the Supabase node, and links to more resources.

Supabase provides a quickstart for setting up your vector store (opens in a new tab). If you use settings other than the defaults in the quickstart, this may affect parameter settings in n8n. Make sure you understand what you're doing.

Node usage patterns

You can use the Supabase Vector Store node in the following patterns.

Use as a regular node to insert, update, and retrieve documents

You can use the Supabase Vector Store as a regular node to insert, update, or get documents. This pattern places the Supabase Vector Store in the regular connection flow without using an agent.

You can see an example of this in scenario 1 of this template (opens in a new tab).

Connect directly to an AI agent as a tool

You can connect the Supabase Vector Store node directly to the tool connector of an AI agent to use a vector store as a resource when answering queries.

Here, the connection would be: AI agent (tools connector) -> Supabase Vector Store node.

Use a retriever to fetch documents

You can use the Vector Store Retriever node with the Supabase Vector Store node to fetch documents from the Supabase Vector Store node. This is often used with the Question and Answer Chain node to fetch documents from the vector store that match the given chat input.

An example of the connection flow (opens in a new tab) (the example uses Pinecone, but the pattern in the same) would be: Question and Answer Chain (Retriever connector) -> Vector Store Retriever (Vector Store connector) -> Supabase Vector Store.

Use the Vector Store Question Answer Tool to answer questions

Another pattern uses the Vector Store Question Answer Tool to summarize results and answer questions from the Supabase Vector Store node. Rather than connecting the Supabase Vector Store directly as a tool, this pattern uses a tool specifically designed to summarizes data in the vector store.

The connections flow (opens in a new tab) in this case would look like this: AI agent (tools connector) -> Vector Store Question Answer Tool (Vector Store connector) -> Supabase Vector store.

Node parameters

Operation Mode

Rerank Results

Get Many parameters

• Table Name: Enter the Supabase table to use.
• Prompt: Enter the search query.
• Limit: Enter how many results to retrieve from the vector store. For example, set this to 10 to get the ten best results.

Insert Documents parameters

• Table Name: Enter the Supabase table to use.

Retrieve Documents (As Vector Store for Chain/Tool) parameters

• Table Name: Enter the Supabase table to use.

Retrieve Documents (As Tool for AI Agent) parameters

• Name: The name of the vector store.
• Description: Explain to the LLM what this tool does. A good, specific description allows LLMs to produce expected results more often.
• Table Name: Enter the Supabase table to use.
• Limit: Enter how many results to retrieve from the vector store. For example, set this to 10 to get the ten best results.

Update Documents

• Table Name: Enter the Supabase table to use.
• ID: The ID of an embedding entry.

Parameters for Update Documents

• ID

Node options

Query Name

The name of the matching function you set up in Supabase. If you follow the Supabase quickstart (opens in a new tab), this will be match_documents.

Metadata Filter

Related resources

Refer to LangChain's Supabase documentation (opens in a new tab) for more information about the service.