Reference · Credentials
Connect Paddle to BusyBot
Used by 1 BusyBot node.
Type
paddleApi 3 fields Fields
| Field | Type | Required | Notes |
|---|---|---|---|
Vendor Auth CodevendorAuthCode | password | Yes | — |
Vendor IDvendorId | string | Yes | — |
Use Sandboxsandbox | boolean | No | — |
Setting up Paddle API
- In Paddle API, create the credential this connection needs — the values listed in the table above. These are issued from your own Paddle API account, usually under its developer, API or integrations settings.
- In BusyBot, open Credentials → Add credential and choose Paddle API.
- Paste each value into the matching field and save.
- Add the Paddle 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 Paddle credentials?
One node: Paddle. Create the credential once and select it in that node.
What does a Paddle credential need?
3 fields: Vendor Auth Code, Vendor ID, Use Sandbox. Required: Vendor Auth Code, Vendor ID. The values come from your own Paddle account.
How are Paddle 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 Paddle API
One credential works across every node below — create it once and reuse it.