Google Certificate Authority
The Certificate Authority Service API is a highly-available, scalable service that enables you to simplify and automate the management of private cert (Google OAuth2).
OCNORA ships 10 typed Google Certificate Authority 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.
Before you connect Google 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 Certificate Authority
Operations, grouped by what they do to your data.
Create and send 2
Read and search 4
Update 2
Delete and cancel 2
A sample Google Certificate Authority workflow
- 1A core triggerStart the run from a chat, form, manual, schedule, webhook, workflow trigger — no Google Certificate Authority trigger is needed.
- 2Get Ca Poolprivate_ca.get_ca_poolReturns a CaPool.
- 3Create Ca Poolprivate_ca.create_ca_poolCreate a CaPool.
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 10
- Create Ca PoolCreate a CaPool.private_ca.create_ca_pool
- Create CertificateCreate a new Certificate in a given Project, Location from a particular CaPool.private_ca.create_certificate
- Delete Ca PoolDelete a CaPool.private_ca.delete_ca_pool
- Get Ca PoolReturns a CaPool.private_ca.get_ca_pool
- Get CertificateReturns a Certificate.private_ca.get_certificate
- List Ca PoolsLists CaPools.private_ca.list_ca_pools
- List CertificatesLists Certificates.private_ca.list_certificates
- Revoke CertificateRevoke a Certificate.private_ca.revoke_certificate
- Update Ca PoolUpdate a CaPool.private_ca.update_ca_pool
- Update CertificateUpdate a Certificate.private_ca.update_certificate
Google Certificate Authority questions
- How does OCNORA authenticate with Google 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 Certificate Authority?
- 10 typed operations, each with a reference page listing its config fields and the shapes it emits.
- What if the Google Certificate Authority operation I need is not listed?
- Where Google 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 Certificate Authority?
- Not yet. Start from a blank workflow, or describe the workflow to Build with AI.
- How are Google 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.
See your first Google Certificate Authority 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.