In many cases I have to create images in code steps and since I can only pass JSON to other steps I can only pass the base64 string..It would be nice to add to formatter a base 64 to fuel converter so that after the image can be used as a file object for example for upload in Google with the provided step.
At the moment the workaround is to upload by myself using the API of Google in the code step and then download the file. But it is not ideal.
+11Hi and welcome to the Community
Thanks for sharing this idea, I've submitted it to our Product team for consideration. Can't give an ETA, but I'll be sure to follow up here if it gets added.
Glad you've already got a workaround going with the API call to Google in your Code step. For anyone else who comes across this thread and wants to set up something similar, we've got a guide that might be helpful:
Worth flagging the size ceiling for anyone copying this pattern. Code step output is capped, and a full resolution PNG as base64 goes past it fast, so the step can look like it succeeded while the string arrives truncated, and the failure only shows up later at the upload, where it looks like an unrelated problem.
If the image is being generated anyway, having the generator write to storage and passing the URL through the Zap tends to be the sturdier shape, since nearly every file field downstream accepts a URL and you stop moving the payload through the Zap at all.
The converter would still be a nice addition for the small stuff, icons and thumbnails where the string is short enough to be safe.
Join us September 23rd, 2026 for a free, one-day virtual event with 30+ sessions on AI automation. Get live build-alongs, playbooks, and strategies to lead AI transformation at your organization.
No account yet? Create an account
Enter your E-mail address. We'll send you an e-mail with instructions to reset your password.
