A large capability gap exists in bubble’s features for passing files among modules/ apps in particular in response to events requiring standard file transfer in the absence of user’s choosing files and filling out HTML form dialogs.
For example a collaborating app needs to send my-bubbl-app files ( mp3’s say ) whenever they experience a threshold (likes go gold). No user involved , just a state change in a collaborating app where that app will respond with a POST to and Endpoint on bubble w an MP3 file in the POST.body.
To support this, 2 things from bubble are necessary ;
Host api routes handler for binary file POST action on https
Endpoint/Workflow → Data layer update to store file while also supporting
– get file as buffered data
– get usual attr values for size, mimetype, name, uri
Above from Mime-Multpart RFC … All of current bubble functions re files are closely tied to the rfc and to multipart form functionality, needlessly dragging in front-end form protocol.
As noted here bubble’s file handlers default to forms based practices. Please note the RFC on mime multipart and the importance /relevance to the presence of users, web pages and html forms to the spec. By relying solely on MMF to the exclusion of all the app-to-app file exchanges like ETL bubble is missing out
Get some engineers on better support for web file apis