BusyBot
Search all guides

Reference · Credentials

Connect Bitbucket to BusyBot

Used by 1 BusyBot node.

Type bitbucketApi 2 fields

Fields

FieldTypeRequiredNotes
Username
username		 string Yes Your Bitbucket username
App Password / Access Token
appPassword		 password Yes Your Bitbucket App Password or Access Token.

Setting up Bitbucket API

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

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

What does a Bitbucket credential need?

2 fields: Username, App Password / Access Token. Required: Username, App Password / Access Token. The values come from your own Bitbucket account.

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

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