Authenticating Google connectors
At Tray.io, we use the Google OAuth2 API to enable our customers to authenticate into Google applications when building workflows on the Tray Platform.
Due to particulars around how the API works, for certain Google services, you will need to whitelist the Tray.io app in the G-Suite admin interface. These services are:
Step 1 - Whitelisting the Tray.io appCopy
Before proceeding with the authentication of your Google accounts, it's essential to whitelist the Tray.io OAuth2 application. This security measure ensures that only authentications created with the Tray.io app are permitted, enhancing the overall security of your Google accounts and applications.
Note: Whitelisting does not grant access to your Google accounts; it only allows authentications created with the Tray.io app.
Prerequisites: Ensure you have super admin permissions before following the instructions below.
To whitelist the Tray.io OAuth2 application, follow these specific instructions using the G-Suite admin interface:
Log in to the G-Suite admin console.
Navigate to Security > Access and data control > API controls from the menu bar.
On the App access control page, click the MANAGE THIRD-PARTY APP ACCESS button.
Click the Add app button on the App access control page and choose OAuth App Name or Client ID from the available options.
Enter the Client ID:
597325623219-f23k7dhk377f8bvamo2e6klu1i37tco7.apps.googleusercontent.comin the search bar and click the SEARCH button.
Under the App name select the tray.io app.
Check the boxes for the client IDs you want to configure, then click Select.
Select the organization you would like to configure access for and click CONTINUE.
Choose the type of access the Tray.io app has to Google data and click CONTINUE.
Review the configured settings
Upon successful configuration, the Tray.io app should be visible under the Configured apps list.
Step 2 - Creating the AuthenticationsCopy
Once you have whitelisted the Tray.io OAuth2 app, you will now be able to create authentications for Gmail, BigQuery and AdWords.
For each service you wish to use, please see the individual connector pages where you will find instructions on how to authenticate and manage the specific access scopes you wish to give (read/write files, edit metadata etc.)
Notes for Embedded customersCopy
Custom OAuth appsCopy
You can create a custom OAuth app in order to White-label the authentication dialog for your integrations.
In order to use Google OAuth in an Embedded Solution and to access Google users’ data, Google requires 3rd party applications to validate domain ownership with their Authentication Server (full google docs here). Therefore, we need you to provide a subdomain that you would like to use, for example: *.integrations.acme.com.
The required steps are outlined below: