Pretty sure when you upload a file you have to include its MimeType. I can see you’re MimeType is wrong when you’re file is Uploaded. It should be “text/plain”.
Thanks for your reply.
Yeah, I tried to upload the file with Content-Type as text/plain, but the result was the same as when I set it as application/json.
Use “Content-type: application/json” in your header like you were doing, use JSON as data type.
Use RAW body type.
In properties that have been created below:
Add your mimeType “text/plain” value.
Add your folderID “drive folder ID” value.
Add your fileName “output drive file name” value.
I believe we want to use Raw-form data, so we can still send a file with the payload. Rather than just the body. Cause that’s what’s missing. There is no file.
Thank you for the reply.
So are you saying that I should send the file using “Form-data” at the same time I send the code I just sent in the body type “Raw”? (Is that what you mean by “Raw-form”?)
If so, how should I use two body type in ONE API call?
I am a beginner, so I would appreciate it if you could let me know.
Thanks.
I this thread is helpful as are some others but there are no definitive solutions to this issue… I am also still struggling to get Google Drive to recognise the file type and include a name for the file… anyone else have insights to this… it is doing my head in and the Google Developer manuals are not that useful to an API novice
DId anyone ever come up with a solution to this? I have tried multipart and media and they both show up as untitled in Google drive just as the OP said. May Google OAuth is working fine, but uploading files to Drive has proved elusive.
Ultimately, what I would like to do is upload a file with the file name that the user sets in Bubble… so I guess that means multipart OR doing it in two API calls. I am open to either at this point.
