Weird Google Drive Folder Reader Trigger Issues

[mutty]

Hi guys,

I have a couple loops setup to trigger with Google Drive Folder Reader but nothing happens when a new file is added. However, a simple test worked fine.

The test loop only contains the trigger with an output. My main flows are more complicated.

Both triggers are wrapped in an if-else that simply checks for a non-empty file.

I’m going to try redoing the triggers but wanted to know if there could be anything else causing this.

@Wasay-Gumloop I’ve shared it with your address:

https://www.gumloop.com/pipeline?workbook_id=unTGB5XEDcYytaXoHmjBZ3

Thanks!

[Gumloop_Bot]

Hey @mutty! If you’re reporting an issue with a flow or an error in a run, please include the run link and make sure it’s shareable so we can take a look.

1. Find your run link on the history page. Format: https://www.gumloop.com/pipeline?run_id={your_run_id}&workbook_id={workbook_id}

2. Make it shareable by clicking “Share” → ‘Anyone with the link can view’ in the top-left corner of the flow screen.
   

3. Provide details about the issue—more context helps us troubleshoot faster.

You can find your run history here: https://www.gumloop.com/history

[Wasay-Gumloop]

Hey @mutty — just to confirm, are you checking the file-triggered runs on the Gumloop history page or the “Previous Runs” tab? And nothing is showing up when you upload a file to the folder?

Could you try the following steps:

1. Disable the trigger on the Drive node and save the workflow.
2. Once saved, you should see the trigger disappear from the top panel.
3. Delete the Drive node and re-add it from the node library.
4. Enable the trigger again and hit save.
5. You should now see the trigger reappear at the top.
6. Try uploading a file to the folder again to test if it fires.

Let me know if that works.

[mutty]

Yep, checked both of those and nothing was there. Just our manual runs. Will give this a go and report back!

Cheers