<aside>
Description
The Custom Google Translate Engine integrates with the Google Cloud Translation API using OAuth 2.0 authentication. This engine provides access to Google's extensive language coverage through your own Google Cloud project.
</aside>
Prerequisites
Step 1 — Enable Cloud Translation API
- Go to: https://console.cloud.google.com/apis/library/translate.googleapis.com
- Select your project from the top dropdown
- Click Enable
Step 2 — Configure OAuth Consent Screen
- Go to: https://console.cloud.google.com/apis/credentials/consent
- Select External as User Type → click Create
- Fill in required fields:
- App name: anything (e.g. "SimpleT")
- User support email: your email
- Developer contact email: your email
- Click Save and Continue
- On the Scopes step → click Add or Remove Scopes → search for and add: https://www.googleapis.com/auth/cloud-translation
- Click Update → Save and Continue through remaining steps
- Publishing status: set to In production (or leave as Testing if only you will use it)
Step 3 — Create OAuth 2.0 Credentials
- Go to: https://console.cloud.google.com/apis/credentials
- Click + CREATE CREDENTIALS → OAuth client ID
- Application type: Web application
- Name: anything (e.g. "SimpleT Google Translate")
- Under Authorized redirect URIs → click + Add URI → enter:
- Click Create
- A popup shows your credentials — copy and save both:
- Client ID (ends in .apps.googleusercontent.com)
- Client Secret
Step 4 — Create Google Translate Engine in SimpleT
- Go to Translation Engines → click New Engine
- Fill in the fields:
- Click Save
Step 5 — Test Translation (Authentication is Automatic)
- Open the engine → click Test Translation
- First time only: A Google sign-in popup will appear
- Sign in with your Google account
- Grant the requested permissions
- Popup closes automatically
- Translation runs immediately after sign-in
- All future tests: No popup — the system silently refreshes the token in the background
Notes
- Tokens are stored securely in the database — you only sign in once
- If Google revokes access (e.g. you remove the app from your Google account permissions), the popup will appear again automatically on the next test
- For production deployment, add your production domain's callback URL to the Authorized redirect URIs list in Google Cloud Console

<aside>
Quick View
End User Documentation