BusyBot

Reference · Credentials

Google Drive OAuth2 credentials

Used by 2 BusyBot nodes.

Type googleDriveOAuth2 5 fields

The Google Drive OAuth2 credential connects as a specific Google user who has granted consent, holding an access token plus a refresh token that renews it. It needs an OAuth client from a Google Cloud project with the Drive API enabled.

Fields

FieldTypeRequiredNotes
Access Token
accessToken		 password Yes Google OAuth2 access token
Refresh Token
refreshToken		 password Yes Google OAuth2 refresh token for automatic renewal
Client ID
clientId		 string Yes Google OAuth2 client ID from Google Cloud Console
Client Secret
clientSecret		 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.

Getting your credentials

  1. In the Google Cloud Console, select or create a project.
  2. Enable the Google Drive API for that project.
  3. Configure the OAuth consent screen with the Drive scopes your workflow needs, adding test users while the app is unverified.
  4. Create an OAuth 2.0 Client ID of type Web application and register BusyBot’s redirect URL against it.
  5. Copy the Client ID and Client Secret into the credential.
  6. Complete the authorisation flow so an access token and refresh token are stored.

Permissions and scopes

Drive offers narrower scopes than full access — including one limited to files the app itself created. Prefer the narrowest that covers your operations; broad Drive scopes attract stricter Google verification requirements.

Troubleshooting

  • Access revoked after about a week — the consent screen is in testing mode. Publish the app for durable refresh tokens.
  • File not found — the authorising user does not have access to it, or the file ID is wrong.
  • redirect_uri_mismatch — the redirect URI on the OAuth client must match the flow’s exactly.
  • Insufficient permission on upload — a read-only scope was granted; re-consent with a scope that permits writes.

Frequently asked questions

Which files can it see?

Whatever the authorising user can see, subject to the scopes granted. A scope limited to app-created files will not show the rest of their Drive.

Why does access keep expiring?

An unpublished consent screen in testing mode issues short-lived refresh tokens. Publishing the app is the fix.

How is this different from a service account?

This acts as the person who consented. A service account is its own identity and must be given access to files explicitly by sharing them with its email address.

Nodes that use Google Drive OAuth2

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

Last updated . Spotted something wrong? Tell us.