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