Google Drive trigger keeps outputting the incorrect file id and name. I thought it might of been an issue with my workflow but I created a new workflow and tested just the “Google Drive Tigger - Changes to a specific file”, I changed the file type to ID and entered a google docs id. I tested the node and looked in the output table and it is showing a completely different id and doc name to what I wanted.
I’m running into the exact same issue! The google drive trigger, is retrieving a completely different file. This is critical and could lead to critical error even data breach! Sending the wrong files to the wrong people… I’m surprised it hasn’t been fixed by now. More details on my case: Hosted n8n (paid) , personal workflow –> google drive trigger –> trigger on changes to a specific file –> file by ID, URL, Name (none of them worked!!) –> The file retrieved is a different and random (I got different ones). The folder is a shared folder, so I suspect it’s taking the latest file modified in that folder BUT, I need it to be this exact same file. I have added a workaround to check the file id before continuing with the flow. However, given the popularity of n8n and the fact that more and more users less tech (like me) copy pasting workflows from tutorial online without testing… well I’m worried these type of errors go un noticed and without a fix for so long Please I hope I’m wrong and that is just me not doing this correctly!