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