Reference · Credentials
Oracle Database credentials
Used by 1 BusyBot node.
Type
oracleDBApi 8 fields Fields
| Field | Type | Required | Notes |
|---|---|---|---|
Useruser | string | Yes | Oracle database username |
Passwordpassword | password | Yes | Oracle database password |
Connection StringconnectionString | string | Yes | Oracle connection string (Easy Connect: host:port/service_name or TNS name) |
Privilegeprivilege | options | No | Administrative privilege (leave empty for normal connections) |
Use SSL/TLSuseSSL | boolean | No | Whether to use SSL/TLS for the connection |
SSL CertificatesslCertificate | string | No | PEM-encoded SSL certificate (for mTLS) |
SSL KeysslKey | password | No | PEM-encoded SSL private key (for mTLS) |
SSL CA CertificatesslCA | string | No | PEM-encoded CA certificate |
Setting up Oracle Database
- In Oracle Database, create the credential this connection needs — the values listed in the table above. These are issued from your own Oracle Database account, usually under its developer, API or integrations settings.
- In BusyBot, open Credentials → Add credential and choose Oracle Database.
- Paste each value into the matching field and save.
- Add the Oracle SQL 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 Oracle Database
One credential works across every node below — create it once and reuse it.