BusyBot
Search all guides

Reference · Credentials

Connect MySQL to BusyBot

Used by 1 BusyBot node.

Type mysqlApi 7 fields

Fields

FieldTypeRequiredNotes
Host
host		 string Yes —
Port
port		 number Yes —
Database
database		 string Yes —
User
user		 string Yes —
Password
password		 password Yes —
SSL
ssl		 boolean No —
SSL CA Certificate
sslCertificate		 password No —

Setting up MySQL

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

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

What does a MySQL credential need?

7 fields: Host, Port, Database, User, Password, SSL, SSL CA Certificate. Required: Host, Port, Database, User, Password. The values come from your own MySQL account.

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

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