Thimo
1
Hi all!
I just published a plugin that allows you to upload multiple files at the same time by selecting them and/or by using drag and drop. You can see the current progress for each file, remove the file, remove files, clear/reset the uploader, and view metadata such as file name, file size, file URL, file type, etc.
Fully customize the uploading experience
Limit file types
Make files private
View upload progress & human readable errors
Demo page (editor is public): Better Multi File Uploader
Plugin page: Better Multi File Uploader Plugin | Bubble

Let me know if you have any questions, bug reports or feature requests!
2 Likes
Great plugin to design a nice uploading interface compared to the Bubble plugin.
But need a State for all uploaded completed is Yes to be useful.
use case is when all uploaded completed is yes, trigger workflow to process the uploaded files.
Thimo
3
Hi @phan.personal!
You could actually already do this as all the files have the “fileUploadComplete” status. So you can filter the list on "fileUploadComplete = no":count is 0 (you might also need to add a conditional to check if the file uploader is empty or not) to know if all files are done uploading.
Added an example to the demo page for you: Better Multi File Uploader
However, I am not sure if the logic you are describing would be the best UX as often with multi-file-uploaders users first upload for example 3 files and after that 2 more files. So in most cases you want to have a button the user can click to trigger the logic to process the uploaded files 
thanks @Thimo
didn’t know there’s a complete state for each file, playing around with that I can implement my use case, though a separate all uploaded complete state in workflow would be great.
Thimo
6
Ah, I can see that a workflow event would be nice to have! I just pushed a new version (1.1.0) that adds the “All Files Uploaded” workflow event:
Also updated the demo page! 
1 Like
that’s quick,
Here’s another one for you.
the url got an extra https:https://
Thimo
8
Ah interesting. Thanks for flagging! I should have fixed this in version 1.1.1. I added additional logic to check if “https://” is already present and if so to not append “https:”. Hope this fixes your issue 
1 Like