Reference · Credentials
Connect UpLead to BusyBot
Used by 1 BusyBot node.
Type
upleadApi 1 field Fields
| Field | Type | Required | Notes |
|---|---|---|---|
API KeyapiKey | password | Yes | UpLead API key. |
Setting up UpLead API
- In UpLead API, create the credential this connection needs — the API Key shown above. These are issued from your own UpLead API account, usually under its developer, API or integrations settings.
- In BusyBot, open Credentials → Add credential and choose UpLead API.
- Paste each value into the matching field and save.
- Add the Uplead 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 UpLead credentials?
One node: Uplead. Create the credential once and select it in that node.
What does a UpLead credential need?
One field: API Key. Required: API Key. The values come from your own UpLead account.
How are UpLead 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 UpLead API
One credential works across every node below — create it once and reuse it.