How to Access Live Google Translate Data in Power Automate Desktop via ODBC

The CData ODBC Driver for Google Translate enables you to access live Google Translate data in workflow automation tools like Power Automate. This article shows how to integrate Google Translate data into a simple workflow, moving Google Translate data into a CSV file.

Through optimized data processing, CData ODBC Drivers offer unmatched performance for interacting with live Google Translate data in Microsoft Power Automate. When you issue complex SQL queries from Power Automate to Google Translate, the driver pushes supported SQL operations, like filters and aggregations, directly to Google Translate and utilizes the embedded SQL engine to process unsupported operations client-side (e.g. SQL functions and JOIN operations).

Connect to Google Translate as an ODBC Data Source

If you have not already, first specify connection properties in an ODBC DSN (data source name). This is the last step of the driver installation. You can use the Microsoft ODBC Data Source Administrator to create and configure ODBC DSNs.

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

When you configure the DSN, you may also want to set the Max Rows connection property. This will limit the number of rows returned, which is especially helpful for improving performance when designing workflows.

Integrate Google Translate Data into Power Automate Workflows

After configuring the DSN for Google Translate, you are ready to integrate Google Translate data into your Power Automate workflows. Open Microsoft Power Automate, add a new flow, and name the flow.

👁 A new flow in Power Automate

In the flow editor, you can add the actions to connect to Google Translate, query Google Translate using SQL, and write the query results to a CSV document.

Add an Open SQL Connection Action

Add an "Open SQL connection" action (Actions -> Database) and configure the properties.

• Connection string: DSN=CData Google Translate Source

After configuring the action, click Save.

👁 A configured 'Open SQL connection' action

Add an Execute SQL Statement Action

Add an "Execute SQL statement" action (Actions -> Database) and configure the properties.

• Get connection by: SQL connection variable
• SQL connection: %SQLConnection% (the variable from the "Open SQL connection" action above)
• SQL statement: SELECT * FROM SupportedLanguages

After configuring the action, click Save.

👁 A configured 'Execute SQL statement' action

Add a Write to CSV File Action

Add a "Write to CSV file" action (Actions -> File) and configure the properties.

• Variable to write to: %QueryResult% (the variable from the "Execute SQL statement" action above)
• File path: set to a file on disk
• Configure Advanced settings as needed.

After configuring the action, click Save.

👁 A configured 'Write to CSV file' action

Add a Close SQL Connection Action

Add a "Close SQL connection" action (Actions -> Database) and configure the properties.

• SQL Connection: %SQLConnection% (the variable from the "Open SQL connection" action above)

After configuring the action, click Save.

👁 A configured 'Close SQL connection' action

Save & Run the Flow

Once you have configured all the actions for the flow, click the disk icon to save the flow. Click the play icon to run the flow.

👁 A fully configured workflow

Now you have a workflow to move Google Translate data into a CSV file.

👁 Application data in a CSV file (Salesforce is shown)

With the CData ODBC Driver for Google Translate, you get live connectivity to Google Translate data within your Microsoft Power Automate workflows.

Related Power Automate Articles

This article explains how to use the CData ODBC Driver for Google Translate with Power Automate Desktop. Check out our other articles for more ways to work with Power Automate (Desktop & Online):

• Google Translate Data in Power Automate Desktop using CData Connect