BusyBot

Reference · Credentials

Google Calendar OAuth2 API credentials

Used by 1 BusyBot node.

Type googleCalendarOAuth2Api 4 fields

Fields

FieldTypeRequiredNotes
Client ID
clientId		 string Yes —
Client Secret
clientSecret		 password Yes —
Access Token
accessToken		 password Yes —
Refresh Token
refreshToken		 password No —

Setting up Google Calendar OAuth2 API

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

Nodes that use Google Calendar OAuth2 API

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