BusyBot
Search all guides

Reference · Credentials

Connect Google Contacts to BusyBot

Used by 1 BusyBot node.

Type googleContactsOAuth2Api 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 Contacts OAuth2 API

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

One node: Google Contacts. Create the credential once and select it in that node.

What does a Google Contacts credential need?

4 fields: Client ID, Client Secret, Access Token, Refresh Token. Required: Client ID, Client Secret, Access Token. The values come from your own Google Contacts account.

How are Google Contacts 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 Contacts use OAuth?

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

Nodes that use Google Contacts OAuth2 API

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