Reference · Credentials
Connect Bitwarden to BusyBot
Used by 1 BusyBot node.
Type
bitwardenApi 4 fields Fields
| Field | Type | Required | Notes |
|---|---|---|---|
Client IDclientId | string | Yes | — |
Client SecretclientSecret | password | Yes | — |
Environmentenvironment | options | Yes | — |
Self-Hosted Domaindomain | string | No | https://bitwarden.mydomain.com |
Setting up Bitwarden API
- In Bitwarden API, create the credential this connection needs — the values listed in the table above. These are issued from your own Bitwarden API account, usually under its developer, API or integrations settings.
- In BusyBot, open Credentials → Add credential and choose Bitwarden API.
- Paste each value into the matching field and save.
- Add the Bitwarden 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 Bitwarden credentials?
One node: Bitwarden. Create the credential once and select it in that node.
What does a Bitwarden credential need?
4 fields: Client ID, Client Secret, Environment, Self-Hosted Domain. Required: Client ID, Client Secret, Environment. The values come from your own Bitwarden account.
How are Bitwarden 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 Bitwarden API
One credential works across every node below — create it once and reuse it.