BusyBot
Search all guides

Reference · Credentials

Connect JWT to BusyBot

Used by 1 BusyBot node.

Type jwtApi 5 fields

Fields

FieldTypeRequiredNotes
Key Type
keyType		 options Yes Choose whether to use a shared secret passphrase (for HMAC) or PEM-encoded keys (for RSA/ECDSA/PS).
Secret
secret		 password No Shared HMAC secret. Required when Key Type is Passphrase.
Private Key
privateKey		 password No PEM-encoded private key for signing. Required when Key Type is PEM Key.
Public Key
publicKey		 password No PEM-encoded public key for verification. Required when Key Type is PEM Key.
Algorithm
algorithm		 options Yes Default signing/verification algorithm. Can be overridden per operation in the node options.

Setting up JWT Credential

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

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

What does a JWT credential need?

5 fields: Key Type, Secret, Private Key, Public Key, Algorithm. Required: Key Type, Algorithm. The values come from your own JWT account.

How are JWT 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 JWT Credential

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