How does OCNORA authenticate with Google API Keys?

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 API Keys?

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

What if the Google API Keys operation I need is not listed?

Where Google API Keys 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 API Keys?

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

How are Google API Keys 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 API Keys

Google CloudOAuth 2.0Connection test available

Manages the API keys associated with developer projects (Google OAuth2).

OCNORA ships 6 typed Google API Keys 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 API Keys Google API Keys API docs ↗

Before you connect Google API Keys

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 API Keys

Operations, grouped by what they do to your data.

Create and send 1

Create Key

Read and search 3

Update 1

Update Key

Delete and cancel 1

Delete Key

A sample Google API Keys workflow

1
A core trigger
Start the run from a chat, form, manual, schedule, webhook, workflow trigger — no Google API Keys trigger is needed.
2
Get Keyapi_keys.get_key
Gets the metadata for an API key. The key string of the API key isn't included in the response.
3
Create Keyapi_keys.create_key
Creates a new API key.

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 6

Google API Keys questions

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

Book a technical demo Talk to sales