How does OCNORA authenticate with Google Cloud Workflows?

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

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

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

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

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

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

Google CloudOAuth 2.0Connection test available

Execute and inspect Google Cloud Workflows (Google OAuth2).

OCNORA ships 3 typed Google Cloud Workflows 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 Workflows

Before you connect Google Cloud Workflows

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 Workflows

Operations, grouped by what they do to your data.

Create and send 1

Execute

Read and search 2

A sample Google Cloud Workflows workflow

1
A core trigger
Start the run from a chat, form, manual, schedule, webhook, workflow trigger — no Google Cloud Workflows trigger is needed.
2
Get Executioncloud_workflows.get_execution
Fetch a Cloud Workflows execution's state and result.
3
Executecloud_workflows.execute
Start a Cloud Workflows execution with a JSON argument (no polling).

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