Reference · Credentials
JWT Credential credentials
Used by 1 BusyBot node.
Type
jwtApi 5 fields Fields
| Field | Type | Required | Notes |
|---|---|---|---|
Key TypekeyType | options | Yes | Choose whether to use a shared secret passphrase (for HMAC) or PEM-encoded keys (for RSA/ECDSA/PS). |
Secretsecret | password | No | Shared HMAC secret. Required when Key Type is Passphrase. |
Private KeyprivateKey | password | No | PEM-encoded private key for signing. Required when Key Type is PEM Key. |
Public KeypublicKey | password | No | PEM-encoded public key for verification. Required when Key Type is PEM Key. |
Algorithmalgorithm | options | Yes | Default signing/verification algorithm. Can be overridden per operation in the node options. |
Setting up JWT Credential
- 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.
- In BusyBot, open Credentials → Add credential and choose JWT Credential.
- Paste each value into the matching field and save.
- 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 and are never shown again after saving.
- 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.
Nodes that use JWT Credential
One credential works across every node below — create it once and reuse it.