Google has announced the deprecation of Less Secure Apps (LSAs) to connect to Google Workspace using a username and password as this authentication is not secure and does not meet the industry's best practices.

To know more about Google Less Secure Apps (LSAs) deprecation, see Google Less Secure Apps (LSA) deprecation

We provide a new version of the Email and Email Trigger packages with a new Control Room managed OAuth2 mode of authentication that you can use to automate Gmail. This authentication mode is secure and uses the centralized access token management from the Control Room. To ensure that your existing automations (bots) that are using Basic authentication to automate Gmail are supported after Basic authentication is deprecated, we recommend that you update the automations to use Control Room managed OAuth2 authentication mode.

To identify the Automation 360 automations that are using Basic authentication in the Email package or Email Trigger to automate Gmail, use the Bot Scanner to scan automations. This helps you to plan your efforts to update your existing automations in Automation 360.

Scan automations that use Email action for Gmail with Basic authentication

Update automations using Gmail with Basic authentication to Control Room managed OAuth2 mode of authentication

update automation using gmail with basic authentication to Control Room manged OAuth2

Perform the following steps to update the automations:
  1. Run Bot Scanner to identify automations that are using Basic authentication to automate Gmail. See Scan automations that use Email action for Gmail with Basic authentication.
  2. Set up an OAuth connection for Google Workspace in the Control Room.

    See Create OAuth connection.

  3. In the Bot editor, edit and update the impacted automations that are using Basic authentication in the Connect, Forward, Reply, Reply all, and Send actions of the Email package and Email Trigger.
    Note: Ensure you are using the latest version of the Email package and Email Trigger package.
    • Automations created using Email package: You can replace Basic authentication using the following options:
      • OAuth2 - Authorization code with PKCE: Attended authentication mode.
      • Control Room managed: Unattended authentication mode.
    • Automations created using Email trigger: You can replace Basic authentication with the Control Room managed OAuth2 mode of authentication.
  4. Verify that the updated automations can run or be deployed.