BusyBot
Search all guides

Reference · Credentials

Connect Venafi TLS Protect Datacenter to BusyBot

Used by 1 BusyBot node.

Type venafiTlsProtectDatacenterApi 4 fields

Fields

FieldTypeRequiredNotes
Domain
domain		 string Yes Base URL of the Venafi TPP instance (e.g., https://tpp.example.com)
Client ID
clientId		 string Yes OAuth2 client ID registered in the Venafi TPP instance
Username
username		 string Yes Venafi TPP username with certificate management permissions
Password
password		 password Yes Password for the Venafi TPP user account

Setting up Venafi TLS Protect Datacenter API

  1. 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.
  2. In BusyBot, open Credentials → Add credential and choose Venafi TLS Protect Datacenter API.
  3. Paste each value into the matching field and save.
  4. 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, never written to logs, and readable only by your own account (to edit them).
  • 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.

Frequently asked questions

Which BusyBot nodes use Venafi TLS Protect Datacenter credentials?

One node: Venafi TLS Protect Datacenter Trigger. Create the credential once and select it in that node.

What does a Venafi TLS Protect Datacenter credential need?

4 fields: Domain, Client ID, Username, Password. Required: Domain, Client ID, Username, Password. The values come from your own Venafi TLS Protect Datacenter account.

How are Venafi TLS Protect Datacenter secrets stored?

Secret values are encrypted at rest with AES-256-GCM, never written to logs, and scoped to your account: only you can open the credential again to edit it, and a workflow in another account cannot use it.

Nodes that use Venafi TLS Protect Datacenter API

One credential works across every node below — create it once and reuse it.