Is the cutting off of “http:” intentional? (because of different http/https use cases?) I didn’t notice for awhile because I was using these image paths locally, but they of course broke when I inserted them into email HTML and also for zapier zaps (triggered from Bubble, transferring a file using the filepath).
in Bubble’s Zapier action workflow:
Just wondering if this is an easy fix (or isn’t a bug at all), or if I should invest time to create workflows to generate the right filepath. For the zapier workflow especially, I’m unable to merely put the string “http:” in front of dynamic data, as the field only takes one input.
EDIT: or, perhaps we don’t need http: or https:, but need the URL to merely start with s3.amazonaws.com/etc … either way, right now :URL is asking us to do some manual reformatting!