Google Drive connector

With the Google Drive® connector, you can use commands in a chain to manage files and folders in Google Drive. For example, with this connector, you can:

• Search files in Google Drive
• Upload and download files
• Create or delete files and folders

Note: This connector's commands manage files stored in Google Drive, not files saved in Google Workspace® products such as Google Docs®, Sheets®, or Slides®.

Prerequisites

To enable the connection, the connector uses the Google Drive REST API. To set up the connector, you'll need:

• A dedicated Google® web application with OAuth consent and API access enabled
• The integration project's OAuth client ID and secret
• Pop-ups enabled on your browser
• The project's redirect URI:
  • PROD: https://h.app.wdesk.com/s/wdata/oc/app/oauth/callback
  • EU: https://h.eu.wdesk.com/s/wdata/oc/app/oauth/callback
  • APAC: https://h.apac.wdesk.com/s/wdata/oc/app/oauth/callback

Create a Google web application

To set up the connector, first create a Google web application with OAuth consent and API access enabled. The connector uses the application's OAuth client ID and secret to connect to the Google Drive API.

Step 1. Select or create a project

In the Google APIs developer console, select or create a project to use with the connector. To create a project:

1. In the toolbar, click Select a project or the current project's name, and then click New Project.
   
2. In Project name, enter a unique name to help identify the integration.
3. In Location, select your organization so others can use the project.
4. Click Create.
   
   

Step 2. Enable API access

1. Select the Library tab.
2. Search for and select Google Drive API.
3. Under Google Drive API, click Enable.
   
   
   

Step 3. Create the OAuth client ID and secret

1. On the OAuth consent screen tab, select Internal, and click Create.
   
2. Under App information, enter the application's name and user support email address to help identify the app when authenticating the connector.
3. Under App domain, add an authorized domain of wdesk.com.
   
4. Under Developer contact information, enter the email address Google should send any updates to regarding the project, and click Save and Continue.
5. Under Scopes and Optional info, click Save and Continue without adding any scopes or optional information.

   Note: No scopes or optional information are required for an application with internal users.

6. Under Summary, review and edit the OAuth consent screen details as necessary, and click Back to Dashboard.
7. On the Credentials tab, click Create credentials, and select OAuth client ID.
   
8. Under Application type, select Web application.
   
9. Enter a unique name to help identify the OAuth credentials.
10. Under Authorized JavaScript origins:
    • In North America, add https://h.app.wdesk.com
    • In the European Union, add https://h.eu.wdesk.com
    • In APAC, add https://h.apac.wdesk.com
11. Under Authorized redirect URIs:
    • In North America, add https://h.app.wdesk.com/s/wdata/oc/app/oauth/callback
    • In the European Union, add https://h.eu.wdesk.com/s/wdata/oc/app/oauth/callback
    • In APAC, add https://h.apac.wdesk.com/s/wdata/oc/app/oauth/callback
12. Click Create, and note the client ID and secret.

Set up the Google Drive connector

Note: To make the connector available for use in your organization's chains, an org security administrator first enables it from Configuration.

1. From Chain Builder, click Connections  compare_arrows, and then Create at the top right.
2. Under BizApp Connection, select Google Drive and the default CloudRunner.
   
3. Under Basic Info, enter a unique name and description to help identify the connector.
4. Under OAuth, enter the client ID and secret for the connector's Google integration project.
   

   Note: All sensitive credentials are automatically encrypted and stored at Advanced Encryption Standard (AES)-256 encryption.

5. Click Connect, and authorize the connector's access to your Google account.

   Note: To ensure Google can authorize the connector's access, enable browser pop-ups.

6. Select the environments to use with the connection, and click Save.
7. To test the connection, create and run a chain with the connector's Download File command, and verify it returns a valid output.

Troubleshooting

If the connection to Google Drive fails:

• Verify the integration project's client ID and secret. In the Google APIs developer console, the project's client ID and secret appear on the Credentials tab.
• Verify the project's authorized Javascript origin from above
• Ensure the project's redirect URI from above
• Verify the project has access to the Google Drive API enabled