Revoke Certificate

private_ca.revoke_certificate
ActionGoogle Cloudconnection required

Calls Certificate Authority POST /v1/projects/{projectsId}/locations/{locationsId}/caPools/{caPoolsId}/certificates/{certificatesId}:revoke.

Revoke a Certificate.

Connection

Required
Yes — the node will not save without one
Auth type
OAuth 2.0
Providers
Google Certificate Authority
Secret shape
{"client_id", "client_secret", "refresh_token"}
Config it needs
location, project_id
Resolved by
config.connection_id, else node.connection_id

Configuration

5 fields, 2 required. A dotted path is a nested object and name[] an array of objects — the editor renders the same tree.

FieldTypeRequiredDefaultConstraintsExample
project_id
GCP project id (overrides connection).
stringNo———
location
Location / region (overrides connection).
stringNo———
ca_pool
Id of the ca pool to act on, from private_ca.list_ca_pools — not its name.
stringYes———
certificate
Certificate id.
stringYes———
body
Request body (RevokeCertificateRequest) as JSON.
objectNo———

Output

One shape.

result

FieldTypeExample
ok
boolean—
createTime
string—
issuerCertificateAuthority
string—
config
object—
pemCertificate
string—
revocationDetails
object—
subjectMode
string—
{
  "config": {},
  "createTime": "",
  "issuerCertificateAuthority": "",
  "ok": false,
  "pemCertificate": "",
  "revocationDetails": {},
  "subjectMode": ""
}

See Revoke Certificate run in a workflow.

In a technical demo we add the Google Certificate Authority connection, drop the node on the canvas and let Workflow Health pre-flight it before the first real run.