BusyBot
Search all guides

Reference · Credentials

Connect Cockpit to BusyBot

Used by 1 BusyBot node.

Type cockpitApi 2 fields

Fields

FieldTypeRequiredNotes
Cockpit URL
url		 string Yes Base URL of your Cockpit CMS instance.
Access Token
accessToken		 password Yes API access token from Cockpit settings.

Setting up Cockpit API

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

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

What does a Cockpit credential need?

2 fields: Cockpit URL, Access Token. Required: Cockpit URL, Access Token. The values come from your own Cockpit account.

How are Cockpit 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 Cockpit API

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