Forum Academy Marketplace Showcase Pricing Features

Make File Private using workflow

Hey Guys,

Does anyone know how to make the file private after it has been added to the database using the workflow? For example if I am saving a file to S3 how do I make that file private? Right now the private option is restricted to the file element editor settings

1 Like

The private setting has to be set at upload time, so it can’t be done in a workflow, since at that point you’re only using the URL to the file. It has already been uploaded.

Thanks for reply. I hate being the one that makes impossible scenarios, but here it goes.

A bit of background here on what I am trying to achieve. So you can guide me better. Below are the steps

  1. user adds private document (no problem here)
  2. Bubble API connector is triggered to send the document URL to cloudconvert.com for conversion (Since it’s a private document the API can’t access the document URL to initiate the download. And I can not use other options like base64 due to the size, and can not use binary as it’s not available. How can I bypass this issue)
  3. Cloudconvert.com returns converted document URL which can be downloaded by bubble and saved to the same entity in step 1 (issue here the converted document must be also private and since the workflow can not make the file private I don’t know what to do.)

I know this is quite complex but I need a proof of concept for an external client and since these are legal documents they have to remain private.

Your feedback is appreciated.

I’m afraid we don’t have a solution there in the short term. If the files are hosted in cloudconvert can they handle security?

I am afraid cloudconvert does no have file storage. They do hold converted documents for short amount of time.

I will try zapier. Do private documents rules effect zapier?

Also would this be something I can do on a sponsorship bases? Just exploring all options

There are a 2 features requests there, a way to access images that are private from external services and ability to save to S3 with privacy rules. We can talk about sponsorship if you want. Please reach out by email for this.

Could you re-upload the processed file when it gets returned? If it’s a new upload, you should be able to replace the file sent to cloudconvert and make it private. It’s a guess; I haven’t tried it.

Sent to support

Any updates about this? It there a way to make public files private using API workflows?

3 Likes

Were you able to find a way to make “:saved to S3” file private in the backend workflows?

The workaround I’ve used is to use the API connector to make an API call to the app.

And then delete the original file (workflow for that)

1 Like

Bumping this up. Any news ?

I’m getting 401 status even when I use Oauth on bubble to bubble connector. Despite the fact that User is Current User (when using Oauth) I can’t save to S3 actual private photo to other bubble app.