TL;DR: Has anyone sent files to Corteza via integration gateway before?
Hello, all!
I’ve a use case where a non-Corteza web app (owned & maintained) is integrating with a Corteza deployment (also owned & maintained) via an integration gateway. The external app remits a file (a couple of files, actually) to Corteza via the aforementioned I.G.
Currently, the external app is encoding the files’ contents to Base64 & then labeling it before transmission. From there, the workflow backing the I.G. does the conventional request.Body → Reader → JSON string → JSON object dance. Then, the workflow extracts the Base64 from the JSON to variables, one for each file. Those Base64 strings are then decoded, which I’m currently doing via my own JavaScript decoder in a jsenv block. After that, I’m not sure what to do with the decoded content.
To be clear, I’m not married to any of this logic. If there’s a “better” way, happy to do it! The integration is all back-channel/intranet connections (still using a secret key in a Header prefilter, just in case), so there’s no worry about bandwidth or obfuscation.
Does anyone have some insight into receiving and storing a file via integration gateway?