Reference · Credentials
Connect TOTP Secret to BusyBot
Used by 1 BusyBot node.
Type
totpApi 2 fields Fields
| Field | Type | Required | Notes |
|---|---|---|---|
Secretsecret | password | Yes | The base32-encoded shared secret for TOTP generation. |
Labellabel | string | No | Optional label in \ |
Setting up TOTP Secret
- In TOTP Secret, create the credential this connection needs — the values listed in the table above. These are issued from your own TOTP Secret account, usually under its developer, API or integrations settings.
- In BusyBot, open Credentials → Add credential and choose TOTP Secret.
- Paste each value into the matching field and save.
- Add the TOTP 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 TOTP Secret credentials?
One node: TOTP. Create the credential once and select it in that node.
What does a TOTP Secret credential need?
2 fields: Secret, Label. Required: Secret. The values come from your own TOTP Secret account.
How are TOTP Secret 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 TOTP Secret
One credential works across every node below — create it once and reuse it.