How does OCNORA authenticate with Google Cloud Batch?

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 Batch?

4 typed operations, each with a reference page listing its config fields and the shapes it emits.

What if the Google Cloud Batch operation I need is not listed?

Where Google Cloud Batch 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 Batch?

Not yet. Start from a blank workflow, or describe the workflow to Build with AI.

How are Google Cloud Batch 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.

Google Cloud Batch

Google CloudOAuth 2.0Connection test available

Run container jobs on Google Cloud Batch (Google OAuth2).

OCNORA ships 4 typed Google Cloud Batch 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.

Ask about Google Cloud Batch

Before you connect Google Cloud Batch

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 Batch

Operations, grouped by what they do to your data.

Create and send 1

Create Job

Read and search 2

Delete and cancel 1

Delete Job

A sample Google Cloud Batch workflow

1
A core trigger
Start the run from a chat, form, manual, schedule, webhook, workflow trigger — no Google Cloud Batch trigger is needed.
2
Get Jobcloud_batch.get_job
Fetch a Cloud Batch job's state and task-group counts.
3
Create Jobcloud_batch.create_job
Create a Cloud Batch job that runs a container across N tasks.

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 4