In a few of my workflows I have a Google Trigger node set to “trigger upon a file created”.
I have it set like this, but a lot of times it fires when I do not use it/not upload anything. At most random times.
It is my personal Google Drive and it is only me that has access to it.
Any ideas? I tried updating n8n, but the problem persists
When you set it to check for newly created files, the trigger node periodically (by default, every minute) sends a request to Google Drive to check for any new files that match your criteria.
Google does not send events to n8n for this trigger; instead, n8n is responsible for regularly checking (polling) Google Drive for changes.
Okay, but why does it trigger with error randomly if no new files are created?
Maybe of “ghost” runners…
Happens sometimes when you have copied the node/workflow multiple times in different executions.
I suggest to restart instance.
