BusyBot
Search all guides

Reference · Credentials

Connect Cal.com to BusyBot

Used by 1 BusyBot node.

Type calApi 2 fields

Fields

FieldTypeRequiredNotes
API Key
apiKey		 password Yes Your Cal.com API key.
Host
host		 string No The Cal.com API host URL.

Setting up Cal.com API

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

One node: Cal.com Trigger. Create the credential once and select it in that node.

What does a Cal.com credential need?

2 fields: API Key, Host. Required: API Key. The values come from your own Cal.com account.

How are Cal.com 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 Cal.com API

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