I need my zap to find the project folder in the route of a drive..
but even though the project folder is right there in the top level of the drive, the ‘find folder’ zap instead finds an obscure folder buried deep in the project folder with a roughly similar name.
Presumably this is a bug.
Does anyone have a fix, or failing that, a decent workaround?
Thanks
Best answer by SamB
Hey folks, I’m happy to report that the feature request has been closed! 🎉
There’s now a Search Type field which will allow you to choose between Exact match or the more “fuzzy” Filename contains option:
The parent folder IS the Project drive - the text underneeath suggests leaving it blankmeans it will default to the top-level folder.. but that doesn’t seem to do any good unfortunately.
Could I add an id code for the drive here perhaps?
In order to add the drive as ‘parent folder’ I had to copy the drive id from the webGUI, go to custom, then paste it in (so not obvious it could even be done)
Needs further testing but I’m tentatively optimistic that’s cracked it!
At the moment the “Find Folder” action uses fuzzy search which finds matches that are approximately equal to a given search query, rather than exactly matching it.
However, we have an open feature request to improve the “Find Folder” search. Please let me know if you’d like to get added to that.
I have added you to the open feature request to improve the search when using the “Find Folder” action for Google Drive. We will keep you in the loop via email once the feature has been implemented.
Additionally, thank you for sharing the workaround here. This will be helpful to our Community members who might have the same issue.