TL;DR: My n8n Supabase Vector Store node is querying a different table than the one I configured it to use. Looking for help debugging this behavior. Hey folks, I’ve run into a bizarre issue with the Supabase Vector Store node in n8n that I’m hoping someone can help me understand. The Problem: I’…

Hey @Maxime_Prn Welcome to the community :wave: One idea would be to check the contents of the SQL function match_documents which is what the Supabase vector store tool calls by default. If you’ve followed the Supabase Langchain quickstart , you can see this match_documents function has the table …

Let me know if you ever find a solution. Will post here if I do on my side.

Right on point! My match_document function was defined as follow: SELECT id, content, metadata, 1 - (embedding <=> query_embedding) AS similarity FROM vector_embeddings ORDER BY embedding <=> query_embedding LIMIT match_count; That’s why it was only looking through my “vector_embe…

Strange Supabase Vector Store behavior in n8n: Queries the wrong table despite correct configuration

Questions

Tommy_dr April 18, 2025, 7:31pm 2

I’m seeing the exact same issue.

My Vector Store node is set to a specific table, but the results are clearly coming from a different one.

Supabase Vector Store queries the wrong table despite correct configuration

Topic		Replies	Views
Supabase Vector Store queries the wrong table despite correct configuration Questions supabase	3	179	December 5, 2025
Problem using multiple Supabase Vector Stores in one n8n project — always retrieves data from the first table Questions supabase	0	68	October 28, 2025
Supabase Vector Store Issue Questions langchain	3	4914	January 24, 2024
Supabase Vector Store node returns empty output (no error) while SQL query returns matches Questions supabase , rag	8	130	February 24, 2026
Ai agent and Supabase Vector Store have issue Questions	2	129	August 14, 2025

Strange Supabase Vector Store behavior in n8n: Queries the wrong table despite correct configuration

Related topics