How does OCNORA authenticate with Google Cloud Shell?

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

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

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

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

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

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

Google CloudOAuth 2.0Connection test available

Allows users to start, configure, and connect to interactive shell sessions running in the cloud (Google OAuth2).

OCNORA ships 3 typed Google Cloud Shell 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 Shell Google Cloud Shell API docs ↗

Before you connect Google Cloud Shell

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 Shell

Operations, grouped by what they do to your data.

A sample Google Cloud Shell workflow

1
A core trigger
Start the run from a chat, form, manual, schedule, webhook, workflow trigger — no Google Cloud Shell trigger is needed.
2
Get Environmentcloud_shell.get_environment
Gets an environment. Returns NOT_FOUND if the environment does not exist.
3
Add Public Keycloud_shell.add_public_key
Adds a public SSH key to an environment, allowing clients with the corresponding private key to connect to that environment via SSH.

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 3