I have the same problem. The external service we use requires parameter based retrieval of a file using an id:
GET https://external-service/v1/file/[fileId]/content
When using the file option on the API Connector all files retrieved are saved in S3 with the name “content”. This name is unsuitable for our customers and users for several reasons.
We have the actual filename for each file id, but we can’t figure out how to tell Bubble the name to use when saving the file to S3.
@lottemint.md It sounds like your recommendation is:
- Expose a new public endpoint
- Have the app send it to itself over the network encoding and decoding to base64 as necessary (using a Bearer token to make sure the app knows that the requests are coming from itself)
While I can imagine that this might work, it’s rather hard for me to imagine this would be the recommended way for choosing a file name or for renaming an existing file for that matter. I’m hopeful there’s a more pragmatic solution that I’ve overlooked in the manual or reference or that can be found here in these forums.
I would be very grateful for any alternative suggestions!