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 Sheets authentication

Prerequisites​

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

  • OAuth 2.0 Authorization code - Your Google email address and the password associated with your Google account.
  • Bring your own OAuth 2.0 app - The Client ID, Client secret, and Scopes of your application.
  • Service account - Service account key and Account email.
Note:

For more details regarding the different authentication types, refer to the How to connect to Google Workspace 365 activities guide.

If your account is not enabled by Google:

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

For more information on Google sheets documentation, refer to Google Sheets for Developers.

OAuth 2.0 Authorization code​

Scopes​

  • Mandatory scopes: openid, https://www.googleapis.com/auth/drive.
  • Default scopes: openid, https://www.googleapis.com/auth/userinfo.email, https://www.googleapis.com/auth/userinfo.profile, 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 Sheets data on your behalf. This may include read, write, modify, and delete data, depending on your Google Sheets permissions. You can always remove any access in your Google Account.

Adding the Google Sheets connection​

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

  1. Select Orchestrator from the product launcher.
  2. Select a folder, and then navigate to the Connections tab.
  3. Select Add connection.
  4. To open the connection creation page, select the connector from the list. You can use the search bar to find the connector.
  5. In the Authentication Type dropdown menu, select OAuth 2.0 Authorization code.
  6. 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 Sheets 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, https://www.googleapis.com/auth/drive.
  • Default scopes: openid, https://www.googleapis.com/auth/drive, https://www.googleapis.com/auth/userinfo.email, https://www.googleapis.com/auth/userinfo.profile.
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 Sheets data on your behalf. This may include read, write, modify and delete data, depending on your Google Sheets permissions. You can always remove any access in your Google Account.

Adding the Google Sheets connection​

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

  1. Select Orchestrator from the product launcher.
  2. Select a folder, and then navigate to the Connections tab.
  3. Select Add connection.
  4. To open the connection creation page, select the connector from the list. You can use the search bar to find the connector.
  5. In the Authentication Type dropdown menu, select Bring your own OAuth 2.0 app.
  6. 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.
  7. Select Connect.

Google Service Account​

Scopes​

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

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

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

Adding the Google Sheets connection​

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

  1. Select Orchestrator from the product launcher.
  2. Select a folder, and then navigate to the Connections tab.
  3. Select Add connection.
  4. To open the connection creation page, select the connector from the list. You can use the search bar to find the connector.
  5. In the Authentication Type dropdown menu, select Google Service Account.
  6. 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.
    Note:

    For more details on how to create a service account and key, check the Create a service account page in the Google documentation.

    • Account email - You Google account email.
  7. 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 (refer to Using OAuth 2.0 for Server-to-Server Applications). For more information, refer to Google's official documentation.

A list of reasons which can cause token expiry:

  • You have revoked your app's access.
  • 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/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 set by the admin 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 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, refer to Google's official 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