Delete Certificate
venafi_tpp.delete_certificate
ActionBusiness appsconnection required
Calls the Venafi TLS Protect Datacenter API with the connection's credentials.
Remove a Certificate object, its workflow tickets and its vaults.
Connection
- Required
- Yes — the node will not save without one
- Auth type
- Custom
- Providers
- Venafi TLS Protect Datacenter
- Secret shape
- {"username": "…", "password": "…"} or {"access_token": "…"}
- Config it needs
- base_url, client_id, scope
- Resolved by
- config.connection_id, else node.connection_id
Configuration
1 field, 1 required. A dotted path is a nested object and name[] an array of objects — the editor renders the same tree.
| Field | Type | Required | Default | Constraints | Example |
|---|---|---|---|---|---|
guid GUID of the Certificate object, with or without the braces Venafi writes it in. | string | Yes | — | — | {2b6b673f-2c55-46fc-935a-5836eae9b9db} |
Example configuration
Every value below is the contract’s own example or default — nothing invented.
{
"guid": "{2b6b673f-2c55-46fc-935a-5836eae9b9db}"
}Output
One shape.
result
| Field | Type | Example |
|---|---|---|
guid The Certificate object that was removed. | string | — |
deleted True when the platform accepted the removal. | boolean | — |
{
"deleted": false,
"guid": ""
}Notes
- Deleting the object does not revoke the certificate at the authority; run venafi_tpp.revoke_certificate first when that is what you mean.
Related Venafi TLS Protect Datacenter nodes
See Delete Certificate run in a workflow.
In a technical demo we add the Venafi TLS Protect Datacenter connection, drop the node on the canvas and let Workflow Health pre-flight it before the first real run.