Trigger doesn't work for new file in Google Drive (explorer vs web)

Questions
,
1

Describe the problem/error/question

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.

I recorded my screen doing this here: [Support] N8N - Google Drive Web vs Explorer - TechSmith Screencast - TechSmith Screencast

What is the error message (if any)?

No error, just never triggers

Please share your workflow

Share the output returned by the last node

Information on your n8n setup

  • n8n version: Current to the web at this time (1.77.3)
  • Database (default: SQLite): (default) - none used directly
  • n8n EXECUTIONS_PROCESS setting (default: own, main): Unknown, n8n cloud
  • Running n8n via (Docker, npm, n8n cloud, desktop app): n8n cloud
  • Operating system: Windows 10
2

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).

1 Like