File API - bubbles incomplete

[rowntreerob]

Review -

API connector - Post.body as a binary file

JS Fetch.Post binary body is a standard way of pushing a binary file around in the context of APIs where the browser and using a “form” do not apply. getting the file as a blob/ArrayBuffer from the storage layer should be a requirement sending the above blob/ArrayBuffer as the body of a POST should be a requirement re - Sending file via API connector - #9 by aaronsheldon implement the equivalent of curl -X POST --data-binary @filePath

POST to API using binary

I’m working with an API that requires file data to be sent as binary. I have tried using the file converter plugin to convert to binary and then the API Connector plugin to sent but can’t figure out how to send it to the API as a POST properly as I continually get an error. I’ve attached below how I have it set up in Bubble. [18%20AM] [05%20AM][31%20AM]

More Generally
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

[jeffdbl]

Hi @rowntreerob, just came across this post as I was trying to figure out how to pass binary files via API to both Wordpress (image in a post), and Vimeo (setting a video thumbnail).

Are there any workarounds you can suggest, provided Bubble has not updated this?

[rowntreerob]

bubble has revise the filemanager in a way that using bubble as an intermediate hop for files you can get a bubble based S3 URI that can be used in a proxy service to call the 2 api’s you mention.

If you leave aside WP for a minute taking a look here on AWS from/to proxy it should be clear that w minimal changes the proxy handles any Fetch.POST based REST api ( expects file in the request.body as a binary and readableStream format).

read here and respond if you think that adding an endpoint for WP uploads makes sense.

Parse-Server has REST upload very similar to WP and the code for that is already in the proxy
see here code

If you want a UX where user form is on a page and the user rather than your system is selecting the file having destination TO: wordpress then that would change things a bit but if you can figure out how to get the file to the bubble.S3 layer as a binary then this all works with minimal changes.