BusyBot
Search all guides

Reference · Credentials

Connect ERPNext to BusyBot

Used by 1 BusyBot node.

Type erpNextApi 6 fields

Fields

FieldTypeRequiredNotes
API Key
apiKey		 password Yes —
API Secret
apiSecret		 password Yes —
Environment
environment		 options Yes —
Subdomain
subdomain		 string No mycompany
Domain
domain		 options No —
Domain (Self-Hosted)
domainSelfHosted		 string No https://erp.mydomain.com

Setting up ERPNext API

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

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

What does a ERPNext credential need?

6 fields: API Key, API Secret, Environment, Subdomain, Domain, Domain (Self-Hosted). Required: API Key, API Secret, Environment. The values come from your own ERPNext account.

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

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