I tried a few different ways (e. g. with encoding the result to base64), but nothing worked. Direct input of the returned binary to the Cloudinary step lead to a time-out. Sidenote: should such a thing be possible or is it bad practice anyway?
Saving the image to tmp and using it from there to upload to Cloudinary gives the following error right now:
But the saving to tmp worked alright. I could get it from there to encode it in another step to base64, which I also tried once if it changed anything. It didn’t.
When I save the binary I received in Pipedream to my Mac, the resulting file can’t be opened as an image. When I compare the binary to the original image, it looks different. I know nothing about encoding, but could this be an issue or is the file getting corrupted on the way?
Left is returned binary in Pipedream, right is the source image downloaded from Akeneo:
The thing is that the binary is the source of the Base64 encoded string. So if the source file is already faulty, the Base64 won’t work as well. And to me it seems that way.
Could you maybe give me some insights to how exactly it has been used successfully by other users? Does that mean the Cloudinary connector?
I see. The successful case is the user uses base64 to save to file. Not specifically for Cloudinary
What happen when you reference the image binary data to Cloudinary’s File prop?
So it would be something like File: {{ steps.akeneo_get_asset_file.$return_value }}
The argument 'path' must be a string or Uint8Array without null bytes. Received '����\x00\x10JFIF\x00\x01\x01\x01\x01,\x01,\x00\x00��\x00\x18Exif\x00\x00II*\x00\b\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00��...
Then I think your previous step might be a problem. Could you check the API Doc from akeneo to see how to handle their response? Maybe you need to change the Content-Type or Accept header? Or maybe you might need to use Pipedream code action instead of the HTTP action to do some customization of the response?
I think this support is more on the usecase side. So if you have the Team plan, you’ll be invited to a dedicated support channel. Or if you’d like to hire a Pipedream expert for your usecase, feel free to use this link: Connect with a Pipedream Partner
If I am just putting in the URL of the API in this type of step, the authentification part is missing. So there won’t be a result.
No, I don’t have a team plan. I am just trying use cases we could present to our (potential) customers. But I heard that Akeneo (I work there) is thinking about a partnership with Pipedream. So maybe I have to wait until this is settled and we have a base to discuss this properly.