How to use Google Workspace activities without Integration Service

About

You can now use the newer Google Workspace activities even if you don't have Integration Service, through GSuite Application Scope.

The Google Workspace activities designed specifically for Integration Service feature a Connection field, which enables you to choose a connection created through an Integration Service connector. When used inside GSuite Application Scope, the activities inherit the connection information from the Scope.

Authentication and projects types matrix

Google Workspace
	Cloud		On-Prem
	GSuite Application Scope	Integration Service	GSuite Application Scope	Integration Service
Cross-platform
API Key	❌	❌	❌	❌
OAuth - BYOA	❌	✅	❌	❌
OAuth - UiPath App	❌	✅	❌	❌
Service Account	❌	❌	❌	❌
Windows
API Key	✅	❌	✅	❌
OAuth - BYOA	✅	✅	✅	❌
OAuth - UiPath App	✅	✅	✅	❌
Service Account	✅	❌	✅	❌

Connection methods

There are two ways to set up a connection in the GSuite Application Scope activity.

Connection method	Description	Benefits	Disadvantages
Asset (recommended)	Uses an Orchestrator Asset to store the connection together with the Scope configuration. The asset uses JSON format. Every time it is used, the activity retrieves the configuration from the asset. Based on the asset configuration, the scope identifies the authentication type and hides unnecessary fields. If the asset JSON is not set correctly, a validation error appears.	Activities benefit from design-time lookups and can discover files, folders, lists, ranges, and others. The connection is easily transferable, as credentials are not passed between users in plain text. Can be configured by an admin. More secure, because credentials do not reach the Studio workflow.	Requires an advanced user to configure the asset. Not easy to set up for a citizen developer.
Properties Panel	Use the existing Properties panel to configure the connection credentials. The configuration can be added in plain text or through variables.	Easier to use. Keeps backward compatibility.
Properties Panel (plain text)	Configure the Properties panel with plain text values. This is not recommended.	Activities benefit from design-time lookups and can discover files, folders, lists, ranges, and others. Easier to use and keeps backward compatibility.	Less secure, as credentials must be passed between users in plain text.
Properties Panel (variables)	Configure the Properties panel with variables.	More secure, as credentials do not reach the Studio workflow. Easier to use and keeps backward compatibility.	Activities cannot discover resources at design time.

GSuite Application Scope asset format

{
    "ApiKey": "",
    "OAuth2ConnectionData": {
        "OAuth2AppData": {
            "ClientId": "",
            "ClientSecret": ""
        }
    },
    "SacConnectionData": {
        "EmailAddress": "",
        "KeyPath": "",
        "ServiceAccountEmail": "",
        "Password": "notasecret",
        "BucketId": "",
        "HasDomainWideAccess": true | false
    },
   "AuthenticationMethod": "oauth2" | "sac" | "apikey"
}

Limitations

The following features are not available when using activities inside GSuite Application Scope: triggers, bindings, and override experience.

Token refresh

There is no service available to refresh your connection tokens, like the one available in Integration Service.

If the Authorization Token isn't refreshed for a certain number of days, it expires, and you must re-authenticate. To avoid the expiration of authorization tokens, run a robot with that specific connection. Running an automation with the Scope activity refreshes the authorization token.

Additional OAuth 2.0 resources:

• Using OAuth 2.0 to Access Google APIs | Authorization | Google for Developers