Skip to main content

Get Support
Have a question? Let's get you an answer!

How Do I...? Troubleshooting Code & Webhooks Developer Zone

Other Help Resources
Wait, there's more! Check out these Community sourced spaces for additional resources.

Zapier Help Center Hire an Expert

Learning Resources
All of our best learning resources can be found here.

Featured Articles Show & Tell Zapier's products AI Hub Zapier Tools Hub

Share your knowledge
Give back to the Community by sharing your automation wins and helping to answer questions.

Share your success See unanswered questions User Groups

Other Learning Resources
Some of our favorite additional ways to upskill your Zapier knowledge.

Zapier Learn Zapier Blog Zapier Webinars

Product Updates
Check out what is new and upcoming with Zapier with our regular product updates.

Product Updates

Early Access Program
Want to join Early Access? Learn more here.

Question

Zap not triggering Google Drive -> Basecamp

  • March 24, 2023
  • 1 reply
  • 42 views
SrdjaNo1

Hi everyone.

I wanted to setup Zap so that anytime a file is uploaded in a specific Google Drive folder a Todo in a Basecamp is created.

Seems a pretty straightforward thing to do and tests pass and that initial todo is created but when I upload file in my Google Drive nothing happens. Even if I run it manually, it just says that it didn’t find new files.

I thought that it might be because of a dynamic name I wanted to create, so I used just a default name, “New Todo”, and it still doesn’t work.

Any help is appreciated.

This post has been closed for comments. Please create a new post if you need help or have a question about this topic.

1 reply

SamB
Community Manager
Forum|alt.badge.img+11
  • SamBCommunity Manager
  • Community Manager
  • March 24, 2023

Welcome to the Community @SrdjaNo1. So glad you could join us! 🙂

It sounds like the Zap isn’t “seeing” the new files that are being added into Google Drive so I wouldn’t have thought that the name of the Todo you’re creating in Basecamp would be the cause of the issue. I suspect the issue may lie with the file itself. 

I know the New File in Folder trigger can be bit selective on when it will trigger on certain types of files. For example if it’s a file that’s being directly uploaded into the folder then it should trigger. But if the file is uploaded and then moved into the folder then it won’t necessarily trigger (depends on the type of file and when it was last modified). You can learn more about this here: Not all my files are triggering my new file in folder Zap.

Is the folder one that you own, or is it one that has been shared with you? If it’s one that’s been shared then the Zap won’t ever trigger in which case you’d need to connect the Zap to a folder that you own in order for it to see the files that are being uploaded into it.

Hopefully that helps to get you pointed in the right direction. Please keep us updated on how you get on with this, keen to ensure you’re all set here! 

Terms & ConditionsAccessibility statement