Skip to content
Documentation
Contact
← Back to documentation
Technical Reference

Google Cloud Storage

Automate file storage operations with Google Cloud Storage. Upload, download, manage buckets, set permissions, and monitor changes with real-time triggers.

CategoryContent And Files
AuthenticationOAuth 2.0
Version0.1.7
Published scopes5 published scopes
Last updatedSeptember 19, 2026

Overview

Connect Google Cloud Storage with Flows360

Automate file storage operations with Google Cloud Storage. Upload, download, manage buckets, set permissions, and monitor changes with real-time triggers.

Use the Google Cloud Storage connector to include its declared actions and events in Flows360 workflows without duplicating the integration logic inside each consuming system. This pinned connector version currently exposes 12 actions and 2 triggers.

Available actions

  • Create Bucket
  • Delete Empty Bucket
  • Clone Object
  • Delete Object
  • Search Objects
  • Search Buckets
  • Create Object ACL
  • Delete Object ACL
  • Plus 4 additional declared actions.

Available triggers

  • New Object Created
  • Object Updated

The capability list above is generated from the exact reviewed connector package so the public description stays aligned with the version Flows360 operates.

Technical guide

Technical reference

Package identity

  • Connector: Google Cloud Storage
  • Package: @activepieces/piece-google-cloud-storage@0.1.7
  • Exact artifact digest: sha256:f30b0324074410208f6f53574a1b4b9e76385c17bd3e3c83bb7b2246fe3fae7b
  • Runtime: Activepieces-compatible deterministic worker
  • Source: the exact reviewed Activepieces source

Authentication

OAUTH2. Connection values are tenant-specific and remain in the consuming Studio instance; CDK stores definitions and field metadata, not customer credential values.

Action contracts

  • Create Bucket (create_bucket), Create a new bucket in a specified location/configuration. Perfect for automating storage provisioning for new projects. Classification: read.
  • Delete Empty Bucket (delete_empty_bucket), Clean up unused buckets by deleting them if they contain no live objects. Classification: read.
  • Clone Object (clone_object), Copy / clone an object (file) to a new location (same or different bucket), optionally overriding metadata. Perfect for duplicating files as backup or version. Classification: read.
  • Delete Object (delete_object), Permanently delete a specific object. Perfect for removing obsolete files. Classification: read.
  • Search Objects (search_objects), Search objects by criteria. Perfect for finding files in your bucket. Classification: read.
  • Search Buckets (search_buckets), Search buckets by name. Perfect for finding buckets in your project. Classification: read.
  • Create Object ACL (create_object_acl), Add an ACL entry to an object (grant a permission). Perfect for granting read/write access to a user or group. Classification: read.
  • Delete Object ACL (delete_object_acl), Remove an ACL entry from an object. Perfect for revoking access for a user. Classification: read.
  • Create Bucket ACL (create_bucket_acl), Add an ACL entry at bucket level. Perfect for granting permission to manage the bucket. Classification: read.
  • Delete Bucket ACL (delete_bucket_acl), Remove an ACL entry from a bucket. Perfect for revoking access for a user or group. Classification: read.
  • Create Bucket Default Object ACL (create_bucket_default_object_acl), Set default ACLs for new objects added to a bucket. Perfect for automatically assigning permissions to new uploads. Classification: read.
  • Delete Bucket Default Object ACL (delete_bucket_default_object_acl), Remove default ACL settings from a bucket. Perfect for reverting to default behavior. Classification: read.

Trigger contracts

  • New Object Created, webhook.
  • Object Updated, webhook.

Verification

Deterministic execution evidence is recorded for the pinned artifact, including 1 exercised action entrypoint and 0 exercised trigger entrypoints.

Capability summary

AuthenticationOAuth 2.0
Supported objects14
Supported actionsNot published
Triggers2

Authentication

Authentication method: OAuth 2.0

Required scopes

https://www.googleapis.com/auth/devstorage.read_writehttps://www.googleapis.com/auth/devstorage.full_controlhttps://www.googleapis.com/auth/cloud-platform.read-onlyhttps://www.googleapis.com/auth/pubsubemail

Authentication profiles

connection · oauth2

OAuth scopes: https://www.googleapis.com/auth/devstorage.read_write, https://www.googleapis.com/auth/devstorage.full_control, https://www.googleapis.com/auth/cloud-platform.read-only, https://www.googleapis.com/auth/pubsub, email

Supported objects

ObjectReadWriteNotes
Create Bucket Yes No Create a new bucket in a specified location/configuration. Perfect for automating storage provisioning for new projects.
Delete Empty Bucket Yes No Clean up unused buckets by deleting them if they contain no live objects.
Clone Object Yes No Copy / clone an object (file) to a new location (same or different bucket), optionally overriding metadata. Perfect for duplicating files as backup or version.
Delete Object Yes No Permanently delete a specific object. Perfect for removing obsolete files.
Search Objects Yes No Search objects by criteria. Perfect for finding files in your bucket.
Search Buckets Yes No Search buckets by name. Perfect for finding buckets in your project.
Create Object ACL Yes No Add an ACL entry to an object (grant a permission). Perfect for granting read/write access to a user or group.
Delete Object ACL Yes No Remove an ACL entry from an object. Perfect for revoking access for a user.
Create Bucket ACL Yes No Add an ACL entry at bucket level. Perfect for granting permission to manage the bucket.
Delete Bucket ACL Yes No Remove an ACL entry from a bucket. Perfect for revoking access for a user or group.
Create Bucket Default Object ACL Yes No Set default ACLs for new objects added to a bucket. Perfect for automatically assigning permissions to new uploads.
Delete Bucket Default Object ACL Yes No Remove default ACL settings from a bucket. Perfect for reverting to default behavior.
New Object Created Yes No webhook trigger declared by the pinned package.
Object Updated Yes No webhook trigger declared by the pinned package.

Triggers

New Object Created · Webhook

Triggers when a new object is created in a bucket

Inputs

  • projectId · string
  • bucket · string
  • prefix · string
Object Updated · Webhook

Triggers when an existing object is updated in a bucket

Inputs

  • projectId · string
  • bucket · string
  • prefix · string

Setup

Setup

  1. Add the Google Cloud Storage connector to the workflow in the target Flows360 Studio instance.
  2. Create or select the tenant-specific connection required by the connector. Connection secrets remain in the Studio connection boundary and are not copied into CDK documentation.
  3. Provide the connection fields declared by the pinned package:
  • No provider credential fields are declared by the pinned package.

OAuth scopes

  • https://www.googleapis.com/auth/devstorage.read_write
  • https://www.googleapis.com/auth/devstorage.full_control
  • https://www.googleapis.com/auth/cloud-platform.read-only
  • https://www.googleapis.com/auth/pubsub
  • email
  1. Select the required action or trigger and complete its declared input fields. Required and optional inputs are defined by the exact package schema.
  2. Test the workflow in the appropriate environment before enabling production scheduling or event delivery.

Limitations

Limitations and operational notes

  • This content describes @activepieces/piece-google-cloud-storage@0.1.7; provider behaviour can change independently and should be revalidated when the provider or connector version changes.
  • Only the 12 actions and 2 triggers declared by this pinned package are represented here.
  • Tenant credentials and connection values are not stored in the public connector record.
  • Provider-side permissions, account entitlements, quotas and rate limits remain subject to the connected provider account and are not inferred when the package does not declare them.
  • Deterministic execution evidence is recorded for the pinned artifact, including 1 exercised action entrypoint and 0 exercised trigger entrypoints.

Troubleshooting

Why canu2019t the connector authenticate?

Check the tenant connection in Studio and confirm every required Google Cloud Storage connection field is present. Re-authorise OAuth-based connections if the provider token or consent has expired. Do not place credential values in CDK content or logs.

Why is an action or trigger unavailable?

Confirm that the workflow is using @activepieces/piece-google-cloud-storage@0.1.7 and compare the requested capability with the declared action and trigger list for this version. A capability that is not declared by the pinned package should not be presented as supported.

What should I check after a provider-side change?

Revalidate authentication, required fields, action/trigger behaviour and provider documentation before publishing refreshed connector content or moving a new package version into production.

github.com