Skip to main content
The steps in this guide require Admin or Owner privileges within Google Cloud.

​
Create or select a Google Cloud project

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

1

Sign in to Google Cloud

Sign in to your Google Cloud Console.

Google Cloud Console Sign In
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.

Google Cloud Console Create Project

​
Enable the Cloud Translation API

Enable the Cloud Translation API for your project. This step is required whether you created a new project or selected an existing one.

Google Cloud Console Enable Cloud Translation API
1

Open the API Library

In the Google Cloud Console, navigate to APIs & Services > Library.

2

Enable Cloud Translation API

Search for “Cloud Translation API” and click on it.

  • New project: Click Enable to activate the API.
  • Existing project: If the API is already enabled, the button will show Manage. If it shows Enable, click it to enable the API.

​
Configure Google Auth Platform

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

1

Navigate to Google Auth Platform

In the Google Cloud Console, go to APIs & Services > OAuth consent screen from the left sidebar. This will open the Google Auth Platform overview page.

2

Start configuration

If you have already configured the 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.

  • App name: Enter a name for your application (e.g., StackOne Integration).
  • User support email: Select an email address for user enquiries.
  • Click Next to continue.
  • Note: If you already have an existing OAuth consent screen configuration, you can edit the details in this and the following steps.
Enter branding information
4

Select audience

Choose the appropriate user type, or go to the Audience page from the left sidebar to select the user type.

  • Internal: Only users within your Google Workspace organisation can authorise (no app verification required).
  • External: Any Google account can authorise (requires app verification for production use).
Select audience
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 the Google Auth Platform, go to Data Access and click Add or Remove Scopes to configure the OAuth scopes your application needs.

Select scopes
1

Add scopes

Enables actions: Adaptive MT Translate, Batch Translate Document, Batch Translate Text, Create Adaptive MT Dataset, Create Glossary, Create Glossary Entry, Delete Adaptive MT Dataset, Delete Glossary, Delete Glossary Entry, Detect Language, Get Glossary, Get Glossary Entry, Import Adaptive MT File, List Adaptive MT Datasets, List Glossaries, List Glossary Entries, List Supported Languages, Romanize Text, Translate Document, Translate Text, Update Glossary, Update Glossary Entry

Add the required Google Contacts 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.

Select scopes from side panel
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 save 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 the Cloud Translation 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.

Create OAuth 2.0 navigation
1

Navigate to Credentials

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

Create OAuth 2.0 form
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 Translation Integration).
  • Under Authorized redirect URIs, click Add URI and enter https://api.stackone.com/connect/oauth2/googletranslate/callback.
  • Click Create. A dialogue will display your Client ID and Client Secret — copy and store them securely.
Create a new OAuth client
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/googletranslate/callback, and click Save.
  • Under Client secrets, click + Add secret to generate a new secret. Copy and store it securely — it will not be shown again.
  • Your Client ID is shown on the same page under Additional information.
Use an existing OAuth client

​
Creating the StackOne Connector Profile

To create the Connector Profile in StackOne for Google Translate:
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 Translate
  • Select Type as OAuth 2.0
  • Fill out the fields using details retrieved from your provider:
    • Client ID
    • Client Secret
    • Scopes (Optional)
  • (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 Translate.