I found an API service that generates a QR code with a PNG output. Right now Tulip connector functions only output XML/JSON/Text. Any plans on expanding that?
Hey @jjj -
Totally, this is one of the first things we added to the roadmap when we added file support to app variables and tables. Supporting both input to, and output from, connectors for at least all supported file types is on the roadmap.
This gets a little tricky because different APIs expect files/images to be encoded in different ways, and we don’t necessarily know what every API ever expects, and this is into the technical weeds most of our customers don’t have experience with, so we need to be smart about how we enable the configuration of these inputs/outputs.
Pete
Hi @Pete_Hartnett @canaalpaslan
We have similare need.
For an important use case to implement, Tulip could be the solution for business.
We are in phase of technical feasability and solution recommendation.
In the usecase, we need to call an API that return an image, response of the API is Multipart.
Did you have visibility of this feature availability? It will help us to keep Tulip or not as prefered/recommanded solution.
Tulip still can’t load a multipart-image response into a variable. The feature is on the roadmap, but there’s no public date yet. You can see the current output limits here: How To Use Outputs from Connector Functions In Apps
Until it ships, you could try routing the call through a small proxy (AWS Lambda, Google Cloud Function, etc.). Have the proxy pull the multipart body apart and return either:
- a
data:image/...;base64,string (good up to about 250 kB) - or a time-limited HTTPS link to the file
In Tulip:
- Create an HTTP Connector with one Text output that calls the proxy.
- If you return a data URL, bind that text variable directly to an Image widget using “Data URL.”
- If you return a signed link, run Store File from URL in a Trigger, then display the stored file. Docs for that step are here: Upload a file
1 Like