Using the Connect action for Google packages

Use the Connect action to establish a connection with the Google server in order to use other actions from that same package to automate tasks. All of the fields in this action accept a credential from the Credential Vault, variable, or a user-input value.

Prerequisites

Configure the OAuth settings in the Google Cloud Platform and retrieve the credentials necessary to connect Automation Anywhere Enterprise with your Google G Suite applications.

If you have not already done so, create a project.
Enable the APIs for the Google G Suite applications you want to automate, such as the Google Drive API, Google Calendar API, and Google Sheets API.
Do the steps in Setting up OAuth 2.0 to generate the Client ID and Secret.
Note:
- Select the Web application option.
- Add this authorized redirect URI: http://localhost:8888/Callback
Do these steps to set up user consent for the username that you will use to connect to the Automation Anywhere Enterprise.

Procedure

In the Actions palette, double-click or drag the Connect action from the package you want to use.
In the Username field, you can provide a valid username or select the credential or credential variable that contains your Google username. To enter a value, click Insecure string.
If you are configuring the Connect action for the Google Calendar or Google Sheets package, enter a session name.
In the Client Id field, select the credential or credential variable that contains the client ID. To enter a value, click Insecure string.
In the Redirect URI field, enter http://localhost:8888/Callback

Note: For the Google Sheets package, the Redirect URI attribute is not supported. Enter the fixed redirect URL directly in Google Cloud Platform: http://localhost:8888/Callback
In the Client secret field, select the credential or credential variable that contains the access token. To enter a value, click Insecure string.
For Google Sheets, you can specify the wait time (in minutes) in the Wait for action to complete (In minutes) field when performing actions such as Get, Set, or Delete. By default, the wait time is 10 minutes.
If the Google sheet does not open within the time you specify, the task proceeds to execute the next set of actions.
Note: When you use Connect action to connect to the Google server, the option Wait for action to complete (In minutes) is only supported in Google Sheets package.
Click Save.
After you add actions from a specific Google package, use the Disconnect action from that same Google package to terminate the connection.

Next steps

The first time the bot runs, the Google login window is displayed. You must select the Google account and approve the requested access permissions.

The token file gets generated for the first time after you provide the access permissions when the bot gets deployed. It is created based on values that you provide in the Username, Client Id and Client secret field, and asks for credentials only the first time to provide the access permission. Next time it uses the same token file to connect to the Google Sheets.

The token file is located at C:\Users\<username>\AppData\Local\AutomationAnywhere\G-SuitAuth, where C:\Users\<username> is the user home directory of the respective system.

If you enter the correct credentials when providing access permissions for the first time and can connect to the Google Sheets successfully, then next time if there is a change in only the password, you need not delete the token file as it will work as expected.

Use other the actions from the same Google package to automate tasks. To use actions from another Google packages, establish a connection using the Connect action from that package.

Automation 360

Using the Connect action for Google packages