Reference · Credentials
MongoDB credentials
Used by 1 BusyBot node.
Type
mongodbApi 11 fields Fields
| Field | Type | Required | Notes |
|---|---|---|---|
Connection StringconnectionString | password | No | Full MongoDB URI. If provided, overrides individual fields. |
Hosthost | string | No | — |
Portport | number | No | — |
Databasedatabase | string | Yes | — |
Useruser | string | No | — |
Passwordpassword | password | No | — |
Auth SourceauthSource | string | No | Authentication database (e.g. \ |
Use TLS/SSLtls | boolean | No | Enable TLS. Required for MongoDB Atlas and most managed providers. |
Allow Invalid CertificatestlsAllowInvalidCertificates | boolean | No | Skip TLS certificate validation. NEVER enable in production. |
Replica Set NamereplicaSet | string | No | Optional replicaSet name for direct connection to a replica set. |
Use SRV (DNS Seedlist)useSrv | boolean | No | Use mongodb+srv:// scheme. Required for MongoDB Atlas cluster hostnames. |
Setting up MongoDB
- In MongoDB, create the credential this connection needs — the values listed in the table above. These are issued from your own MongoDB account, usually under its developer, API or integrations settings.
- In BusyBot, open Credentials → Add credential and choose MongoDB.
- Paste each value into the matching field and save.
- Add the MongoDB 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 MongoDB
One credential works across every node below — create it once and reuse it.