I copied Cole’s Ultimate n8n RAG AI Agent and set it up using my Postgres account. I’m running n8n in a Docker Container on UNraid, and I am also running Postgres in a Docker Container locally as well.
When testing the n8n workflow, I couldn’t get the Local File monitor to work. Not sure if it is an issue with the Docker containers or the wrong file path, but I couldn’t get the trigger working.
I figured it might be easier just to use a Google Drive trigger instead so I set that up. But here is the problem. Even though I activated the workflow, it doesn’t seem to pickup when I add a file to my Google Drive. I can test the trigger manually, and it will test one file, but I don’t know how to get it to do it for all the files.
Does anyone know why the Google Drive trigger might not be working? Is there something else I need to do other than just activating the workflow?
P.S. Thank you Cole for creating such an advanced RAG agent. I have been experience all the RAG pain you talk about and have tired numerous times to get a accurate RAG agent. You are leading the way on AI, keep it up!
2 Likes
Hey Doug, I really appreciate the kind words!
Sorry the local file trigger isn’t working for you, are you on a Mac by chance? I believe there is a glitch that the n8n team needs to work on where Mac + Docker + n8n doesn’t work well for detecting local file changes.
Then for Google Drive, if you run the test it does pick up the latest new/updated file in Google Drive? Make sure your workflow is toggled to active for it to automatically pick up files!
It’s running in Docker on my UNRaid server (which is a variant of Ubuntu Linux).
I just tried it all again. I have 19 txt files that I converted mainly to Markdown format in My Google Drive n8n folder (but they are all .txt files). it still didn’t pick up the files when I added them even though my workflow is Active. When I click test, it pulled in the first file and went through the flow successfully. But it appears to be stuck on the loop over items. It is trying, but for some strange reason it shows item 2 of 2 is 8968 items. I confirmed, the google drive folder only has 19 files in it.
Any suggestions or ideas on how I can troubleshoot?
This is wild, especially that massive number in the loop node. To be honest, this seems like a bug worth reporting to n8n - the Google Drive trigger is 100% set up right if a test can pull a single file.
Here’s a trick that may work, at least it did for me when mine got stuck. Move all of the files, at least the ones that are not yet inserted into the DB. Add a brand new file to the directory and run the workflow/confirm that it’s picking it up. If successful, rename all the other files (append a number or something) and move them back into the directory.
Hope this helps!
1 Like
I appreciate you sharing this!!
