BusyBot
Search all guides

Reference · Credentials

Connect LDAP to BusyBot

Used by 1 BusyBot node.

Type ldapApi 8 fields

Fields

FieldTypeRequiredNotes
LDAP Server Address
hostname		 string Yes IP address or domain name of the LDAP server
LDAP Server Port
port		 string No Port for LDAP connection (389 for LDAP, 636 for LDAPS)
Binding DN
bindDN		 string Yes Distinguished Name of the user to authenticate as
Binding Password
bindPassword		 password Yes Password for the Bind DN user
Connection Security
connectionSecurity		 options No —
Ignore SSL/TLS Issues
allowUnauthorizedCerts		 boolean No Whether to connect even if SSL/TLS certificate validation fails
CA Certificate
caCertificate		 string No PEM-encoded CA certificate for verifying the LDAP server certificate
Timeout
timeout		 number No Connection timeout in seconds

Setting up LDAP

  1. In LDAP, create the credential this connection needs — the values listed in the table above. These are issued from your own LDAP account, usually under its developer, API or integrations settings.
  2. In BusyBot, open Credentials → Add credential and choose LDAP.
  3. Paste each value into the matching field and save.
  4. Add the LDAP 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 LDAP credentials?

One node: LDAP. Create the credential once and select it in that node.

What does a LDAP credential need?

8 fields: LDAP Server Address, LDAP Server Port, Binding DN, Binding Password, Connection Security, Ignore SSL/TLS Issues, CA Certificate, Timeout. Required: LDAP Server Address, Binding DN, Binding Password. The values come from your own LDAP account.

How are LDAP 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 LDAP

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