Reference · Credentials
Connect SSH to BusyBot
Used by 1 BusyBot node.
Type
sshApi 7 fields Fields
| Field | Type | Required | Notes |
|---|---|---|---|
Hosthost | string | Yes | — |
Portport | number | Yes | — |
Usernameusername | string | Yes | — |
Auth TypeauthType | options | Yes | — |
Passwordpassword | password | No | — |
Private KeyprivateKey | string | No | — |
Passphrasepassphrase | password | No | — |
Setting up SSH
- In SSH, create the credential this connection needs — the values listed in the table above. These are issued from your own SSH account, usually under its developer, API or integrations settings.
- In BusyBot, open Credentials → Add credential and choose SSH.
- Paste each value into the matching field and save.
- Add the SSH 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 SSH credentials?
One node: SSH. Create the credential once and select it in that node.
What does a SSH credential need?
7 fields: Host, Port, Username, Auth Type, Password, Private Key, Passphrase. Required: Host, Port, Username, Auth Type. The values come from your own SSH account.
How are SSH 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 SSH
One credential works across every node below — create it once and reuse it.