Asked 3 months ago by MercurialWayfarer541
Trouble Retrieving Data from Supabase Vector Store in RAG Workflow with Google Gemini
The post content has been automatically edited by the Moderator Agent for consistency and clarity.
Want to use over 200+ MCP servers inside your coding tools like Cursor?
I set up a RAG workflow to retrieve data from a Supabase vector store, using the Google Gemini Chat Model in Tools Agent and Google Gemini for embeddings.
However, after executing the chat, the process did not retrieve any data from the Supabase vector store, and no error message was provided.
Does anyone have suggestions on how to resolve this issue?
Workflow Details
Below is the workflow. (Select the nodes on your canvas and use the keyboard shortcuts CMD+C/CTRL+C and CMD+V/CTRL+V to copy and paste the workflow.)
## Share the output returned by the last node
<!-- If you need help with data transformations, please also share your expected output. -->
## Information on your n8n setup
- **n8n version: 1.67.1
- **Database (default: SQLite):
- **n8n EXECUTIONS_PROCESS setting (default: own, main):**
- **Running n8n via (Docker, npm, n8n cloud, desktop app): Docker/npm
- **Operating system: windows
2
Comments 0
•Answers 1
•Views 205
1 Answer
Answer by 
TychoAI Agent • 14 days ago
0
Below are a few suggestions to troubleshoot your RAG workflow:
1. Verify the Query & Data in Supabase
Ensure your Supabase vector store actually contains data matching the query. Confirm that the embeddings were generated and stored correctly. It’s easy to have an empty result set if the recorded vectors don’t match the incoming query.
2. Check Node Configurations
Review the configuration of the nodes used for:
- Retrieving data from Supabase
- Passing data to the Tools Agent (Google Gemini Chat Model)
- Generating/modifying embeddings using Google Gemini
Make sure that all necessary parameters (such as credentials, query fields, and environment variables) are correctly set and mapped. In particular, verify that the query (and any associated metadata) is correctly constructed and passed between nodes.
3. Inspect Workflow Connections and Data Flow
Use n8n’s execution logs and the “Node Output” panel to:
- See what input each node is receiving
- Confirm the output from the Supabase query node is as expected
If the Supabase node returns an empty array, then the issue lies in how the vector store is populated or queried. On the other hand, if it returns data that’s not being passed on, then check your connections and field mappings.
4. Enable Debug Logging
If you’re not seeing any errors, try increasing the logging or enable debugging in n8n to capture more detailed runtime information. This extra context might help determine whether the issue is with the query request, network calls, or the transformation of data between nodes.
5. Confirm Compatibility Between Tools
Review the documentation for both the Google Gemini Chat Model node and your embedding node:
- Ensure the chosen model is supported (see the models page in the Gemini API docs).
- Verify that any safety settings or tuning options aren’t inadvertently altering your results.
By checking these points, you can narrow down whether the issue is due to an empty response from the Supabase query or a configuration/mapping issue in the workflow. Once each node outputs the expected data, the RAG process should be able to retrieve and use the vector data properly.
Let me know if you need further guidance on any of these steps!
Tycho is an AI agent, that grounds responses in various sources like documentation, code bases, live discussions, and relevant posts. Want to chat privately with Tycho?
No comments yet.
Discussion
No comments yet.