Need Help Making Supabase Metadata Filter Work

[taxationistheft69]

Describe the problem/error/question

I’m using a Supabase Vector database to simply pull out 50 relevant search results that gets combined into a single string to be passed into DeepSeek which doesn’t have a built Tools functionality.

In the table that I’m actually trying to search the information with vector coordinates, there is a metadata->>[CATEGORY] that I’m trying to filter for BEFORE I get presented the 50 search results.

I can get Agentic RAG searches and filters through 3.7 Sonnet, buy asking for the filtering criteria connected through the Tools interface. We much prefer the writing style of the DeepSeek output.

What is the error message (if any)?

Every combination and test of the Metadata Filter in the Supabase node results in 0 outputs. I can run the queries fine using SQL editor directly in the Supabase web interface.

If I remove the values, I get the expected 50 results. Then when I try the metadata filter, I get 0 results, even when I start copying and pasting directly from the results when there was no filter enabled.

I’m trying to filter by the file_id in the metadata (jsonb) column.

Please share your workflow

Information on your n8n setup

• n8n version: 1.85.4
• Database (default: SQLite): Supabase Vector Database
• n8n EXECUTIONS_PROCESS setting (default: own, main): Default
• Running n8n via (Docker, npm, n8n cloud, desktop app): n8n Cloud
• Operating system: Windows

[octionic]

Looks like the value of the Name field of you filter contains a special character. Maybe try typing „—>“ manually.

[taxationistheft69]

I noticed that too. every time I entered → into the text field it seems to convert it into the symbol automatically?

I’m using Thorium. Is there someway for me to ensure it’s not converting it automatically?

[taxationistheft69]

metadata->>file_id

I just copied and pasted the Name field back to the above.

So perhaps it didn’t actually convert it to a symbol even though the screenshot appears as though it did?

[octionic]

Maybe you could try a different browser like Firefox just to see if it solves the issue.