Extend Google Sheets with Google Translate Data

Interact with Google Translate data from Google Sheets through macros, custom functions, and add-ons. The CData API Server enables connectivity to Google Translate data from cloud-based and mobile applications like Google Sheets. The API Server is a lightweight Web application that produces OData services for Google Translate.

Google Apps Script can consume these OData services in the JSON format. This article shows how to create a simple add-on that populates a Google Spreadsheet with SupportedLanguages data.

Set Up the API Server

If you have not already done so, download the CData API Server. Once you have installed the API Server, follow the steps below to begin producing secure Google Translate OData services:

Connect to Google Translate

To work with Google Translate data from Google Sheets, we start by creating and configuring a Google Translate connection. Follow the steps below to configure the API Server to connect to Google Translate data:

1. First, navigate to the Connections page.
2. Click Add Connection and then search for and select the Google Translate connection.
3. Enter the necessary authentication properties to connect to Google Translate.

   Authentication

   Google Cloud Translation API requires OAuth 2.0 authentication to ensure secure access to translation services, datasets, glossaries, and adaptive MT resources. This authentication method allows you to securely connect to your Google Cloud project and manage translation resources with proper authorization.

   OAuth 2.0 Setup and Configuration

   Step 1: Create Google Cloud Project and Enable API

   To set up OAuth authentication:

   1. Visit the Google Cloud Console
   2. Create a new project or select an existing project
   3. Note down your Project ID (required for all API calls)
   4. Navigate to "APIs & Services" > "Library"
   5. Search for and enable the "Cloud Translation API"
   6. Go to "APIs & Services" > "Credentials"
   7. Click "Create Credentials" and select "OAuth Client ID"
   8. Configure the OAuth consent screen if prompted
   9. Select "Desktop application" or "Web application" as appropriate
   10. Set the authorized redirect URI (CallbackURL)
   11. Copy the Client ID and Client Secret for use in your connection

   Required Connection Properties

   • AuthScheme: Set this to OAuth (required)
   • OAuthClientId: Client ID from Google Cloud Console (required)
   • OAuthClientSecret: Client secret from Google Cloud Console (required)
   • CallbackURL: Redirect URI specified in your OAuth application (required)
   • InitiateOAuth: Set to GETANDREFRESH for automatic token management (recommended)
   • ProjectId: Your Google Cloud project ID or project number (required for queries)

   Required OAuth Scopes

   The Google Cloud Translation API Profile requires the following OAuth scope:

   • https://www.googleapis.com/auth/cloud-translation - Full access to Cloud Translation API resources including translation, datasets, glossaries, and adaptive MT
   
4. After configuring the connection, click Save & Test to confirm a successful connection.

Configure API Server Users

Next, create a user to access your Google Translate data through the API Server. You can add and configure users on the Users page. Follow the steps below to configure and create a user:

1. On the Users page, click Add User to open the Add User dialog.
2. Next, set the Role, Username, and Privileges properties and then click Add User.
3. An Authtoken is then generated for the user. You can find the Authtoken and other information for each user on the Users page:

Creating API Endpoints for Google Translate

Having created a user, you are ready to create API endpoints for the Google Translate tables:

1. First, navigate to the API page and then click Add Table .
2. Select the connection you wish to access and click Next.
3. With the connection selected, create endpoints by selecting each table and then clicking Confirm.

Gather the OData Url

Having configured a connection to Google Translate data, created a user, and added resources to the API Server, you now have an easily accessible REST API based on the OData protocol for those resources. From the API page in API Server, you can view and copy the API Endpoints for the API:

Retrieve Google Translate Data

Open the Script Editor from your spreadsheet by clicking Tools -> Script Editor. In the Script Editor, add the following function to populate a spreadsheet with the results of an OData query:

function retrieve(){
  var url = "https://MyUrl/api.rsc/SupportedLanguages?select=Id,LanguageCode,DisplayName,ProjectId";
  var response = UrlFetchApp.fetch(url,{
    headers: {"Authorization": "Basic " + Utilities.base64Encode("MyUser:MyAuthtoken")}
  }); 
  var json = response.getContentText();
  var sheet = SpreadsheetApp.getActiveSheet();
  var a1 = sheet.getRange('a1');
  var index=1;
  var supportedlanguages = JSON.parse(json).value;

  var cols = [["Id","LanguageCode","DisplayName","ProjectId"]]; 
  sheet.getRange(1,1,1,4).setValues(cols);

  row=2;
  for(var i in supportedlanguages){
    for (var j in supportedlanguages[i]) {
      switch (j) {
        case "Id":
          a1.offset(row,0).setValue(account[i][j]);
          break;
        case "LanguageCode":
          a1.offset(row,1).setValue(account[i][j]);
          break;
        case "DisplayName":
          a1.offset(row,2).setValue(account[i][j]);
          break;
        case "ProjectId":
          a1.offset(row,3).setValue(account[i][j]);
          break;
      }      
    }
    row++;
  }
}

Follow the steps below to add an installable trigger to populate the spreadsheet when opened:

1. Click Resources -> Current Project's Triggers -> Add a New Trigger.
2. Select retrieve in the Run menu.
3. Select From Spreadsheet.
4. Select On open.

After closing the dialog, you are prompted to allow access to the application.

You can test the script by clicking Publish -> Test as Add-On. Select the version, installation type, and spreadsheet to create a test configuration. You can then select and run the test configuration.