Reference · Credentials
Venafi TLS Protect Datacenter API credentials
Used by 1 BusyBot node.
Type
venafiTlsProtectDatacenterApi 4 fields Fields
| Field | Type | Required | Notes |
|---|---|---|---|
Domaindomain | string | Yes | Base URL of the Venafi TPP instance (e.g., https://tpp.example.com) |
Client IDclientId | string | Yes | OAuth2 client ID registered in the Venafi TPP instance |
Usernameusername | string | Yes | Venafi TPP username with certificate management permissions |
Passwordpassword | password | Yes | Password for the Venafi TPP user account |
Setting up Venafi TLS Protect Datacenter API
- In Venafi TLS Protect Datacenter API, create the credential this connection needs — the values listed in the table above. These are issued from your own Venafi TLS Protect Datacenter API account, usually under its developer, API or integrations settings.
- In BusyBot, open Credentials → Add credential and choose Venafi TLS Protect Datacenter API.
- Paste each value into the matching field and save.
- Add the Venafi TLS Protect Datacenter Trigger node to a workflow, select this credential, and run a simple operation to confirm it authenticates.
Security
- Secret values are encrypted at rest with AES-256-GCM and are never shown again after saving.
- Grant the minimum scopes or permissions the operations you actually use require.
- Rotate the credential periodically, and immediately if it may have been exposed.
- Credentials are scoped to your account — a workflow cannot use another account's.
Nodes that use Venafi TLS Protect Datacenter API
One credential works across every node below — create it once and reuse it.