Automate file storage operations with Google Cloud Storage. Upload, download, manage buckets, set permissions, and monitor changes with real-time triggers.
Google Cloud Storage currently provides 2 triggers that can start a workflow and 12 actions a workflow can run. Use those building blocks to turn activity in one tool into an owned next step in the shared workspace.
New Object Created
Triggers when a new object is created in a bucket
Object Updated
Triggers when an existing object is updated in a bucket
Create Bucket
Create a new bucket in a specified location/configuration. Perfect for automating storage provisioning for new projects.
Delete Empty Bucket
Clean up unused buckets by deleting them if they contain no live objects.
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.
Delete Object
Permanently delete a specific object. Perfect for removing obsolete files.
Search Objects
Search objects by criteria. Perfect for finding files in your bucket.
Search Buckets
Search buckets by name. Perfect for finding buckets in your project.
Create Object ACL
Add an ACL entry to an object (grant a permission). Perfect for granting read/write access to a user or group.
Delete Object ACL
Remove an ACL entry from an object. Perfect for revoking access for a user.
Create Bucket ACL
Add an ACL entry at bucket level. Perfect for granting permission to manage the bucket.
Delete Bucket ACL
Remove an ACL entry from a bucket. Perfect for revoking access for a user or group.
Create Bucket Default Object ACL
Set default ACLs for new objects added to a bucket. Perfect for automatically assigning permissions to new uploads.
Delete Bucket Default Object ACL
Remove default ACL settings from a bucket. Perfect for reverting to default behavior.
These recipes are generated from the triggers, actions, and categories currently available for this piece. Use them as starting points, then choose the exact fields, conditions, and records your workflow should update.
Start from a supported Google Cloud Storage event, then create or update the appropriate CRM, project, or custom record with the source context preserved.
Starts with
New Object Created
Finishes with
Create or update a Coherence record
Use a change in Coherence to run a supported Google Cloud Storage action, so the next step follows the record instead of relying on someone to copy it.
Starts with
A Coherence record or workflow changes
Finishes with
Create Bucket
Combine Google Cloud Storage with another integration and Coherence records to turn activity in one tool into an owned next step in the shared workspace.
Starts with
New Object Created
Finishes with
Create Bucket, then preserve the outcome in Coherence
The exact authentication fields depend on Google Cloud Storage. The workflow structure stays straightforward:
Authorize the Google Cloud Storage account and permissions the workflow needs.
Select one of the current triggers or actions listed above and map its fields.
Run a small test, inspect the result in both systems, and only then enable the workflow.
Explore apps that share a category with Google Cloud Storage or provide a complementary trigger or action.
Google Cloud Storage currently provides 2 triggers that can start a workflow and 12 actions a workflow can run. Use those building blocks to turn activity in one tool into an owned next step in the shared workspace.
Google Cloud Storage currently lists 2 triggers and 12 actions in the integration catalog. The supported list is refreshed from the pieces available in Coherence, so review the capability names on this page before building a workflow.
Yes. A workflow can combine supported Google Cloud Storage triggers or actions with Coherence records and other available integrations. The exact flow depends on the authentication, permissions, triggers, and actions exposed by each connected app.
The listed triggers and actions are designed for visual workflows. If the pre-built integration does not expose a capability you need, HTTP and webhook steps can cover APIs that your team is authorized to use.
Start automating in minutes. No credit card required.
