I have Google Drive Desktop installed and running successfully. I can see the Google Drive files via my file explorer. I have a work flow that “should” monitor a specific folder in my Google Drive, and when there is a new file, trigger and do some processing (upload to my S3 bucket, on success, delete the file from Google, on failure, message me and stop).
If I add the file via explorer, the trigger never fires. If I add the file via an upload on the web interface, it runs. If I copy the file to the explorer windows, and trigger it via “test”, it works.
No one has any ideas how I can get the Google Drive Desktop app to “trigger” the workflow the same way the web interface does? Or is there a different method to accomplish this? Ideally, allowing me to trigger on a folder on my local machine (not my Google Drive).
It sounds like the file event isn’t being picked up when using Google Drive Desktop. One possibility is that changes made via the file explorer don’t trigger the same notifications as those made through the web interface, likely due to differences in how the two methods sync files.
One workaround might be to adjust your workflow to periodically poll the folder (say, every minute) instead of relying solely on real-time triggers.
This could help ensure that any new files added through the desktop app are caught.
Thanks for the reply @mohamed3nan – I guess I didn’t realize I could do both at the same time. I will investigate that, thanks. Would they be considered two triggers or there is something I would change on the existing trigger to add that polling?
Maybe you could try something like this: add another scheduled trigger that checks every 5 minutes(increase it to save the number of executions) for any file inside the folder, and if there is a file, it will output that and continue as normal.
Important: Note that I assumed the folder will always be empty. This is the logic behind the “Search file” node, which looks for any file in the folder.
