(I plan to submit a bug, but thought I’d post the question in the event anyone else was having this problem.)
I’m using a Workflow API to store attachments into an object in Bubble.
Here you can see the endpoint is expecting a value of type “attachment_file” which is of type “file”.
This file value will then be stored into the “Letters” table in Bubble.
The expected behavior is that this attachment should then be stored inside of the Letter object as a file. Instead, it is being stored as a reference to the Zapier file and not the attachment. (Unfortunately, we don’t have access to any log files to see exactly what Bubble is importing.)
Now I know that the object being sent to Bubble is actually a file. I am also sending the same object to Dropbox and it’s being stored as a file, too. The images above shows the dropbox URL which is correct and I can see the files in Dropbox. Bubble, however, is not storing a file. Also, as seen below, the file_url is not pointing to Bubble’s amazon S3 storage, instead it is pointing to Zapier’s temporary file store. So it lokks like the Bubble API workflow is storing the file URL instead of the actual file object, then also using the attachments URL instead of just uploading the file and using the amazon S3 url.
So I decided to test this out by first importing a file via the API and then updating it via Bubble. In that first image above you see the data table with the file URL pointing to Zapier. After uploading a new file (clicking on the file and uploading a new one in the edit menu). You can now see the Amazon S3 url.
This is incredibly important since the Zapier file reference is only temporary. The file has to be uploaded into Bubble for it to persist. Thanks.