BusyBot
Search all guides

Reference · Credentials

Connect Bitly to BusyBot

Used by 1 BusyBot node.

Type bitlyOAuth2 4 fields

Fields

FieldTypeRequiredNotes
Access Token
accessToken		 password Yes OAuth2 access token from Bitly.
Refresh Token
refreshToken		 password No OAuth2 refresh token for automatic renewal.
Client ID
clientId		 string Yes OAuth2 client ID from Bitly app registration.
Client Secret
clientSecret		 password Yes OAuth2 client secret from Bitly app registration.

Setting up Bitly OAuth2

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

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

What does a Bitly credential need?

4 fields: Access Token, Refresh Token, Client ID, Client Secret. Required: Access Token, Client ID, Client Secret. The values come from your own Bitly account.

How are Bitly 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.

Does Bitly use OAuth?

Yes. This credential connects through OAuth (fields: Access Token, Refresh Token, Client ID, Client Secret): you approve access in Bitly, and the resulting tokens are stored encrypted like every other credential.

Nodes that use Bitly OAuth2

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