BusyBot
Search all guides

Reference · Credentials

Connect npm to BusyBot

Used by 1 BusyBot node.

Type npmApi 2 fields

Fields

FieldTypeRequiredNotes
Access Token
accessToken		 password No npm access token for authenticated operations.
Registry URL
registryUrl		 string No Custom registry URL for private registries.

Setting up npm API

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

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

What does a npm credential need?

2 fields: Access Token, Registry URL. The values come from your own npm account.

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

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