How does OCNORA authenticate with Google Public Certificate Authority?

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 Public Certificate Authority?

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

What if the Google Public Certificate Authority operation I need is not listed?

Where Google Public Certificate Authority 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 Public Certificate Authority?

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

How are Google Public Certificate Authority 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 Public Certificate Authority

Google CloudOAuth 2.0Connection test available

The Public Certificate Authority API may be used to create and manage ACME external account binding keys associated with Google Trust Services' public (Google OAuth2).

OCNORA ships 1 typed Google Public Certificate Authority operation. 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 Public Certificate Authority Google Public Certificate Authority API docs ↗

Before you connect Google Public Certificate Authority

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 Public Certificate Authority

Operations, grouped by what they do to your data.

Create and send 1

Create External Account Key

A sample Google Public Certificate Authority workflow

1
A core trigger
Start the run from a chat, form, manual, schedule, webhook, workflow trigger — no Google Public Certificate Authority trigger is needed.
2
Create External Account Keypublic_ca.create_external_account_key
Creates a new ExternalAccountKey bound to the project.

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 1

Create External Account Key
Creates a new ExternalAccountKey bound to the project.
public_ca.create_external_account_key