Connector image input file - need the correct Type and File name

Product Suggestions
1

Hello
I don’t know how many people have been able to send image to external system with Connector function. But there is strong limitation with the Tulip feature: connector function, input image encoding as file: Connector input encoding control
1/ Content type:
The file is properly send but without the correct Type. The backend system received the file with a generic “Content-Type”: “application/octet-stream” instead of the correct one (ie: “Content-Type”: “image/jpeg” for jpeg image).
The result is that, in the external system, it is not possible to open the image send.

2/ File name:
The file name with his extension (like .jpeg) is not possible to send.

Today this feature is unusable, we always need an extra layer (Nodered or PowerAutomate) to pass properly an image to external system.

Example of use case, for lean/5S, we collect, with a Tulip apps, improvement/idea with sometime picture that end user take, we want to pass idea/topics with picture to Asana system for follow-up.

2

Hi @Nicolas ,
Thank you for the feedback! We know the limitation around file ingestion in connector functions. Improving how files are handled — both as inputs and outputs in connectors — is on our radar, and we’re working through the best way to deliver this. In the meantime, I encourage other community members to upvote this post as it helps us with prioritization of the work.

Best,
Cana

3

Thanks a lot for your quick feedback.

First priority for me is for image. As it is already an Input type “Image”, with encoding with “file”, pass in the POST API call the correct FileName and Content-Type will a huge improvement.