Reference · Credentials
Google Cloud Storage OAuth2 credentials
Used by 1 BusyBot node.
Type
googleCloudStorageOAuth2 5 fields Fields
| Field | Type | Required | Notes |
|---|---|---|---|
Access TokenaccessToken | password | Yes | Google OAuth2 access token with Cloud Storage scopes |
Refresh TokenrefreshToken | password | Yes | Google OAuth2 refresh token for automatic renewal |
Client IDclientId | string | Yes | Google OAuth2 client ID from Google Cloud Console |
Client SecretclientSecret | password | Yes | Google OAuth2 client secret from 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 Cloud Storage OAuth2
- In Google Cloud Storage OAuth2, create the credential this connection needs — the values listed in the table above. These are issued from your own Google Cloud Storage OAuth2 account, usually under its developer, API or integrations settings.
- In BusyBot, open Credentials → Add credential and choose Google Cloud Storage OAuth2.
- Paste each value into the matching field and save.
- Add the Google Cloud Storage 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 Cloud Storage OAuth2
One credential works across every node below — create it once and reuse it.