Hi,
I am using ‘ a new file in folder’ zap to trigger a new file in Google Drive. I am passing file name and file link to an API workflow in bubble.io
When this zap is triggered automatically, I get the following error
But when I run the same zap step by step, It is working fine.
What could be the issue here?
Best answer by Ram RP
Hi
Jumping in here to see if I can help! Based off the initial error screenshot you provided, and matching up to the Filename field, I noticed that what is populating in Title indicates an actual file.
Do you know if on the backend of things, Title is populated with an actual file and not simply the name of said file? Does this make sense? Let me know if you’d like me to rephrase!
Hey, It started working all of a sudden again.
I did not do any changes. It is file name and not the actual file.
Thanks for all the help!!
+11Hi
Hmm, that error seems to be suggesting that the file name field received a file object instead of the name. As this error is only occurring when the Zap is running, I wonder if there’s an issue with the selected fields.
Could you please share a screenshot of the fields that have been selected within the Action section in the step of the Zap that’s running into this error? Please remove/hide any private information from it first (like names, email addresses etc.). This will help us to better see if there’s anything in the set up of that action step that might be causing this error.
Looking forward to hearing from you!
Hi
Hmm, that error seems to be suggesting that the file name field received a file object instead of the name. As this error is only occurring when the Zap is running, I wonder if there’s an issue with the selected fields.
Could you please share a screenshot of the fields that have been selected within the Action section in the step of the Zap that’s running into this error? Please remove/hide any private information from it first (like names, email addresses etc.). This will help us to better see if there’s anything int he set up of that action step that might be causing this error.
Looking forward to hearing from you!
This is the action setup of the details I am passing to bubble
+8Hi
Jumping in here to see if I can help! Based off the initial error screenshot you provided, and matching up to the Filename field, I noticed that what is populating in Title indicates an actual file.
Do you know if on the backend of things, Title is populated with an actual file and not simply the name of said file? Does this make sense? Let me know if you’d like me to rephrase!
Hi
Jumping in here to see if I can help! Based off the initial error screenshot you provided, and matching up to the Filename field, I noticed that what is populating in Title indicates an actual file.
Do you know if on the backend of things, Title is populated with an actual file and not simply the name of said file? Does this make sense? Let me know if you’d like me to rephrase!
Hey, It started working all of a sudden again.
I did not do any changes. It is file name and not the actual file.
Thanks for all the help!!
+6Hi
That's great news! We're really happy to hear that everything is sorted out now.
If you happen to encounter the same issue in the future, feel free to reach out to us without any hesitation. We’re always happy to help! 😊
Enter your E-mail address. We'll send you an e-mail with instructions to reset your password.
