SupaBase could not retrieve document information.
When I connect my N8N to Supabase, the agent is able to find the document's name but could not retrieve the document content. Instead, it says it's unable to extract the file. Can anyone help?
12 Replies
I can help with that! It sounds like the issue is that N8N is only fetching the document metadata, not the actual file content usually because of missing public file access or incorrect Supabase storage URL. Are you using a signed URL or trying to read directly from the bucket?
hi thanks for helping! No, im not using a signed url or trying to read directly from the bucket? actually i dont have a bucket. but how come it worked perfectly yesterday
You probably want to provide more info on what Supabase call exactly you are making that is not working now. I see nothing in your first post the looks like Supabase stuff.
Document in supabase would tend to mean a file and you mention a pdf. Supabase does not have documents like Firebase as part of the DB nomenclature.
Thank you so much for replying.
The original file was PDF, but I extract the file to text and then import to Supabase. And this is the data looks like in my Supabase table. Basically I was extracting a washer manual PDF into tags and then importing to Supabase. Yesterday I was able to retrieve the information from the Supabase, but today it gives me the error. So, do you know what's wrong with it, and can you help me with that? Thank you so much!
Got it if it worked yesterday but not today, it’s likely your Supabase project credentials or table permissions changed. Did you recently modify your API keys or database policies?
I would check your API Gateway log in the dashboard for errors or for your request in general. You don't show any errors here so hard to know. If you are getting a successful select of the DB with no data or empty array then you are not meeting RLS most likely.
No, I didn't change any credentials or policies.
Thank you so much for the reply. I checked the log, and seems like this is the issue？What do you think?
logs showed no error
The first is just a security warning, not error, and not involved.
I'm guessing you are calling a postgres function match_documents to get the info with that rpc call.
You would need to debug that to see if it is not returning data you expect.
First you would look to see if it is returning empty data.
Then you have to figure out if that is a bug in your function code OR RLS not being met.
Thank you so much for the advice. I will try.
Actually, the information that I want to retrieve is actually from the Postgres function match_ memories, not match_documents. So, how do I change it?
I fixed the problem. Thank you so much!
I fixed the problem. Thank you for helping.