BusyBot
Search all guides

Reference · Credentials

Connect Google Calendar to BusyBot

Used by 2 BusyBot nodes.

Type googleCalendarOAuth2 5 fields

Fields

FieldTypeRequiredNotes
Access Token
accessToken		 password Yes Google OAuth2 access token with Calendar scope
Refresh Token
refreshToken		 password Yes Google OAuth2 refresh token for automatic renewal
Client ID
clientId		 string Yes Google OAuth2 client ID from the Google Cloud Console
Client Secret
clientSecret		 password Yes Google OAuth2 client secret from the Google Cloud Console
Token Expiry (Unix timestamp)
expiresAt		 string No Unix timestamp (seconds) when the access token expires. Managed automatically after refresh.

Setting up Google Calendar OAuth2

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

2 nodes: Google Calendar, Google Calendar Trigger. Create the credential once and every one of them can use it.

What does a Google Calendar credential need?

5 fields: Access Token, Refresh Token, Client ID, Client Secret, Token Expiry (Unix timestamp). Required: Access Token, Refresh Token, Client ID, Client Secret. The values come from your own Google Calendar account.

How are Google Calendar 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.

Does Google Calendar use OAuth?

Yes. This credential connects through OAuth (fields: Access Token, Refresh Token, Client ID, Client Secret, Token Expiry (Unix timestamp)): you approve access in Google Calendar, and the resulting tokens are stored encrypted like every other credential.

Nodes that use Google Calendar OAuth2

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