Skip to main content
Select Actions to adjust the guide
Some actions may require additional configuration in the provider to be accessible. Choose the actions you need and the guide will be updated.
Action
Scope(s)
Loading actions…
Dynamic Guide URL
Scopes Selected
Separator
A Google Cloud project with Owner or Editor permissions is required to create OAuth credentials.

Create or select a Google Cloud project

To use Google Drive API with OAuth 2.0, you need a Google Cloud project.

1

Sign in to Google Cloud

Sign in to your Google Cloud Console.

2

Create or select a project

Select an existing project from the dropdown at the top of the page, or create a new one by clicking New Project and filling in the Project name, Organization, and Parent resource fields, then clicking Create.

Enable the required Google APIs

Navigate to APIs & Services > Library, search for each API below, click on it, then click Enable. If it already shows Manage, the API is already enabled. Both APIs must be enabled before they will appear as selectable options when restricting the API Key in a later step.

  • Google Drive API
  • Google Picker API

Configure Google Auth Platform

Before creating OAuth credentials, ensure Google Auth Platform is configured.

1

Navigate to Google Auth Platform

In the Google Cloud Console, go to APIs & Services > OAuth consent screen. This will open the Google Auth Platform dashboard.

2

Start configuration

If you have already configured Auth Platform (the OAuth Overview page with usage metrics is shown), skip this step and navigate to the Branding page from the sidebar. Otherwise, you will see a Get started button — click it to begin the configuration process.

3

Enter app information

Fill in the required fields for your application.

  • App name: Enter a name for your application (e.g., StackOne Integration).
  • User support email: Select an email for user inquiries.
  • Click Next to continue.
4

Select audience

Choose the appropriate user type for your application.

  • Internal: Only users within your Google Workspace organization can authorize (no app verification required).
  • External: Any Google account can authorize (requires app verification for production use).
  • Click Next to continue.
5

Enter contact information

Provide email addresses for Google to notify you about any changes to your project. Click Next to continue.

6

Finish configuration

Review your settings, agree to the Google API Services User Data Policy, and click Create to complete the setup.

Configure scopes

In Google Auth Platform, go to Data Access and click Add or Remove Scopes to configure the OAuth scopes your application needs.

1

Add scopes

Enables actions: Check Permissions, Copy File, Create Comment, Create File, Create Permission, Create Reply, Create Shared Drive, Delete Comment, Delete File, Delete Permission, Delete Reply, Delete Revision, Delete Shared Drive, Download Unified File, Empty Trash, Generate IDs, Get About, Get Access Proposal, Get Changes Start Page Token, Get Comment, Get File, Get Permission, Get Reply, Get Revision, Get Shared Drive, Get Unified Credentials, Get Unified Drive, Get Unified File, Get Unified Folder, Get Unified Role, Hide Shared Drive, List Access Proposals, List Changes, List Comments, List Files, List Permissions, List Replies, List Revisions, List Shared Drives, List Unified Drives, List Unified Files, List Unified Folders, List Unified Resource Types, List Unified Resource Users, List Unified Roles, Resolve Access Proposal, Unhide Shared Drive, Update Comment, Update File, Update Permission, Update Reply, Update Revision, Update Shared Drive, Upload File (Multipart), Upload File (Resumable), Upload File (Simple), Upload Unified File

Add the required Google Drive scopes for your integration.

2

Select scopes from the list

In the Update selected scopes side panel that opens, check the required scopes from the list.

3

Manually add scopes (if needed)

If a required scope is not shown in the list, use the Manually add scopes section.

  • Enter the full scope URL in the input field.
  • Click Add to table.
4

Apply and save

Confirm and persist your scope configuration.

  • Click Update to apply the selected scopes. The side panel will close.
  • On the Data Access page, click Save to persist the scope configuration.

Create OAuth 2.0 client credentials

Set up OAuth client credentials to authenticate with Google Drive API. If you already have an existing OAuth 2.0 client, you can reuse it by adding the StackOne redirect URI and generating a new secret.

1

Navigate to Credentials

In the Google Cloud Console, go to APIs & Services > Credentials.

2

Option A — Create a new OAuth client

Skip this step if you are using an existing client.

  • Click + Create Credentials and select OAuth client ID.
  • Select Web application as the application type.
  • Enter a Name for your OAuth client (e.g., StackOne Drive Integration).
  • Under Authorized redirect URIs, click Add URI and enter https://api.stackone.com/connect/oauth2/googledrive/callback.
  • Click Create. A dialog will display your Client ID and Client Secret — copy and store them securely.
3

Option B — Use an existing OAuth client

Skip this step if you created a new client above.

  • Click on your existing OAuth 2.0 client ID from the list.
  • Under Authorized redirect URIs, click Add URI, enter https://api.stackone.com/connect/oauth2/googledrive/callback, and click Save.
  • Under Client secrets, click + Add secret to generate a new secret. Copy it and store it securely — it will not be shown again.
  • Your Client ID is shown on the same page under Additional information.

Find your App ID and API key

The File Picker integration requires an App ID and API key in addition to OAuth credentials.

1

Find the App ID

The App ID is your Google Cloud project number.

  • Navigate to IAM & Admin > Settings from the left sidebar.
  • Copy the Project number value.
2

Create an API key

Create an API key restricted to both the Google Picker API and the Google Drive API. The Create API key dialog requires a name and at least one API restriction before the key can be used, and both APIs must already be enabled in your project (see the previous step) before they appear in the dropdown.

  • Navigate to APIs & Services > Credentials.
  • Click + Create Credentials and select API key.
  • In the Create API key dialog, enter a Name for the key (e.g. StackOne File Picker).
  • Under Select API restrictions, choose both Google Picker API and Google Drive API from the dropdown (this field is required — leaving it unset triggers an “API selection required” error). If either entry is missing from the list, go back and enable that API in APIs & Services > Library first.
  • Leave Authenticate API calls through a service account disabled unless your integration specifically requires service account authentication.
  • Under Application restrictions, leave the default None selected.
  • Click Create. The API key created dialog will appear with your key under Your API key — use the copy icon next to the value to copy it, store it securely for use later, then click Close.

Creating the StackOne Connector Profile

To create the Connector Profile in StackOne for Google Drive:
1

Navigate to Connector Profiles

Login to StackOne and navigate to Connector Profiles
2

Create New Connector Profile

  • Click + Connector Profile
  • Search for and select Google Drive
  • Select Type as OAuth2 - File Picker
  • Fill out the fields using details retrieved from your provider:
    • Client ID
    • Client Secret
    • Scopes (Optional)
    • App ID
    • API Key
  • (Optional) Select Actions to be enabled for this Connector Profile
  • Click Create profile
Congratulations! The new Connector Profile will now show up in your project ready to be used. You can now continue to Link Accounts for Google Drive.