BusyBot
Search all guides

Reference · Credentials

Connect MongoDB to BusyBot

Used by 1 BusyBot node.

Type mongodbApi 11 fields

Fields

FieldTypeRequiredNotes
Connection String
connectionString		 password No Full MongoDB URI. If provided, overrides individual fields.
Host
host		 string No —
Port
port		 number No —
Database
database		 string Yes —
User
user		 string No —
Password
password		 password No —
Auth Source
authSource		 string No Authentication database (e.g. \
Use TLS/SSL
tls		 boolean No Enable TLS. Required for MongoDB Atlas and most managed providers.
Allow Invalid Certificates
tlsAllowInvalidCertificates		 boolean No Skip TLS certificate validation. NEVER enable in production.
Replica Set Name
replicaSet		 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

  1. 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.
  2. In BusyBot, open Credentials → Add credential and choose MongoDB.
  3. Paste each value into the matching field and save.
  4. 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, 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 MongoDB credentials?

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

What does a MongoDB credential need?

11 fields: Connection String, Host, Port, Database, User, Password, Auth Source, Use TLS/SSL, Allow Invalid Certificates, Replica Set Name, Use SRV (DNS Seedlist). Required: Database. The values come from your own MongoDB account.

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

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