BusyBot
Search all guides

Reference · Credentials

Connect Jenkins to BusyBot

Used by 1 BusyBot node.

Type jenkinsApi 3 fields

Fields

FieldTypeRequiredNotes
Jenkins URL
baseUrl		 string Yes Base URL of your Jenkins server (e.g., https://jenkins.example.com).
Username
username		 string Yes —
API Token
apiToken		 password Yes Jenkins API token from User > Configure > API Token.

Setting up Jenkins API

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

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

What does a Jenkins credential need?

3 fields: Jenkins URL, Username, API Token. Required: Jenkins URL, Username, API Token. The values come from your own Jenkins account.

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

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