UiPath Documentation
integration-service
latest
false
UiPath logo, featuring letters U and I in white

Integration Service user guide

Last updated Mar 16, 2026

Google Drive authentication

Prerequisites​

Depending on the authentication type you select, you need one of the following credentials:

  • OAuth 2.0 Authorization code - connects to the UiPath public application with your Google email address and the password associated with your Google account.
  • Bring your own OAuth 2.0 app - connects to a private application you create.
  • Google Service Account - connects using the service account key and account email.
Note:

For more details on the different authentication types, check How to connect to Google Workspace 365 activities.

Once authenticated, you can use the connection to access the different functionalities that Google Drive offers.

If Google did not enable your account:

  • Reach out to your administrator for approvals on creating connections.
  • Enable permission by checking the options available to allow creating a connection.

For more details on Google Drive, check the Google Drive developer documentation.

OAuth 2.0 Authorization code​

Scopes​

  • Mandatory scopes: openid and https://www.googleapis.com/auth/drive.
  • Default scopes: openid, https://www.googleapis.com/auth/userinfo.email, https://www.googleapis.com/auth/userinfo.profile, and https://www.googleapis.com/auth/drive.

To add more granular permissions, refer to the Google activities documentation.

Connecting allows UiPath products to interact with Google Drive data on your behalf. This may include read, write, modify, and delete data, depending on your Google Drive permissions. You can always remove any access in your Google Account.

Adding the Google Drive connection​

To create a connection to your Google Drive, perform the following steps:

  1. In Automation Cloud, select Integration Service from the rail menu.
  2. From the Connectors list, select Google Drive. You can also use the search bar to narrow down the connector.
  3. Select the Connect to Google Drive button, which redirects you to the connection page.
  4. In the Authentication Type dropdown menu, select OAuth 2.0 Authorization code.
  5. Select Connect.

Bring your own OAuth 2.0 app​

The Bring your own OAuth 2.0 app authentication type allows you to connect UiPath to Google Drive using a custom OAuth application. You can create and manage this custom app in Google Cloud Console, instead of the default UiPath public app. This gives you greater control over consent, scopes, and security policies, and helps avoid refresh-token limits associated with shared OAuth client IDs.

Scopes​

Mandatory scopes: openid and https://www.googleapis.com/auth/drive.

Note:

If you authenticate using Bring your own OAuth 2.0 app, you benefit by default from the scopes configured at app creation. If you want to use the default app permissions, you can declare a common scope. This means you use only the permissions configured for that application. You can also declare additional scopes at connection creation, using the Scopes field. You will then be asked to grant the additional consent during sign-in.

To add more granular permissions, refer to the Google activities documentation.

Connecting allows UiPath products to interact with Google Drive data on your behalf. This may include read, write, modify and delete data, depending on your Google Drive permissions. You can always remove any access in your Google Account.

Adding the Google Drive connection​

To create a connection to your Google Drive, perform the following steps:

  1. In Automation Cloud, select Integration Service from the rail menu.
  2. From the Connectors list, select Google Drive. You can also use the search bar to narrow down the connector.
  3. Select the Connect to Google Drive button, which redirects you to the connection page.
  4. In the Authentication Type dropdown menu, select Bring your own OAuth 2.0 app.
  5. Configure the following:
    • Client ID - The client ID from the OAuth 2.0 Client IDs section in your Google Cloud Console credentials.
    • Client secret - The client Secret from your Google Cloud Console credentials.
  6. Select Connect.

Google Service Account​

Scopes​

  • Mandatory scopes: https://www.googleapis.com/auth/drive
  • Default scopes: https://www.googleapis.com/auth/drive

To add more granular permissions, refer to the Google activities documentation.

Connecting allows UiPath products to interact with Google Drive data on your behalf. This may include read, write, modify and delete data, depending on your Google Drive permissions. You can always remove any access in your Google Account.

Adding the Google Drive connection​

To create a connection to your Google Drive, perform the following steps:

  1. In Automation Cloud, select Integration Service from the rail menu.

  2. From the Connectors list, select Google Drive. You can also use the search bar to narrow down the connector.

  3. Select the Connect to Google Drive button, which redirects you to the connection page.

  4. In the Authentication Type dropdown menu, select Google Service Account.

  5. Configure the following:

    • Service Account Key - Paste the complete JSON key file downloaded from Google Cloud Console for your service account. For more details, check Create a service account key in the official Google documentation.
    • Account email - The service account email, for example, my-sa@project.iam.gserviceaccount.com.
      Note:

      If you impersonate a user using domain-wide delegation, provide the user email to impersonate and ensure domain-wide delegation is configured in the Admin console.

  6. Select Connect.

Refresh tokens for OAuth applications​

Google has refresh token limitations for individual OAuth 2.0 client IDs. If the limit is reached, creating a new refresh token automatically invalidates the oldest refresh token without warning. This limit does not apply to service accounts. For more details, refer to Using OAuth 2.0 for Server-to-Server Applications and the official Google documentation.

A list of reasons which can cause token expiry:

  • You have revoked the access of your application.
  • The refresh token has not been used for six months.
  • You need to change passwords and the refresh token contains Gmail scopes.
  • Your account has exceeded a maximum number of granted (live) refresh tokens.
    • If you request a new token after the limit is exceeded, your old connection, based on a previously granted token, will expire. Only the new connection or the latest edited or reauthenticated connection (with the latest token) will work.
  • An admin has set any of the services requested in your application's scopes to Restricted (the error is admin_policy_enforced).
  • For Google Cloud Platform APIs, the session length that the admin set could have been exceeded.
Note:

The limit is currently set to 100 refresh tokens per Google account per OAuth 2.0 client ID. This number can be subject to change. For the latest information, always check the official Google documentation.

There is a larger limit on the total number of refresh tokens a user account or service account can have across all clients. Regular users won't exceed this limit, but a developer account used to test an implementation might.

To make sure this limit is not exceeded, UiPath offers users the ability to create their own OAuth applications and connect using the Bring your own app authentication type. Make sure to follow the best practices from Google when creating your OAuth application. For details on how to create an OAuth application, check the official Google documentation.

Note:

Token invalidation results in failed connections and automations are unable to run without fixing connections.

Was this page helpful?

Connect

Need help? Support

Want to learn? UiPath Academy

Have questions? UiPath Forum

Stay updated