Trigger Input - emulate click on input and show file dialog.

Upload - Start uploading files to Wasabi.

Uploads files to Wasabi using the presigned url generated by the server side action - Create presigned URL

Fields:

Title	Description	Type
Presigned URLs	Presigned URLs generated by Create Presigned url server side action(PUT HTTP method)	Text

Reset File Uploader - Remove all files from this element. Reset states: Files (to the empty list ), Files Count (to 0), File Size Total (to 0), Upload Progress (to 0), Is Uploading (to false), Is Reading Files (to false).

Download File - download a file from Wasabi.

Fields:

Title	Description	Type
Presigned URLs	Presigned URLs generated by Create Presigned url server side action	Text
Download File Name	The name you would like to give to this file. Leave empty to use the original file name.	Text
SSE key	(optional) In order to use Wasabi server side encryption fill-in this field with 256-bit, base64-encoded encryption key. You can use Create SSE-C Key action to create the key.	Text

☝

Note: Plugin functionality doesn’t provide an option to display download progress as it has no access to such data (tracking current load). The download process depends on many factors that the plugin can’t consider (network bandwidth, device capability, file size, etc).

Delete Files/Folders - Delete files and folders from the selected bucket

Fields:

Title	Description	Type
Presigned URLs	Presigned URLs generated by Create Presigned URL server side action(Delete HTTP method)	Text

Remove File From Input - remove the file from the element.

Fields:

Title	Description	Type
File	The file you would like to remove.	Text

Cancel Upload - cancel current files uploading

Fields:

Title	Description	Type
Reset after	Reset uploader after the upload ends	yes/no

Upload File To Wasabi From Another Cloud element Action

Fields

Title	Description	Type
S3 Presigned URL	here a regular url from any service can be used, as long as it is public, or the result of Generate S3 compatible presigned url for private S3 buckets	text

Retrieve encrypted files element Action

Use this action to display encrypted files in your application. First use the serverside action Retrieve files with the Encrypted Files checkbox checked and them use the returned presigned urls to get the files here

Fields

Title	Description	Type
Presigned Urls	A list of presigned urls from the Retrieve Files action	text
SSE Key	SSE Key for decription

This action will return a state - Encrypted Files Urls.

1. Create Presigned URL
This action generates pre-signed URLs for S3-compatible storage operations (Wasabi in this case). It supports GET, PUT, and DELETE operations for single or multiple files. The function can use either permanent or temporary credentials and optionally enables server-side encryption. It allows customization of URL expiration time and handles various input formats. The function returns an array of presigned URLs, each corresponding to a file specified in the input, enabling secure, time-limited access to S3 objects without requiring AWS credentials to be shared with the client.



Fields

Title	Description	Type
Bucket name	The name of the Wasabi bucket where the object(s) are stored.	Text
Bucket Region	The region where this Bucket is stored. Please check all available regions here	Text
Object Key	The key (path) of the file(s) in the bucket.	list of texts
HTTP method	The HTTP method for which to generate the pre-signed URL (GET, PUT, or DELETE).	Dropdown
Expiration Time	The duration for which the pre-signed URL will be valid.	Number
Timeslot	The unit of time for the expiration (Days, Hours, Minutes or Seconds).	Dropdown

⌛
Note: The maximum value of expiration time is 7 days.
The action returns an object with a single property:
• presignedUrls: An array of strings, where each string is a pre-signed URL for an S3 object.
The length of the presignedUrls array corresponds to the number of object keys provided in the objectKey input property. If a single object key is provided, the array will contain one URL. If multiple object keys were provided (comma-separated), the array will contain a URL for each key.
Each pre-signed URL in the array:
• Allows the specified HTTP method (GET, PUT, or DELETE) on the corresponding S3 object.
• Is valid for the duration specified by the expirationTime and time_var inputs.
These URLs can be used to perform the specified operation on the S3 objects without requiring additional authentication, as long as they are used before expiration.

2. Create SSE-C Key
This action generates a random base64-encoded encryption key for Wasabi to use to encrypt or decrypt your data.
Run the action and save the result to a state or to a database to use it later in others actions. You will need only the “SSE Customer Key” state in the plugin's actions.





❗
NOTE: Wasabi does not store the encryption key you provide. If you lose the encryption key, any GET request for an object without its encryption key fails, and you lose the object.

3. Create Bucket



Fields:

Title	Description	Type
Bucket name	Must be unique, valid DNS name, 63 characters or less. Case sensitive.	Text
Bucket Region	The region of where this Bucket is stored. Please check all available regions here	Text

5. Retrieve Files

1. status (string): Either "success" or "fail", indicating the outcome of the operation.

2. files (array of objects): An array containing information about each file in the specified location. Each object in the array has the following properties:
• Location (string): The full path of the object in the bucket.
• Full Name (string): The full name of the file, including extension.
• Name (string): The name of the file without extension.
• Type (string|null): The MIME type of the file, or null if not determined.
• Parameters (string|null): Any query parameters in the object key.
• Size (number): The size of the object in bytes.
• Extension (string|null): The file extension, or null if none.
• Last Modified (string): The last modification date of the object.
• S3 URL (string): The complete URL to access the object in S3.
• SSE URL (string): Pre-signed URL if encrypted files is true
• Storage Class (string): The storage class of the object in S3.
• Full Name Encoded (string): URL-encoded full name of the file.
• Name Encoded (string): URL-encoded name of the file without extension.

3. error (string): An error message if the operation failed, empty string otherwise.

6. Delete files/folders

1. deleted (array of strings): An array containing the locations from which objects were successfully deleted.

2. error (string): An error message if an operation failed, or an empty string if all operations were successful.

1. status: Either "success" or "fail", indicating the outcome of the operation.

2. error: An empty string if successful, or the error message if the operation failed.

8. Initiate Multipart Upload

1. UploadIds: The IDs of the initiated multipart upload.

2. presignedUrls: A list of pre-signed URLs for each part of the multipart upload.

9. Complete Multipart Upload

10. Retrieve Buckets

1. status: Either "success" or "fail", indicating the outcome of the operation.

2. buckets: An array of bucket names if successful, or an empty array if failed.

3. error: An empty string if successful, or the error message if the operation failed.

11. Create folder

1. success: A boolean indicating whether the operation was successful.

2. message: A string describing the result of the operation.

3. error: (Only present if success is false) A string containing the error message.

12. Generate S3 Compatible GET Presigned URLs - generates an S3 compatible GET presigned url for accessing files from S3 like private buckets



Title	Description	Type
Bucket name	The name of the S3 compatible bucket where the object(s) are stored.	Text
Object Key	The file from the S3 compatible service. Ex: folder1/forder2/folderX/filename.ext	Text
Expiration Time	An expiration time interval, maximum 7 days	Text
Timeslot	Timeslot to use for expiration time. Available options: Seconds, Minutes, Hours, Days	Dropdown
Bucket Region	The region where the S3 compatible bucket is located.	Text
Endpoint URL	Allows you to specify a custom endpoint URL for your S3-compatible storage service. This is particularly useful when working with S3-compatible storage providers other than Amazon S3, such as MinIO, Wasabi, or other object storage systems that implement the S3 API. If provided, this URL will be used as the base endpoint for all S3 operations instead of the default Amazon S3 endpoints. This allows the plugin to connect to your specific S3-compatible storage service. Usage: If you’re using Amazon S3, you can leave this property empty. For other S3-compatible services, provide the full URL to your storage service’s API endpoint. Example Values: “https://play.min.io:9000” (for MinIO) “https://s3.wasabisys.com” (for Wasabi) “https://your-custom-s3-compatible-endpoint.com”	Text (optional)

Return Values:

Title	Description	Type
Presigned URLs	S3 compatible GET presigned url	Text

1. Upload File To Wasabi From Another Cloud
This API Call allows uploading files to your Wasabi Cloud Storage from another cloud storage (for example all uploaded in base files are saved to AWS S3 and you have a URL of them ).
For an API call to work, you need to enter the Wasabi Access Key and Secret Key.



❗
This API Call is in BETA mode. Max upload file size = 300MB. If you try to upload files with a larger size, it may respond with an error text message.



Fields

Name	Description	Type
Private	Using access token has full control. No one else has access rights, not public. The value word “true” or “false”.	Text
Bucket_Name	The name of the Bucket you would like to upload to. Case sensitive.	Text
Bucket_Region	The region of where this Bucket is stored. Enter one of the following: us-west-1, eu-central-1, us-east-1, us-east-2.	Text
Folder_Structure	The folder structure of where this file should be saved (example: uploads) . You can also specify sub folders (eg: uploads/images). As a suggestion you could save the folder as current user/thing’s unique id.	Text
Filename_Prefix	Prefix for the file name. Some special characters (for example: !$#@), will not upload correctly.	Text
Filename	FIle name to save on Wasabi S3 with extension ( .png, .mp3, etc.) )	Text
URL_From_Another_Cloud	URL of file	Text
Access_Key	Wasabi Access Key	Text
Secret_Key	Wasabi Secret Key	Text

Return Values: Return type: JSON

json
{
  "Location": "text",
  "Full Name": "text",
  "Name": "text",
  "Type": "text",
  "Size": "number",
  "Extension": "text",
  "S3 URL": "text"
}

2. Upload File To Wasabi From Another Cloud with SSE
The same API call as Upload File To Wasabi From Another Cloud but with the field SSE
This API Call allows uploading files to your Wasabi Cloud Storage from another cloud storage with Wasabi Server Side encription.
For an API call to work, you need to enter the Wasabi Access Key, Secret Key, and sse_key.



❗
This API Call is in BETA mode. Max upload file size = 300MB. If you try to upload files with a larger size, it may respond with an error text message.



Fields

Name	Description	Type
Private	Using access token has full control. No one else has access rights, not public. The value word “true” or “false”.	Text
Bucket_Name	The name of the Bucket you would like to upload to. Case sensitive.	Text
Bucket_Region	The region of where this Bucket is stored. Enter one of the following: us-west-1, eu-central-1, us-east-1, us-east-2.	Text
Folder_Structure	The folder structure of where this file should be saved (example: uploads) . You can also specify sub folders (eg: uploads/images). As a suggestion you could save the folder as current user/thing’s unique id.	Text
Filename_Prefix	Prefix for the file name. Some special characters (for example: !$#@), will not upload correctly.	Text
Filename	FIle name to save on Wasabi S3 with extension ( .png, .mp3, etc.) )	Text
URL_From_Another_Cloud	URL of file	Text
Access_Key	Wasabi Access Key	Text
Secret_Key	Wasabi Secret Key	Text
Sse_key	In order to use Wasabi server side encryption fill-in this field with 256-bit, base64-encoded encryption key. You can use “Create SSE-C Key” action to create the key.	Text

Return Values: Return type: JSON

json
{
  "body Location": "text",
  "body Full Name": "text",
  "body Name": "text",
  "body Type": "text",
  "body Size": "number",
  "body Extension": "text",
  "body S3 URL": "text",
  "body message": "text",
  "error status_code": "number",
  "error status_message": "text",
  "error body": "text",
  "returned_an_error": "yes/no"
}

By default, public use of a bucket, folder, or file is allowed only by certain paid (not trial) accounts. If your account does not have access to this feature, contact Wasabi Support at support@wasabi.com for assistance.

1. Go to your Wasabi console

javascript
{
  "Version": "2012-10-17",
  "Statement": [
    {
      "Effect": "Allow",
			"Principal": {
			        "AWS": "*"
			      },
      "Action": "s3:*",
      "Resource": "*",
      "Condition": {
        "StringLike": {
          "aws:Referer": "YOUR_WEB_SITE_FULL_URL"
        }
      }
    }
  ]
}

By default, public use of a bucket, folder, or file is allowed only by certain paid (not trial) accounts. If your account does not have access to this feature, contact Wasabi Support at support@wasabi.com for assistance.

javascript
{
  "Id": "acceptsonlyhttpreferer",
  "Version": "2012-10-17",
  "Statement": [
    {
      "Sid": "Public",
      "Effect": "Deny",
      "Principal": {
        "AWS": "*"
      },
      "Action": "s3:GetObject",
      "Resource": "arn:aws:s3:::YOUR_BUCKET_NAME_HERE/*",
      "Condition": {
        "StringNotLike": {
          "aws:Referer": [
            "https://YOUR_BUBBLE_APP_URL_HERE/",
            "https://YOUR_BUBBLE_APP_URL_HERE/*",
            "https://console.wasabisys.com/",
            "https://console.wasabisys.com/*"
          ]
        }
      }
    }
  ]
}

• Your Bubble app

• WASABI Console

The Lifecycle feature is only supported for new buckets. Create a new bucket in order to create and apply lifecycle rules.

• Click CREATE NEW RULE. The Lifecycle Rule Settings panel is displayed.

• Enter a name for the Lifecycle rule. For example:

• Choose the scope of the rule. You can:— Limit the scope of the rule by using filters. Continue with Step 6.— Apply the rule to all objects in the bucket. Skip to Step 7.

• Filter options are provided when you choose to limit the scope of the rule. You can filter by a name prefix and/or the size of the object. For size, you can enter the minimum and/or maximum size in bytes, kilobytes, megabytes, or gigabytes.

• Check at least one of the Action options. Follow the on-screen instructions for the selected option(s), as described in Lifecycle Rule Actions below.

• Click CREATE.

• .jpg - JPEG has been the most widely used image compression standard in the world.

• .psd - Photoshop Document (PSD) is a raster format for storing graphic information using lossless compression, created specifically for Adobe Photoshop and supporting all its capabilities.

• .pdf - Portable Document Format (PDF) is a file format developed by Adobe in 1993 to present documents, including text formatting and images, in a manner independent of application software, hardware, and operating systems.

• etc.

1. audio/* -any audio file.

2. video/* -any video file.

3. image/* -any image file.

Simple upload workflow example( single part, file less than 5Gb in size)

1. Place the Wasabi element on the page and fill the desired settings

2. To set up auto upload use the File added event

3. Add Create pre-signed URL action to the workflow and fill the necessary fields ( HTTP method for upload should be PUT)

4. Next, use the Upload action (pre-signed URLs should be the result of 1st step - Create pre-signed URLs

Multipart upload workflow example( file more than 5Gb in size)

1. Place the Wasabi element on the page and fill the desired settings

2. To set up auto upload use the File added event

3. Add Initiate Multipart Upload action to the workflow

4. Save the Upload ID and the file location to a custom state

5. Next, use the Upload action (the pre-signed URLs should be the result of step one - Initiate Multipart Upload)

6. To complete a multipart upload you have to use another event - All parts uploaded

7. Add Complete Multipart upload action to the workflow, use the saved custom states for the Object Key and Upload ID, and the Parts returned state

Delete file client-side workflow

1. Set up a button to trigger the workflow

2. Add Create Presigned Url action (use DELETE HTTP method)

3. Use the Delete files action (pre-signed URLs should be the result of 1st step)

Download file client-side workflow

1. Set up a button to trigger the download action

2. Add the Create presigned URL action to the workflow ( use the GET HTTP method)

3. Use the Download file action to finish the download

Upload from another cloud example

1. Set up an event to trigger the upload action, for example a button click

2. Add Generate S3 compatible presigned url action to the workflow

3. Add Upload to Wasabi from another cloud action to the workflow and use the result from the first action in it

4. From now on it should follow the same path as in the first workflow example , use the file added event and Get presigned url and Upload action( please see first workflow example)