BusyBot
Search all guides

Reference · Credentials

Connect Kling AI to BusyBot

Used by 1 BusyBot node.

Type klingAiApi 2 fields

Fields

FieldTypeRequiredNotes
Access Key
accessKey		 password Yes Kling AI Access Key from the API-key page. Combined with the Secret Key to sign the request JWT.
Secret Key
secretKey		 password Yes Kling AI Secret Key from the API-key page. Used to HS256-sign the JWT; stays server-side and is never sent to Kling directly.

Setting up Kling AI API

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

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

What does a Kling AI credential need?

2 fields: Access Key, Secret Key. Required: Access Key, Secret Key. The values come from your own Kling AI account.

How are Kling AI 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 Kling AI API

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