I’ve tried uploading via Header credentials and the result is the same, no correct file name is received.
in zoom dev forum i check i need to add flag -O for original name, but i don’t think it correct and i don’t know how to do that. )
NodeApiError: UNKNOWN ERROR - check the detailed error for more information
at Object.googleApiRequest (/usr/local/lib/node_modules/n8n/node_modules/n8n-nodes-base/dist/nodes/Google/YouTube/GenericFunctions.js:24:15)
at Object.execute (/usr/local/lib/node_modules/n8n/node_modules/n8n-nodes-base/dist/nodes/Google/YouTube/YouTube.node.js:587:84)
at Workflow.runNode (/usr/local/lib/node_modules/n8n/node_modules/n8n-workflow/dist/Workflow.js:659:28)
Information on your n8n setup
**n8n version:0.212.0 (and 0.210.2 too)
**Database you’re using (default: SQLite):Default
**Running n8n with the execution process: main
**Running n8n via [Docker, npm, n8n.cloud, desktop app]: Docker
i found a bug in https module (i don’t know how to get rid of that)
URL of download any Zoom record contains dots, for example
https:// us06web. zoom.us / rec / webhook_download / eR_gtb8uTs1PI9u41mpUuKhWXPY0FtFTyO1Xr_dsLssqcT-lmpVmhUE9sFDMS5cJWcbSJVJ82RPDZ3hE.bLLjupyNNgQ_bDrM/L3Xnkh6lVlSKP1fBJIoLOXA8mkAI805-vRheF8urxoOqdKUJrYrjuXlfjtpMtsE**.**qQZ98vYOWMJuXhHp
And original filename get after redirect (Follow Redirects checked).
BUT https module takes part of url as filename and extention, with example below showing as:
Hi @lightcom, I am sorry for the trouble with uploading larger files. I know @netroy is currently in the process of improving the support for working with larger binary data. Perhaps he can confirm if the YouTube node is on the respective roadmap here?
As for the download problem, perhaps you can check if the Zoom server returns a content-disposition header? This header is unfortunately ignored by n8n, but you could parse it as described here (and perhaps you might want to leave a vote on the respective feature request too, to bring n8n more in line with web standards):
Any chance you can share the JSON payload you are getting from Zoom? You can of course redact all confidential values, just not the content-disposition header value itself. I can then see if I can turn that value into a proper filename
Thanks @lightcom, got your message. It looks like the content-disposition header sent by zoom does not include an actual filename (which is why the logic would from the linked thread would fail). You can find an example of the header I was expecting at MIME - Wikipedia.
So I think you would need to set your file name using a different approach. I’ll respond to your message with a quick example using the topic name, but you can of course adjust this as needed (adding the start time etc. for example).
I am currently in the process of backing up all my Zoom recordings to Google Drive. Would you mind sharing your complete workflow with me? I’m interested in sharing it with others as a starting point, (n8n workflow templates)
I believe what you have set up would be an excellent foundation.
Could you please share your entire workflow staring form the HTTP call pulling all the recordings from the Zoom API?
Since I had 300 gigabytes in the cloud, I had to clear up to 15 gigabytes. I gathered a list of all the files, put the record data and download url into google sheets, then used ANT Downloader to download all the files. It would have taken much longer through the n8n.