BusyBot
Search all guides

Reference · Credentials

Connect CrateDB to BusyBot

Used by 1 BusyBot node.

Type crateDbApi 6 fields

Fields

FieldTypeRequiredNotes
Host
host		 string Yes —
Port
port		 number Yes —
Database
database		 string Yes —
User
user		 string Yes —
Password
password		 password No —
SSL
ssl		 options No —

Setting up CrateDB

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

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

What does a CrateDB credential need?

6 fields: Host, Port, Database, User, Password, SSL. Required: Host, Port, Database, User. The values come from your own CrateDB account.

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

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