WASABI STORAGE DROPZONE & UTILITIES

Wasabi Storage Dropzone & Utilities

Published August 2022

    •    Updated January 2026

Plugin details

This plugin features a blazing fast WASABI DROPZONE with support for preview, image and video resizing, compression, audio compression, and advanced upload capabilities including parallel uploads, resumable uploads, and multi-part (parallel) uploads. 
It also includes a powerful set of Wasabi utilities, usable both as a standalone solution or in support of other plugin operations.

To use these actions in conjunction with our plugins, please refer directly to the plugin instructions.

The following elements for Wasabi are provided:
- WASABI DROPZONE visual element
- WASABI DROPZONE FILE PREVIEWER
- WASABI DROPZONE FILE UTILITIES (FRONT-END)

The following actions for Wasabi are provided:

𝗕𝗮𝗰𝗸-𝗘𝗻𝗱 𝗔𝗰𝘁𝗶𝗼𝗻𝘀:
- GET UPLOAD PRESIGNED EXPIRING URL (BACK-END)
- GENERATE DOWNLOAD PRESIGNED EXPIRING URL (BACK-END)
- PUT FILE TO WASABI (BACK-END)
- GET FILE BASE64 DATAURI FROM WASABI (BACK-END)
- PUT BASE64 DATAURI TO WASABI (BACK-END)
- DELETE FILE FROM WASABI (BACK-END)
- GET FILE METADATA FROM WASABI (BACK-END)
- LIST OBJECTS FROM WASABI (BACK-END)
- COPY FILE BETWEEN WASABI BUCKETS (BACK-END)
- SET FILE PUBLIC ACCESS IN WASABI (BACK-END)
- CREATE BUCKET IN WASABI (BACK-END)
- DELETE BUCKET IN WASABI (BACK-END)

𝗙𝗿𝗼𝗻𝘁-𝗘𝗻𝗱 𝗔𝗰𝘁𝗶𝗼𝗻𝘀:
- GENERATE DOWNLOAD PRESIGNED EXPIRING URL (FRONT-END)
- DELETE FILE OR FOLDER FROM WASABI (FRONT-END)
- SET FILE PUBLIC ACCESS IN WASABI (FRONT-END)

You may use Cloud2Cloud File Transfer Plugin (https://bubble.io/plugin/cloud2cloud-transfer-1682686574569x774496654310506500) to transfer files between storage providers, including Bubble.io.

Demo Link: https://wasabiutilitiesdemo.bubbleapps.io/version-test

Editor Link: https://bubble.io/page?type=page&name=index&id=wasabiutilitiesdemo-editor&tab=tabs-1

💡 𝗦𝘂𝗯𝘀𝗰𝗿𝗶𝗽𝘁𝗶𝗼𝗻𝘀 𝗮𝗿𝗲 𝗽𝗿𝗼𝗿𝗮𝘁𝗲𝗱. 𝗜𝗳 𝘆𝗼𝘂 𝗶𝗻𝘀𝘁𝗮𝗹𝗹 𝗮𝗻𝗱 𝘂𝗻𝘀𝘂𝗯𝘀𝗰𝗿𝗶𝗯𝗲 𝘁𝗵𝗶𝘀 𝗽𝗹𝘂𝗴𝗶𝗻 𝗶𝗻 𝗼𝗻𝗲 𝗱𝗮𝘆 𝘁𝗼 𝘁𝗲𝘀𝘁 𝗶𝘁 𝗼𝘂𝘁, 𝘆𝗼𝘂'𝗹𝗹 𝗼𝗻𝗹𝘆 𝗯𝗲 𝗰𝗵𝗮𝗿𝗴𝗲𝗱 𝟭/𝟯𝟬𝘁𝗵 𝗼𝗳 𝘁𝗵𝗲 𝗺𝗼𝗻𝘁𝗵𝗹𝘆 𝘀𝘂𝗯𝘀𝗰𝗿𝗶𝗽𝘁𝗶𝗼𝗻 𝗳𝗲𝗲.

📖 𝗦𝘁𝗲𝗽-𝗯𝘆-𝗦𝘁𝗲𝗽 𝗶𝗻𝘀𝘁𝗿𝘂𝗰𝘁𝗶𝗼𝗻𝘀 𝗮𝗿𝗲 𝗶𝗻 𝘁𝗵𝗲 "𝗜𝗻𝘀𝘁𝗿𝘂𝗰𝘁𝗶𝗼𝗻𝘀" 𝘀𝗲𝗰𝘁𝗶𝗼𝗻 𝗮𝗻𝗱 𝗗𝗲𝗺𝗼 𝗘𝗱𝗶𝘁𝗼𝗿 𝗶𝘀 𝗶𝗻 𝘁𝗵𝗲 "𝗟𝗶𝗻𝗸𝘀" 𝘀𝗲𝗰𝘁𝗶𝗼𝗻 𝗼𝗳 𝘁𝗵𝗲 𝗣𝗹𝘂𝗴𝗶𝗻 𝗣𝗮𝗴𝗲.

Our plugin portfolio: https://bubble.io/contributor/wiseable-1586609424436x711052886532460500

Contact us at [email protected] for any additional feature you would require or support question.

$129

One time • Or $7/mo

5.0 stars   •   4 ratings

122 installs  

This plugin does not collect or track your personal data.

Platform

Web & Native mobile

Contributor details

wise:able

Joined 2020   •   122 Plugins

View contributor profile

Instructions

1️⃣: WASABI DROPZONE
=============================

📋 ELEMENT DESCRIPTION
--------------------------------
WASABI DROPZONE is a visual element allowing to drop, resize, compress and select single- or multi-files supporting uploading, opening and deleting files with advanced multipart upload capabilities for large files.

🔧 STEP-BY-STEP SETUP
--------------------------------


0) Sign-up for Wasabi: https://wasabi.com/sign-up/

1) In Wasabi, create a BUCKET, go to PERMISSIONS and in the "BLOCK PUBLIC ACCESS" area unlock public access to all options to allow access via the links generated by the plugin.

2) Create your WASABI ACCESS KEY & ACCESS KEY SECRET, then add to the credentials the Wasabi FULL-ACCESS policy to the said BUCKET: https://wasabi.com/help/getting-started/

3) Register on plugins.wiseable.io. Create a new Credential which associates your BUBBLE APP URL, WASABI ACCESS KEY & ACCESS KEY SECRET.
The registration service will generate your PUBLIC ACCESS KEY. This key serves as a secure proxy for your real ACCESS KEY. It allows your application to communicate with the service without exposing your real ACCESS KEY. Since this PUBLIC ACCESS KEY is explicitly tied to your registered BUBBLE APP URL, it can only be used from that domain, ensuring that even if the key is publicly visible, it remains safe and cannot be misused by unauthorized sources.

4) In the Plugin Settings, enter the following:
   - WASABI ACCESS KEY & ACCESS KEY SECRET (for back-end actions)
   - PUBLIC ACCESS KEY (generated from plugins.wiseable.io) (for front-end elements)

5) Drag and drop the visual element WASABI DROPZONE in your app, containing the dropzone.

6) Select the WASABI DROPZONE element, in APPEARANCE section, configure the following fields:

FIELDS:
- RESULT DATA TYPE: Returned type. Must always be set to FILE METADATA (WASABI DROPZONE).
- ACCEPTED FILES TYPES: Either a case-insensitive filename extension, Format .ext. Example: .jpg, .pdf, or .doc. Or a standard MIME type, with no extensions. The string audio/* matches any audio file. The string video/* matches any video file. The string image/* matches any image file. Format type/subtype. Example: image/png, video/mp4. For more information, see http://www.w3.org/Protocols/rfc2616/rfc2616-sec14.html#sec14.17. Leave empty to accept any types.
- CAPTURE TYPE: When capturing live media on mobile devices, specifies either the user-facing or environment-facing media input to use, such as camera or microphone. Supported values: user | environment
- RETAIN FOLDER STRUCTURE: Retain folder structure when uploading a folder.
- MAX NUMBER OF FILES: Limit the maximum number of files in the Dropzone. Files beyond this limit will be in REJECTED FILES state.
- MAX FILE SIZE (MIB): Maximum allowed file size in MiB.
- UPLOAD BUCKET: Bucket Name of the file.
- UPLOAD FOLDER: Upload Folder. The format must be [path/]. Example 1: path1/path2/. Example 2: Leave empty if the file is at the root of the bucket.
- REGION: Bucket Region. See https://wasabi.com/company/storage-regions
- MAX PARALLEL UPLOADS: Max Parallel Uploads of Files, excluding chunks.
- AUTO UPLOAD: Set to true to trigger upload as soon as dropped in the Dropzone.
- PART SIZE (MIB): Part size in MiB to split the file in. Minimum value of 5 MiB. Please make sure that the total count of chunks for a given file does not exceed 1000.

IMAGE RESIZING & COMPRESSION SETTINGS:
- MAX WIDTH: If set, the image will be resized to this maximum width before upload. The other dimension will be adjusted proportionally to maintain the aspect ratio and avoid distortion.
- MAX HEIGHT: If set, the image will be resized to this maximum height before upload. The other dimension will be adjusted proportionally to maintain the aspect ratio and avoid distortion.
- IMAGE QUALITY: Image quality. The higher the number the higher the quality. Valid range is 0.0-1.0.

VIDEO RESIZING & COMPRESSION SETTINGS:
- CODEC: Target codec. Valid values: libx264 | libx265 | libvpx-vp9 | av1
- QUALITY FACTOR: Quality factor (0=best, 51=worst). Valid values: 0–51.
- PRESET: Encoding speed vs. compression. Valid values: ultrafast | superfast | veryfast | faster | fast | medium | slow | slower | veryslow.
- TUNE: Content optimization. Valid values: film | animation | fastdecode | zerolatency.
- OUTPUT RESOLUTION: Output resolution (e.g., 1280x720). Valid values: WxH (e.g., 1920x1080)

AUDIO COMPRESSION SETTINGS:
- CODEC: Target codec. Valid values: aac | libmp3lame | libvorbis | libopus | pcm_s16le | pcm_s24le | pcm_s32le.
- BITRATE: Target Bitrate. Valid values: 32k | 64k | 96k | 128k | 160k | 192k | 224k | 256k | 320k

7) Integrate the logic into your application using the following WASABI DROPZONE, states and actions:

EVENTS:
- ACCEPTED FILE LOOP: Event triggered for each accepted file, satisfying the ACCEPTED FILES TYPES and MAX FILE SIZE (MIB).
- REJECTED FILE LOOP: Event triggered for each rejected file, e.g. not satisfying the ACCEPTED FILES TYPES or the MAX FILE SIZE (MIB).
- UPLOADED FILE LOOP: Event triggered upon successful file upload.
- ALL FILES UPLOADED: Event triggered when all files have been processed.
- ERROR: Event triggered upon error.

EXPOSED STATES:
Use any element able to show/process the data of interest (such as a Group with a Text field) stored within the result of the following states of the WASABI DROPZONE element:
- ACCEPTED FILES: List of files' metadata satisfying the ACCEPTED FILES TYPES criteria in the dropzone. The available metadata are:
  • file_name - name of the dropped file.
  • upload_percentage - number between 0 and 100 showing the upload progress.
  • compression_percentage - number between 0 and 100 showing the compress progress.
  • file_size_bytes - size of the file in bytes.
  • object_url: value to set as input of the previewer,
  • mime_type: MIME-Type of the file. Value to set as input of the previewer,
  • status - added, queued, uploading, compressing, error, success.
    ▪ added - means the file is dropped to the dropzone and the destination URL is not assigned.
    ▪ queued - means to URL is assigned but there are other files uploading (2 files are uploaded at the same time).
    ▪ uploading - file is uploading.
    ▪ compressing - file is compressing.
    ▪ error - there was an error during the upload.
    ▪ success - upload is successful.
  • uuid - is a random identifier of this file.
  • upload_filepath - Path & File Name. The format is [path/]filename.ext.
  • upload_bytes_sent - upload progress in bytes.
  • bucket - bucket name where the file is uploaded.
  • region - region where the bucket is located.
- REJECTED FILES: List of rejected files' metadata. Same metadata as ACCEPTED FILES added the following:
  • message - rejection reason.
- TOTAL UPLOAD PROGRESS: Percentage of total uploaded bytes divided by the upload list's file's size.
- DRAGGING OVER: Returns true if a file is dragging over the dropzone, else otherwise.
- ERROR MESSAGE: Populated upon ERROR event.

ELEMENT ACTIONS - TRIGGERED IN WORKFLOW:
- REMOVE FILE FROM: Removes the specified file in the dropzone, identified by its UUID.
- RESET: Reset the dropzone to its initial state.
- CANCEL FILE UPLOAD: Cancel the specified file being uploaded, identified by its UUID.
- PROCESS UPLOAD QUEUE: Manually trigger the upload of queued files when AUTO UPLOAD is set to no.

2️⃣: WASABI DROPZONE FILE PREVIEWER
================================

📋 ELEMENT DESCRIPTION
--------------------------------
WASABI DROPZONE FILE PREVIEWER is a visual element allowing to display media preview along with controls when supported.

🔧 STEP-BY-STEP SETUP
--------------------------------

1) Drag and drop the visual element WASABI DROPZONE FILE PREVIEWER in your app.

2) Select the WASABI DROPZONE FILE PREVIEWER element, in APPEARANCE section, configure the following fields:

FIELDS:
- FILE OBJECT URL: Must contain the OBJECT_URL of the file to preview of the WASABI DROPZONE's ACCEPTED FILES state.
- MIME TYPE: Must contain the MIME-TYPE of the file to preview of the WASABI DROPZONE's ACCEPTED FILES state.
- SHOW CONTROLS: Show or hide media controls.

3) Integrate the logic into your application using the following WASABI DROPZONE, states and actions:

EXPOSED STATES:
Use any element able to show/process the data of interest (such as a Group with a Text field) stored within the result of the following states of the WASABI DROPZONE element:
- IS PREVIEWABLE: Returns yes if the media is previewable.

3️⃣: WASABI DROPZONE FILE UTILITIES (FRONT-END)
===============================================

📋 ELEMENT DESCRIPTION
--------------------------------
WASABI DROPZONE FILE UTILITIES (FRONT-END) provides front-end actions for Wasabi operations with client-side processing, ideal for mobile applications and improved responsiveness.

🔧 STEP-BY-STEP SETUP
--------------------------------

0) If not already done, perform steps 0, to 4 from the WASABI DROPZONE setup.

1) Add the WASABI DROPZONE FILE UTILITIES (FRONT-END) element to the page where Wasabi operations must be integrated.

2) Integrate the logic into your application using the following element's states and actions:

EVENTS:
- SUCCESS: Event triggered upon success.
- ERROR: Event triggered upon error.

EXPOSED STATES:
- RESULTS: Populated upon SUCCESS event. Returns the operation results.
- ERROR MESSAGE: Populated upon ERROR event. Always check this state and implement error handling using the ERROR event to provide a better user experience.
- REQUESTED ACTION: Latest requested Action

ELEMENT ACTIONS - TRIGGERED IN WORKFLOW:
- GENERATE DOWNLOAD PRESIGNED EXPIRING URL (FRONT-END): Generate an URL allowing access to the specified object, expiring after the specified duration.
- DELETE FILE OR FOLDER FROM WASABI (FRONT-END): Delete a file or folder from your Wasabi Bucket.
- SET FILE PUBLIC ACCESS IN WASABI (FRONT-END): Enable or disable public access via the virtual-hosted-style URL.

4️⃣: GET UPLOAD PRESIGNED EXPIRING URL (BACK-END)
===============================================

📋 ACTION DESCRIPTION
--------------------------------
GET UPLOAD PRESIGNED EXPIRING URL generates an URL allowing uploading for the specified bucket and path. This action is used in conjunction with the WASABI DROPZONE visual element.

🔧 STEP-BY-STEP SETUP
--------------------------------

0) If not already done, perform the steps 0, 2 and 3 of the WASABI DROPZONE setup.

1) Set up the "GET UPLOAD PRESIGNED EXPIRING URL (BACK-END)" action in the workflow.

Input Fields:
- STORAGE REGION: Bucket Region. See https://wasabi.com/company/storage-regions
- BUCKET NAME: Bucket Name of the file.
- PATH & FILE NAME: Path & File Name to process. The format must be [path/]filename.ext.
  Example 1: path1/path2/filename.ext.
  Example 2: filename.ext if the file is at the root of the bucket.

Output Fields:
- URL: Returns the presigned expiring URL.

5️⃣: GENERATE DOWNLOAD PRESIGNED EXPIRING URL (BACK-END)
======================================================

📋 ACTION DESCRIPTION
--------------------------------
GENERATE DOWNLOAD PRESIGNED EXPIRING URL generates an URL allowing access to the specified object, expiring after the specified duration. The presigned URLs are useful if you want your user/customer to be able to download a specific object from your bucket, but you don't require them to have Wasabi security credentials, permissions, nor bucket public access.

🔧 STEP-BY-STEP SETUP
--------------------------------

0) If not already done, perform the steps 0, 2 and 3 of the WASABI DROPZONE setup.

1) Set up the "GENERATE DOWNLOAD PRESIGNED EXPIRING URL (BACK-END)" action in the workflow.

Input Fields:
- STORAGE REGION: Bucket Region. See https://wasabi.com/company/storage-regions
- BUCKET NAME: Bucket Name of the file.
- PATH & FILE NAME: Path & File Name to process. The format must be [path/]filename.ext.
  Example 1: path1/path2/filename.ext.
  Example 2: filename.ext if the file is at the root of the bucket.
- EXPIRE AFTER (S): The number of seconds before the presigned URL expires. Defaults to 60 minutes.

Output Fields:
- URL: Returns the presigned expiring URL in Wasabi virtual-hosted-style format. Format is https://bucket-name.s3.Region.wasabisys.com/key-name?token.

6️⃣: PUT FILE TO WASABI (BACK-END)
============================

📋 ACTION DESCRIPTION
--------------------------------
PUT FILE TO WASABI stores a file in your Wasabi Bucket, returning the object key or URL if the operation is successful. The file must be less than 22 megabytes to be executable in backend workflow.

🔧 STEP-BY-STEP SETUP
--------------------------------

0) If not already done, perform the steps 0, 2 and 3 of the WASABI DROPZONE setup.

1) Optionally, add the "DETECT FILE TYPE" action from our FILE & MEDIA TYPE DETECTOR plugin to automatically detect the MIME-TYPE, which is set to "content/octet-stream" by default in Wasabi, and might prevent the browser from displaying correctly the media.

2) Set up the "PUT FILE TO WASABI (BACK-END)" action in the workflow.

Input Fields:
- FILE TO STORE (URL): File URL from the Bubble.io uploader, or a Protocol-relative URLs (//server/file.ext), or a HTTPS file URL (https://server/file.ext). The file must be accessible through the HTTPS protocol. The file must be less than 22 megabytes.
- CONTENT TYPE: A standard MIME type describing the format of the contents. Format type/subtype. Example: image/png, video/mp4. For more information, see http://www.w3.org/Protocols/rfc2616/rfc2616-sec14.html#sec14.17. Defaulting to "application/octet-stream".
- STORAGE REGION: Bucket Region. See https://wasabi.com/company/storage-regions
- BUCKET NAME: Bucket Name to which the file will be saved.
- PATH & FILE NAME: Path & File Name to save to. The format must be [path/]filename.ext.
  Example 1: path1/path2/filename.ext.
  Example 2: filename.ext if the file is at the root of the bucket.
- GENERATE URLS: Generate virtual-hosted-style URLs format in the response. Format is https://bucket-name.s3.Region.wasabisys.com/key-name.

Output Fields:
- FILE: Returns the object key or URL. For URL, format is https://bucket-name.s3.Region.wasabisys.com/key-name. Use this URL to retrieve the file, providing your bucket's permission allow getObject permission from the Internet.

7️⃣: GET FILE BASE64-DATAURI FROM WASABI (BACK-END)
==============================================

📋 ACTION DESCRIPTION
--------------------------------
GET FILE BASE64-DATAURI FROM WASABI retrieves the file Data URI from your Wasabi Bucket, encoded in Base64. Use this action to load the URI in an element supporting this format, such as an audio player, or store the datastream into a database. The file must be less than 4.5 megabytes to be executable in backend workflow.

🔧 STEP-BY-STEP SETUP
--------------------------------

0) If not already done, perform the steps 0, 2 and 3 of the WASABI DROPZONE setup.

1) Set up the "GET FILE BASE64-DATAURI FROM WASABI (BACK-END)" action in the workflow.

Input Fields:
- STORAGE REGION: Bucket Region. See https://wasabi.com/company/storage-regions
- BUCKET NAME: Bucket Name from which the file will be retrieved.
- PATH & FILE NAME: Path & File Name to retrieve. The file must be less than 4.5 megabytes. The format must be [path/]filename.ext.
  Example 1: path1/path2/filename.ext.
  Example 2: filename.ext if the file is at the root of the bucket.

Output Fields:
- BASE64 DATAURI: Returns the base64-encoded file data.

8️⃣: PUT BASE64 DATAURI TO WASABI (BACK-END)
======================================

📋 ACTION DESCRIPTION
--------------------------------
PUT BASE64 DATAURI TO WASABI stores BASE64 Data URI to a file in your Wasabi Bucket, returning the object key or URL if the operation is successful. The file must be less than 22 megabytes to be executable in backend workflow.

🔧 STEP-BY-STEP SETUP
--------------------------------

0) If not already done, perform the steps 0, 2 and 3 of the WASABI DROPZONE setup.

1) Set up the "PUT BASE64 DATAURI TO WASABI (BACK-END)" action in the workflow.

Input Fields:
- BASE64 DATAURI: Base64-encoded DataURI. The expected format is data:[mimeType];base64,[base64Data] and length must be less than 22 megabytes.
- STORAGE REGION: Bucket Region. See https://wasabi.com/company/storage-regions
- BUCKET NAME: Bucket Name to which the file will be saved.
- PATH & FILE NAME: Path & File Name to save to. The format must be [path/]filename.ext.
  Example 1: path1/path2/filename.ext.
  Example 2: filename.ext if the file is at the root of the bucket.
- GENERATE URLS: Generate virtual-hosted-style URLs format in the response. Format is https://bucket-name.s3.Region.wasabisys.com/key-name.

Output Fields:
- FILE: Returns the object key or URL. For URL, format is https://bucket-name.s3.Region.wasabisys.com/key-name. Use this URL to retrieve the file, providing your bucket's permission allow getObject permission from the Internet.

9️⃣: DELETE FILE FROM WASABI (BACK-END)
============================================

📋 ACTION DESCRIPTION
--------------------------------
DELETE FILE FROM WASABI deletes a file from your Wasabi Bucket, returning the object key or URL if the operation is successful.

🔧 STEP-BY-STEP SETUP
--------------------------------

0) If not already done, perform the steps 0, 2 and 3 of the WASABI DROPZONE setup.

1) Set up the "DELETE FILE FROM WASABI (BACK-END)" action in the workflow.

Input Fields:
- STORAGE REGION: Bucket Region. See https://wasabi.com/company/storage-regions
- BUCKET NAME: Bucket Name from which the file will be deleted.
- PATH & FILE NAME: Path & File Name to delete. The format must be [path/]filename.ext.
  Example 1: path1/path2/filename.ext.
  Example 2: filename.ext if the file is at the root of the bucket.
- GENERATE URLS: Generate virtual-hosted-style URLs format in the response. Format is https://bucket-name.s3.Region.wasabisys.com/key-name.

Output Fields:
- FILE: Returns the object key or URL.

🔟: GET FILE METADATA FROM WASABI (BACK-END)
=======================================

📋 ACTION DESCRIPTION
--------------------------------
GET FILE METADATA FROM WASABI retrieves the metadata of the specified object.

🔧 STEP-BY-STEP SETUP

0) If not already done, perform the steps 0, 2 and 3 of the WASABI DROPZONE setup.

1) Set up the "GET FILE METADATA FROM WASABI (BACK-END)" action in the workflow.

Input Fields:
- STORAGE REGION: Bucket Region. See https://wasabi.com/company/storage-regions
- BUCKET NAME: Bucket Name of the file.
- PATH & FILE NAME: Path & File Name to process. The format must be [path/]filename.ext.
  Example 1: path1/path2/filename.ext.
  Example 2: filename.ext if the file is at the root of the bucket.

Output Fields:
- FILE SIZE: Returns the size of the file's content in bytes.
- CREATED AT: Returns the date and time at which the file was created (RFC 3339 date-time).
- TAGS: Returns a list of tags. Each tag is formatted as key=value.

1️⃣1️⃣: LIST OBJECTS FROM WASABI (BACK-END)
==================================

📋 ACTION DESCRIPTION
--------------------------------
LIST OBJECTS FROM WASABI returns the list of objects' key or URLs from a Wasabi bucket.

🔧 STEP-BY-STEP SETUP
--------------------------------

0) If not already done, perform the steps 0, 2 and 3 of the WASABI DROPZONE setup.

1) Set up the "LIST OBJECTS FROM WASABI (BACK-END)" action in the workflow.

Input Fields:
- STORAGE REGION: Bucket Region. See https://wasabi.com/company/storage-regions
- BUCKET NAME: Bucket Name from which the list will be retrieved.
- PREFIX FILTER: Limit the response to keys that begin with the specified string, starting from the bucket name root.
- GENERATE URLS: Generate virtual-hosted-style URLs format in the response. Format is https://bucket-name.s3.Region.wasabisys.com/key-name.
- INCLUDE FOLDERS: Include folders in the response.

Output Fields:
- LIST: Returns the list of objects' key or URL.

1️⃣2️⃣: COPY FILE BETWEEN WASABI BUCKETS (BACK-END)
=============================================

📋 ACTION DESCRIPTION
--------------------------------
COPY FILE BETWEEN WASABI BUCKETS copy a file from a source bucket and path to a target bucket and path, then returns the object key or URL of the target file.

🔧 STEP-BY-STEP SETUP
--------------------------------

0) If not already done, perform the steps 0, 2 and 3 of the WASABI DROPZONE setup.

1) Set up the "COPY FILE BETWEEN WASABI BUCKETS (BACK-END)" action in the workflow.

Input Fields:
- STORAGE REGION: Bucket Region. See https://wasabi.com/company/storage-regions
- SOURCE BUCKET NAME: Bucket Name of the source file.
- SOURCE PATH & FILE NAME: Source Path & File Name that will be copied. The format must be [path/]filename.ext.
  Example 1: path1/path2/filename.ext.
  Example 2: filename.ext if the file is at the root of the bucket.
- TARGET BUCKET NAME: Bucket Name to which the file will be retrieved from.
- TARGET PATH & FILE NAME: Target Path & File Name. The format must be [path/]filename.ext.
  Example 1: path1/path2/filename.ext.
  Example 2: filename.ext if the file is at the root of the bucket.
- GENERATE URLS: Generate virtual-hosted-style URLs format in the response. Format is https://bucket-name.s3.Region.wasabisys.com/key-name.

Output Fields:
- FILE: Returns the object key or URL.

1️⃣3️⃣: SET FILE PUBLIC ACCESS IN WASABI (BACK-END)
=============================================

📋 ACTION DESCRIPTION
--------------------------------
SET FILE PUBLIC ACCESS IN WASABI enables or disable public access via the virtual-hosted-style URL.

🔧 STEP-BY-STEP SETUP
--------------------------------

0) If not already done, perform the steps 0, 2 and 3 of the WASABI DROPZONE setup.

1) Set up the "SET FILE PUBLIC ACCESS IN WASABI (BACK-END)" action in the workflow.

Input Fields:
- STORAGE REGION: Bucket Region. See https://wasabi.com/company/storage-regions
- BUCKET NAME: Bucket Name of the file.
- PATH & FILE NAME: Path & File Name. The format must be [path/]filename.ext.
  Example 1: path1/path2/filename.ext.
  Example 2: filename.ext if the file is at the root of the bucket.
- PUBLIC ACCESS: Enable public access via the virtual-hosted-style URL.
- GENERATE URLS: Generate virtual-hosted-style URLs format in the response. Format is https://bucket-name.s3.Region.wasabisys.com/key-name.

Output Fields:
- FILE: Returns the object key or URL.

1️⃣4️⃣: CREATE BUCKET IN WASABI (BACK-END)
====================================

📋 ACTION DESCRIPTION
--------------------------------
CREATE BUCKET IN WASABI creates a bucket in the specified region.

🔧 STEP-BY-STEP SETUP
--------------------------------

0) If not already done, perform the steps 0, 2 and 3 of the WASABI DROPZONE setup.

1) Set up the "CREATE BUCKET IN WASABI (BACK-END)" action in the workflow.

Input Fields:
- STORAGE REGION: Bucket Region. See https://wasabi.com/company/storage-regions
- BUCKET NAME: Bucket Name to create.

Output Fields:
- BUCKET NAME: Returns the bucket name if successful.

1️⃣5️⃣: DELETE BUCKET IN WASABI (BACK-END)
====================================

📋 ACTION DESCRIPTION
--------------------------------
DELETE BUCKET IN WASABI deletes the empty specified bucket.

🔧 STEP-BY-STEP SETUP
--------------------------------

0) If not already done, perform the steps 0, 2 and 3 of the WASABI DROPZONE setup.

1) Set up the "DELETE BUCKET IN WASABI (BACK-END)" action in the workflow.

Input Fields:
- STORAGE REGION: Bucket Region. See https://wasabi.com/company/storage-regions
- BUCKET NAME: Bucket Name to delete.

Output Fields:
- BUCKET NAME: Returns the bucket name if successful.

🔍 IMPLEMENTATION EXAMPLE
======================
Feel free to browse the app editor in the Service URL for an implementation example.

ℹ️ ADDITIONAL INFORMATION
======================
▶ Presigned URL may expire before the set expiration time depending on your credentials: https://wasabi.com/help/getting-started/

▶ Permissions details
- GET UPLOAD PRESIGNED EXPIRING URL (BACK-END) requires PutObject permission.
- GENERATE DOWNLOAD PRESIGNED EXPIRING URL (BACK-END) requires GetObject permission.
- PUT FILE TO WASABI (BACK-END) requires PutObject permission.
- GET FILE BASE64 DATAURI FROM WASABI (BACK-END) requires GetObject permission.
- PUT BASE64 DATAURI TO WASABI (BACK-END) requires PutObject permission.
- DELETE FILE FROM WASABI (BACK-END) requires DeleteObject permission.
- GET FILE METADATA FROM WASABI (BACK-END) requires GetObject, GetObjectTagging permissions.
- LIST OBJECTS FROM WASABI (BACK-END) requires ListBucket permission.
- COPY FILE BETWEEN WASABI BUCKETS (BACK-END) requires GetObject, PutObject permissions.
- SET FILE PUBLIC ACCESS IN WASABI (BACK-END) requires HeadObject, GetObject, PutObjectAcl permissions.
- CREATE BUCKET IN WASABI (BACK-END) requires CreateBucket, PutBucketOwnershipControls, PutBucketPublicAccessBlock, PutBucketCors permissions.
- DELETE BUCKET IN WASABI (BACK-END) requires DeleteBucket permission.

⚠️ TROUBLESHOOTING
================
Any plugin related error will be posted either to:
- Your browser Javascript console: Instructions here https://webmasters.stackexchange.com/questions/8525/how-do-i-open-the-javascript-console-in-different-browsers
- Logs tab, "Server logs" section of your App Editor.

Make sure that "Plugin server side output" and "Plugin client side output" is selected in "Show Advanced". Server Logs Details: https://manual.bubble.io/core-resources/bubbles-interface/logs-tab#server-logs

For front-end actions, you can also open your browser's developer console (F12 or Ctrl+Shift+I in most browsers) to view detailed error messages and logs.

Always check the ERROR MESSAGE state of the element and implement error handling using the ERROR event to provide a better user experience.

⚡ PERFORMANCE CONSIDERATIONS
===========================

𝗚𝗘𝗡𝗘𝗥𝗔𝗟
-------------
The largest retrievable result-set from Wasabi for back-end actions is capped at 30 seconds duration time - this does not apply to front-end actions.

⏱️ 𝗕𝗔𝗖𝗞-𝗘𝗡𝗗 𝗔𝗖𝗧𝗜𝗢𝗡 𝗦𝗧𝗔𝗥𝗧 𝗗𝗘𝗟𝗔𝗬
-----------------------------------------------
Each time a server-side action is called, Bubble initializes a small virtual machine to execute the action. If the same action is called shortly after, the caching mechanism kicks in, resulting in faster execution on subsequent calls.

A useful workaround is to fire a dummy execution at page load, which pre-warms the Bubble engine for the next few minutes, reducing the impact of cold starts for your users.

𝗣𝗨𝗧 𝗙𝗜𝗟𝗘 𝗧𝗢 𝗪𝗔𝗦𝗔𝗕𝗜 (𝗕𝗔𝗖𝗞-𝗘𝗡𝗗)
-------------------------
This implementation posts file data to Wasabi.
The file must be less than 22 megabytes to be executable in backend workflow, as the maximum allowable file size is capped by Bubble.io's Workflow Action maximum execution time to perform this transfer operation.

𝗣𝗨𝗧 𝗕𝗔𝗦𝗘𝟲𝟰 𝗗𝗔𝗧𝗔𝗨𝗥𝗜 𝗧𝗢 𝗪𝗔𝗦𝗔𝗕𝗜 (𝗕𝗔𝗖𝗞-𝗘𝗡𝗗)
-------------------------
This implementation posts file data to Wasabi.
The file must be less than 22 megabytes to be executable in backend workflow, as the maximum allowable file size is capped by Bubble.io's Workflow Action maximum execution time to perform this transfer operation.

𝗚𝗘𝗧 𝗙𝗜𝗟𝗘 𝗕𝗔𝗦𝗘𝟲𝟰-𝗗𝗔𝗧𝗔𝗨𝗥𝗜 𝗙𝗥𝗢𝗠 𝗪𝗔𝗦𝗔𝗕𝗜 (𝗕𝗔𝗖𝗞-𝗘𝗡𝗗)
----------------------------------------------
This implementation gets file data from Wasabi.
The file must be less than 4.5 megabytes to be executable in backend workflow, as the maximum allowable file size is capped by Bubble.io's Workflow Action maximum execution time to perform this transfer operation.

❓ QUESTIONS?
===========
Contact us at [email protected] for any additional feature you would require or support question.

Types

This plugin can be found under the following types:

Api   •   Background Services   •   Element   •   Event   •   Action

Resources

Support contact

Documentation

Tutorial

Rating and reviews

Average rating (5.0)

Support and resolution of issues at a high level!

November 23rd, 2024

A week ago I noticed a flaw - when you load a photo from your phone, it flips to the side by 90 degrees. I wrote about it in the plugin thread and almost instantly received a response and the first attempts to solve this problem. As a result, the creator of the plugin and I discussed the details, I provided all the input and that's it - the problem is solved.  Thanks redvivi

Good plugin all around

May 8th, 2024

Good plugin, well built, good support, haven't really had any issues at all.

Highly recommended

November 19th, 2022

Honestly the customer support from wise:able is the best out there for any plugin or template I have worked with.  

Great plugin and excellent customer service

September 13th, 2022

Highly recommend this plugin to store files on wasabi. I'm a relative newbie to Bubble so had some questions setting up with my app, but the customer service and forum thread were so helpful!
I'm still waiting for a reply from the owners of a competing plugin!! In the same time I've implemented this plugin and deployed!!

Thank you!

Product

Bubble for

Discover

Learn

Resources

Community

Company

Legal

Bubble uses cookies

Bubble uses cookies. By using our service you consent to all cookies in accordance with our Cookie Policy. Read more

Save & Close

I agree

I disagree

Show details

Strictly necessary

Performance

Targeting

Functionality

Unclassified

Cookie declaration

About cookies

Strictly necessary

Performance

Targeting

Functionality

Unclassified

Strictly necessary cookies allow core website functionality such as user login and account management. The website cannot be used properly without strictly necessary cookies.

Cookie report
Name	Provider / Domain	Expiration	Description
usprivacy	.bubble.io	1 year	This cookie stores the user's consent state regarding tracking and privacy in compliance with the United States privacy regulation.
__cf_bm	Cloudflare Inc. .calendly.com	29 minutes 45 seconds	This cookie is used to distinguish between humans and bots. This is beneficial for the website, in order to make valid reports on the use of their website.
__cf_bm	Cloudflare Inc. .clutch.co	29 minutes 55 seconds	This cookie is used to distinguish between humans and bots. This is beneficial for the website, in order to make valid reports on the use of their website.
li_gc	LinkedIn Corporation .linkedin.com	5 months 4 weeks	Used to store guest consent to the use of cookies for non-essential purposes
__cf_bm	Cloudflare Inc. .transformo.io	29 minutes 57 seconds	This cookie is used to distinguish between humans and bots. This is beneficial for the website, in order to make valid reports on the use of their website.
meta_u1main	.bubble.io	Session
__cf_bm	Cloudflare Inc. .lu.ma	29 minutes 44 seconds	This cookie is used to distinguish between humans and bots. This is beneficial for the website, in order to make valid reports on the use of their website.
meta_live_u2main.sig	.bubble.io	2 days 23 hours
_GRECAPTCHA	Google LLC www.google.com	5 months 4 weeks	Google reCAPTCHA sets a necessary cookie (_GRECAPTCHA) when executed for the purpose of providing its risk analysis.
__cf_bm	Cloudflare Inc. .producthunt.com	29 minutes 57 seconds	This cookie is used to distinguish between humans and bots. This is beneficial for the website, in order to make valid reports on the use of their website.
_GRECAPTCHA	Google LLC www.recaptcha.net	5 months 4 weeks	Google reCAPTCHA sets a necessary cookie (_GRECAPTCHA) when executed for the purpose of providing its risk analysis.
_gd_session	bubble.io	4 hours	This cookie manages user sessions on the website, ensuring that user interactions are recognized across various web requests. This helps in providing a consistent and accurate user experience.
_scid	Snap Inc. .bubble.io	1 year 1 month
opt_out	.postrelease.com	1 year	This cookie is used to track the user's decision to opt out of cookies on the website, indicating they have chosen not to have their data used for tracking and personalisation purposes.
AWSALBCORS	Amazon.com Inc. storm.birdie.so	6 days 23 hours	For continued stickiness support with CORS use cases after the Chromium update, we are creating additional stickiness cookies for each of these duration-based stickiness features named AWSALBCORS (ALB).
VISITOR_PRIVACY_METADATA	YouTube .youtube.com	5 months 4 weeks	This cookie is used to store the user's consent and privacy choices for their interaction with the site. It records data on the visitor's consent regarding various privacy policies and settings, ensuring that their preferences are honored in future sessions.
__cf_bm	Cloudflare Inc. .lumacdn.com	29 minutes 58 seconds	This cookie is used to distinguish between humans and bots. This is beneficial for the website, in order to make valid reports on the use of their website.
_tt_enable_cookie	.bubble.io	2 months 4 weeks	This cookie is used to remember the user's preferences regarding the use of cookies on the website.
AWSALBCORS	Amazon.com Inc. app.birdie.so	1 week	For continued stickiness support with CORS use cases after the Chromium update, we are creating additional stickiness cookies for each of these duration-based stickiness features named AWSALBCORS (ALB).
__cf_bm	Cloudflare Inc. .t.co	29 minutes 44 seconds	This cookie is used to distinguish between humans and bots. This is beneficial for the website, in order to make valid reports on the use of their website.
__cf_bm	Cloudflare Inc. .twitter.com	29 minutes 44 seconds	This cookie is used to distinguish between humans and bots. This is beneficial for the website, in order to make valid reports on the use of their website.
__cf_bm	Cloudflare Inc. .vimeo.com	29 minutes 58 seconds	This cookie is used to distinguish between humans and bots. This is beneficial for the website, in order to make valid reports on the use of their website.
__session	.gitbook.com	1 year 1 month	This cookie is used to maintain an anonymized user session by the server.
meta_live_u2main	.bubble.io	2 days 23 hours
CookieScriptConsent	CookieScript .bubble.io	1 year 1 month	This cookie is used by Cookie-Script.com service to remember visitor cookie consent preferences. It is necessary for Cookie-Script.com cookie banner to work properly.
meta-firebase_workflow	.bubble.io	59 minutes 21 seconds

Performance cookies are used to see how visitors use the website, eg. analytics cookies. Those cookies cannot be used to directly identify a certain visitor.

Cookie report
Name	Provider / Domain	Expiration	Description
X-AB	Stack Exchange Inc. sc-static.net	1 day
_ga_G4MHXCYE4T	.bubble.io	1 year 1 month	This cookie is used by Google Analytics to persist session state.
m	Stripe m.stripe.com	1 year 1 month	This cookie is generally used for performance and optimization of payment processing services, facilitating caching of content on the browser to make pages load faster.
_ttp	.bubble.io	2 months 4 weeks	This cookie is used to track user interaction and behavior on the website for site performance and usage analysis. This information is used to improve the user experience and optimize the website's functionality.
analytics_session_id	Cakemail .bubble.io	1 year	This cookie tracks user behavior throughout the session on the website, collecting data such as how long a visitor stays on a page and what links they click on. This information is used to improve user experience and website performance.
data-c	Media.net .media.net	4 weeks 2 days	This cookie is used to collect information on user behavior and interaction to enhance the user experience and measure website performance.
_gd_visitor	bubble.io	1 year 1 month	This cookie is used to track visitors' interactions with the website, collecting data on their behavior for analytics purposes. It helps in understanding how users engage with the site, which parts of the site are most visited, and how the navigation flow is structured, aiming to improve the user experience and site performance.
_ttp	.tiktok.com	2 months 4 weeks	This cookie is used to track user interaction and behavior on the website for site performance and usage analysis. This information is used to improve the user experience and optimize the website's functionality.
analytics_session_id.last_access	.bubble.io	1 year	This cookie is used to store the time of the last access by a user in an analytics session, helping in understanding user engagement and the effectiveness of the website content.
_ga_BFPVR2DEE2	.bubble.io	1 year 1 month	This cookie is used by Google Analytics to persist session state.
ahoy_visit	Teachable store.bubble.io	4 hours	This cookie is used to track a visitor's session, helping to understand how users interact with the site to improve user experience and functionality.
_ga_5Q4JP8E2X4	.bubble.io	1 year 1 month	This cookie is used by Google Analytics to persist session state.
_ga_CEPZJCHM3K	.bubble.io	1 year 1 month	This cookie is used by Google Analytics to persist session state.
data-c-ts	Media.net .media.net	4 weeks 2 days	This cookie is used to time-stamp and perform a time sync for users' sessions, ensuring accurate session time tracking.
_ga	Google LLC .bubble.io	1 year 1 month	This cookie name is associated with Google Universal Analytics - which is a significant update to Google's more commonly used analytics service. This cookie is used to distinguish unique users by assigning a randomly generated number as a client identifier. It is included in each page request in a site and used to calculate visitor, session and campaign data for the sites analytics reports. By default it is set to expire after 2 years, although this is customisable by website owners.
_ga_Y168TZXEQ5	.bubble.io	1 year 1 month	This cookie is used by Google Analytics to persist session state.
ajs_anonymous_id	Segment.io Inc. .bubble.io	1 year	These cookies are generally used for Analytics and help count how many people visit a certain site by tracking if you have visited before. This cookie has a lifespan of 1 year.
c	.bidswitch.net	1 year	This cookie is used to identify the frequency of visits and how the visitor accesses the website. It collects data on the user's visits to the website, such as which pages have been read.

Targeting cookies are used to identify visitors between different websites, eg. content partners, banner networks. Those cookies may be used by companies to build a profile of visitor interests or show relevant ads on other websites.

Cookie report
Name	Provider / Domain	Expiration	Description
YSC	Google LLC .youtube.com	Session	This cookie is set by YouTube to track views of embedded videos.
personalization_id	Twitter Inc. .twitter.com	1 year 1 month	This cookie carries out information about how the end user uses the website and any advertising that the end user may have seen before visiting the said website.
CMPRO	Casale Media Inc. .casalemedia.com	2 months 4 weeks	These cookies are linked to advertising and tracking the products users were looking at.
_scid_r	.bubble.io	1 year 1 month	This cookie is used for tracking purposes, helping to identify unique visitors across sessions and track their interactions and engagement on the website.
tv_UICR	.tremorhub.com	4 weeks 2 days	This cookie is used to track user interactions and engagement with the website's content to improve the service and content delivery. It can collect data on user behavior and preferences to facilitate targeted advertising and marketing strategies.
VISITOR_INFO1_LIVE	Google LLC .youtube.com	5 months 4 weeks	This cookie is set by Youtube to keep track of user preferences for Youtube videos embedded in sites;it can also determine whether the website visitor is using the new or old version of the Youtube interface.
tvid	Tremor Video DSP .tremorhub.com	1 year	This cookie is used for tracking user interaction and engagement with the website's content, helping in the improvement and optimization of online services provided. It may also be used for delivering personalized advertising experiences.
uid	.criteo.com	1 year	This cookie provides a uniquely assigned, machine-generated user ID and gathers data about activity on the website. This data may be sent to a 3rd party for analysis and reporting.
_uetsid	Microsoft Corporation .bubble.io	1 day	This cookie is used by Bing to determine what ads should be shown that may be relevant to the end user perusing the site.
lidc	Microsoft Corporation .linkedin.com	1 day	This is a Microsoft MSN 1st party cookie that ensures the proper functioning of this website.
_uetvid	Microsoft Corporation .bubble.io	1 year 3 weeks	This is a cookie utilised by Microsoft Bing Ads and is a tracking cookie. It allows us to engage with a user that has previously visited our website.
addshoppers	shop.pe	1 year 1 month	This cookie is used to track user interaction and sharing behavior on social media platforms, enabling personalized marketing and social media sharing capabilities.
_gcl_au	Google LLC .bubble.io	3 months	Used by Google AdSense for experimenting with advertisement efficiency across websites using their services
addshoppers.com	bubble.io	1 year 1 month	This cookie is associated with the AddShoppers social sharing platform, a technology that integrates with websites to enable tracking and sharing capabilities across social networks. It supports social media integration and can gather data regarding sharing and social interactions on the site to help understand user influence and to enhance marketing strategies.
CMID	Casale Media Inc. .casalemedia.com	1 year	These cookies are linked to advertising and tracking the products users were looking at.
bcookie	Microsoft Corporation .linkedin.com	1 year	This is a Microsoft MSN 1st party cookie for sharing the content of the website via social media.
tuuid_lu	.bidswitch.net	1 year	Contains a unique visitor ID, which allows Bidswitch.com to track the visitor across multiple websites. This allows Bidswitch to optimize advertisement relevance and ensure that the visitor does not see the same ads multiple times.
tuuid	.bidswitch.net	1 year	This cookie is mainly set by bidswitch.net to make advertising messages more relevant to the website visitor.
_fbp	Meta Platform Inc. .bubble.io	2 months 4 weeks	Used by Facebook to deliver a series of advertisement products such as real time bidding from third party advertisers
ab	.agkn.com	1 year	This cookie is generally provided by agkn.com and is used for advertising purposes.
demdex	Adobe Inc. .demdex.net	5 months 4 weeks	This cookie helps Adobe Audience Manger perform basic functions such as visitor identification, ID synchronization, segmentation, modeling, reporting, etc.
sc_at	Snap Inc. .snapchat.com	1 year
MUID	Microsoft Corporation .bing.com	1 year	This cookie is widely used my Microsoft as a unique user identifier. It can be set by embedded microsoft scripts. Widely believed to sync across many different Microsoft domains, allowing user tracking.
dpm	Adobe Inc. .dpm.demdex.net	5 months 4 weeks	Adobe Audience Manager - data management platform uses this cookie to record information around synchronisation of IDs.
CMPS	Casale Media Inc. .casalemedia.com	2 months 4 weeks	These cookies are linked to advertising and tracking the products users were looking at.

Functionality cookies are used to remember visitor information on the website, eg. language, timezone, enhanced content.

Cookie report
Name	Provider / Domain	Expiration	Description
ajs_anonymous_id	Segment.io Inc. .loom.com	1 year 1 month	These cookies are generally used for Analytics and help count how many people visit a certain site by tracking if you have visited before. This cookie has a lifespan of 1 year.
loom_anon_comment	Loom .loom.com	1 year 1 month	This cookie is used to differentiate anonymous users when they leave comments on holaspirit.com, enabling the identity of the commenter to remain unknown for privacy.
_cfuvid	.vimeo.com	Session	This cookie is used for purposes of tracking users across sessions to optimize user experience by maintaining session consistency and providing personalized services.
__stripe_mid	Stripe Inc. .bubble.io	1 year	This cookie is set by Stripe to distinguish users and enable secure payment processing during interactions with the website.
_cfuvid	.calendly.com	Session	This cookie is used for purposes of tracking users across sessions to optimize user experience by maintaining session consistency and providing personalized services.
ajs_anonymous_id	Segment.io Inc. demo.arcade.software	1 year	These cookies are generally used for Analytics and help count how many people visit a certain site by tracking if you have visited before. This cookie has a lifespan of 1 year.
__stripe_sid	Stripe Inc. .bubble.io	29 minutes 58 seconds	This cookie is set by Stripe to manage and process payments securely, allowing temporary storage of session related information during a users visit to the website.
loom_referral_video	Loom, Inc. .www.loom.com	Session	This cookie is used to track referrals and video plays across the website, enabling the website to attribute video views to the correct referral sources.
MSPTC	Microsoft .bat.bing.com	1 year	This cookie is used to track user engagement and interaction with the website to enhance customer experience and website functionality. It may collect information about how users navigate and use the site, helping to identify preferences and improve service delivery.
visitor-id	Media.net .media.net	1 year	This cookie is used to identify unique visitors across the website to provide a consistent and personalized experience.

Unclassified cookies are cookies that do not belong to any other category or are in the process of categorization.

Cookie report
Name	Provider / Domain	Expiration
__Secure-ROLLOUT_TOKEN	.youtube.com	5 months 4 weeks
ttcsid	.bubble.io	2 months 4 weeks
intercom-device-id-cz703g22	.bubble.io	8 months 4 weeks
intercom-session-cz703g22	.bubble.io	1 week
kwsu	ciqtracking.com	1 year 1 month
CrossDomainCookieScriptConsent_239	.crossdomain.cookie-script.com	1 year 1 month
__BROWSER__	store.bubble.io	Session
ahoy_visitor	store.bubble.io	1 year 1 month
bubble-certifications_live_u2main	.certification.bubble.io	3 days
_ScCbts	.bubble.io	1 week
_brilliant_session	.bubble.io	Session
bubble-certifications_live_u2main.sig	.certification.bubble.io	3 days
ttcsid_CRGSJIJC77UAMBH9S77G	.bubble.io	2 months 4 weeks
bubble-certifications_u1main	.certification.bubble.io	Session
_iub_cs-57859130-uspr	.bubble.io	1 year
intercom-id-cz703g22	.bubble.io	8 months 4 weeks
muc_ads	Twitter .t.co	1 year 1 month
upgrade_pv_1487181547537x364191731148390400	bubble.io	1 week

Cookies are small text files that are placed on your computer by websites that you visit. Websites use cookies to help users navigate efficiently and perform certain functions. Cookies that are required for the website to operate properly are allowed to be set without your permission. All other cookies need to be approved before they can be set in the browser.

You can change your consent to cookie usage at any time on our Privacy Policy page.

Your consent will also apply to the following websites:

bubble.io
flusk.eu

Wasabi Storage Dropzone & Utilities

Plugin details

$129

One time • Or $7/mo

Other actions

Platform

Contributor details

Instructions

Types

Categories

Resources

Rating and reviews

Average rating (5.0)