Google Cloud Storage
Google Cloud Storage objects (Google OAuth2).
OCNORA ships 11 typed Google Cloud Storage operations. Each node has a schema-driven form, input and output tables beside its settings, and is pre-flighted by Workflow Health before your first real run.
Before you connect Google Cloud Storage
- Authentication
- OAuth 2.0
- Credential
- {"client_id", "client_secret", "refresh_token"}
- Connection test
- Available: the stored credential can be checked against the provider when you add it. This is not a record that a test was run or passed.
What you can do with Google Cloud Storage
Operations, grouped by what they do to your data.
Create and send 2
Read and search 5
Update 1
Delete and cancel 2
Other operations 1
Nodes that use your Google Cloud Storage connection
Beyond its own nodes, these generic nodes accept your Google Cloud Storage credential. Each chooses the provider from the connection you select, so the same node also works with the other providers shown.
- Fetch Filefile.fetchDownload a file from Cloud Storage, S3 or Azure Blob as a file blob.Also works withAmazon S3Azure Blob Storage
- Put Filefile.putUpload text or a file blob to Cloud Storage, S3 or Azure Blob.Also works withAmazon S3Azure Blob Storage
A sample Google Cloud Storage workflow
- 1A core triggerStart the run from a chat, form, manual, schedule, webhook, workflow trigger — no Google Cloud Storage trigger is needed.
- 2Get Bucketgcs.get_bucketRead a bucket's location, labels, versioning, lifecycle and access config.
- 3Copy Objectgcs.copy_objectCopy a Cloud Storage object to another key or bucket.
An outline built from this provider’s node contracts, not a recorded run. Each step’s output fields are available to the next in the field picker.
Every node below has a reference page: what it does, the connection it needs, its config fields with types, constraints and examples, and the shapes it emits.
Operations 11
- Copy ObjectCopy a Cloud Storage object to another key or bucket.gcs.copy_object
- Create BucketCreate a Cloud Storage bucket with a location and storage class.gcs.create_bucket
- Delete BucketDelete an empty Cloud Storage bucket.gcs.delete_bucket
- Delete ObjectDelete an object from a Google Cloud Storage bucket.gcs.delete_object
- Get BucketRead a bucket's location, labels, versioning, lifecycle and access config.gcs.get_bucket
- Get ObjectDownload an object from a Cloud Storage bucket as a file (base64 envelope).gcs.get_object
- Get Object MetadataRead a Cloud Storage object's size, checksums, holds and custom metadata.gcs.get_object_metadata
- List BucketsList the Cloud Storage buckets in a GCP project.gcs.list_buckets
- List ObjectsList objects in a Google Cloud Storage bucket.gcs.list_objects
- Put ObjectUpload a text or binary object to a Google Cloud Storage bucket.gcs.put_object
- Update Object MetadataChange a Cloud Storage object's headers and custom metadata in place.gcs.update_object_metadata
Google Cloud Storage questions
- How does OCNORA authenticate with Google Cloud Storage?
- With a stored OAuth 2.0 credential, shaped {"client_id", "client_secret", "refresh_token"}. A connection test can check it when you add it.
- What can I automate with Google Cloud Storage?
- 11 typed operations, each with a reference page listing its config fields and the shapes it emits. The credential also drives 2 generic nodes.
- What if the Google Cloud Storage operation I need is not listed?
- Where Google Cloud Storage has an HTTP API, call it from the HTTP node with the same credential, or describe the step to the AI builder, which asks our team for a typed node when one is missing.
- Are there templates that use Google Cloud Storage?
- Not yet. Start from a blank workflow, or describe the workflow to Build with AI.
- How are Google Cloud Storage calls controlled?
- Every call and every run step is audited, runs count against the execution budget, and Workflow Health pre-flights the workflow when you save it.
See your first Google Cloud Storage workflow run.
Book a technical demo. We add the connection, pick a template or describe the workflow to Build with AI, and Workflow Health checks it before it runs.