Google Storage Batch Operations

Google CloudOAuth 2.0Connection test available

Storage Batch Operations (Google OAuth2).

OCNORA ships 6 typed Google Storage Batch Operations 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 Storage Batch Operations

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 Storage Batch Operations

Operations, grouped by what they do to your data.

Create and send 1

Read and search 4

Delete and cancel 1

A sample Google Storage Batch Operations workflow

  1. 1
    A core trigger
    Start the run from a chat, form, manual, schedule, webhook, workflow trigger — no Google Storage Batch Operations trigger is needed.
  2. 2
    Get Bucket Operationstorage_batch_operations.get_bucket_operation
    Gets a BucketOperation.
  3. 3
    Create Jobstorage_batch_operations.create_job
    Creates a batch job.

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.

Google Storage Batch Operations questions

How does OCNORA authenticate with Google Storage Batch Operations?
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 Storage Batch Operations?
6 typed operations, each with a reference page listing its config fields and the shapes it emits.
What if the Google Storage Batch Operations operation I need is not listed?
Where Google Storage Batch Operations 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 Storage Batch Operations?
Not yet. Start from a blank workflow, or describe the workflow to Build with AI.
How are Google Storage Batch Operations 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 Storage Batch Operations 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.