Ellipse Gradient for Header

Google Cloud Translation Integration Guide

Connect enterprise applications and document workflows to Google Cloud Translation through REST APIs, asynchronous batch operations, glossaries, and secure Google Cloud authentication.

Google Cloud Translation integration options at a glance

Google Cloud Translation provides REST APIs for Basic v2 and Advanced v3 translation scenarios, including text, document, glossary, language, and long-running operation workflows. Advanced supports asynchronous batch translation using Google Cloud Storage input and output locations. Authentication uses Google Cloud OAuth 2.0 credentials, service accounts, Application Default Credentials, IAM, and API keys for applicable Basic requests. A native Translation webhook or callback was not confirmed, so asynchronous work is normally tracked through operation polling. Martini can consume these APIs, validate and transform payloads, coordinate Cloud Storage processing, expose a controlled translation API, and manage retries and operational state.

Integration pointSupported by Google Cloud Translation?Common use casesHow Martini supports it
REST APIsYesBasic v2 and Advanced v3 support text translation, language detection, supported-language discovery, document translation, glossaries, batch jobs, and long-running operations.Martini can consume the documented REST endpoints, map request and response structures, expose reusable APIs, and orchestrate downstream processing.
Bulk / async / batch APIsYesAdvanced supports asynchronous batch text and document translation, commonly using Google Cloud Storage for input and output.Martini can submit jobs, persist operation names, schedule polling, process completion results, and route failures.
File / attachment APIsYesAdvanced supports document translation for supported formats and Cloud Storage-based batch document processing.Martini can validate file metadata, coordinate Cloud Storage locations, and pass document references to Translation workflows.
AuthenticationYesGoogle Cloud supports OAuth 2.0, service accounts, Application Default Credentials, IAM, and API keys for applicable Basic API requests.Martini can store credentials in secure environment configuration and use authenticated REST requests without embedding secrets in mappings.
gRPC APIsYesAdvanced v3 also provides Google Cloud client-library and gRPC support for applications requiring that protocol.Martini integrations should generally use the documented REST interface; custom JVM-based implementation may be considered for a deployment-specific gRPC requirement.
Webhooks / outbound callbacksNot confirmedA native Translation webhook or callback for completed translation events was not confirmed; long-running operations use polling.Martini can use scheduled workflows to poll operation status or coordinate notifications from an adjacent application or Google Cloud service.
GraphQL APIsNoA native Google Cloud Translation GraphQL API was not confirmed.Martini can expose its own GraphQL or REST façade where required, but the vendor-side integration should use REST or another confirmed interface.
SOAP APIsNoA Google Cloud Translation SOAP API was not confirmed.Martini can consume SOAP services generally, but this vendor integration should use the confirmed REST APIs unless the architecture introduces another SOAP-based system.

How Google Cloud Translation exposes data and business events

Google Cloud Translation REST APIs

Cloud Translation exposes REST APIs for Basic v2 and Advanced v3 operations, including text translation, language discovery, document translation, glossary management, and long-running operations.

Martini implementation pattern

Martini implementation pattern: a workflow or Martini API receives source content, validates the project, location, language, and payload rules, authenticates with Google Cloud credentials, calls the appropriate REST endpoint, and maps the response to the requesting application.

Implementation sequence

Receive a translation request
Validate project, language, location, and payload constraints
Authenticate with Google Cloud credentials
Call the appropriate Translation REST endpoint
Map the translated response to the target application
Persist correlation and audit metadata

Google Cloud Translation batch operations

Advanced supports asynchronous batch text and document translation, commonly using Cloud Storage input and output locations. The API returns a long-running operation reference rather than an immediate final result.

Martini implementation pattern

Martini implementation pattern: submit the batch request, persist the returned operation name, and use a scheduled workflow to poll status. When complete, the workflow validates and processes output files; failures are classified for retry or operational review.

Implementation sequence

Validate source files and Cloud Storage permissions
Submit the Advanced batch translation request
Persist the returned operation name
Schedule bounded operation-status polling
Process completed output files
Route failed operations to retry or operational handling

Google Cloud Translation document APIs

Advanced supports document translation for supported file formats, either through direct requests or Cloud Storage references depending on the operation. File types and size limits vary by method.

Martini implementation pattern

Martini implementation pattern: identify eligible documents, validate format and size constraints, map source and target locations, call the document translation API, and return or store the translated document while protecting sensitive content.

Implementation sequence

Identify the document to translate
Validate format, size, language, and access permissions
Map the document or Cloud Storage reference
Call the document translation endpoint
Validate the translated document result
Write the result to the requesting application or output location

Google Cloud Translation glossaries

Glossaries provide user-managed terminology for specific source and target language pairs. They can guide translations for approved product, technical, regulatory, or service terminology.

Martini implementation pattern

Martini implementation pattern: classify the business content, select a compatible glossary, include its resource reference in the Translation request, and validate the response before delivering it to the downstream system.

Implementation sequence

Classify the content and language pair
Select a compatible glossary resource
Validate location and API-edition compatibility
Submit the glossary-aware translation request
Validate and deliver the translated result

Common Google Cloud Translation integration patterns

Pattern 1: Translate application content synchronously

When to use this pattern

Use this pattern when an application needs an immediate translation for customer communications, service content, product descriptions, or other bounded text payloads.

Integration direction
Salesforce
Martini
Google Cloud Translation
Salesforce
Example Mapping
Google Cloud Translation FieldCanonical FieldTarget Field
contentssourceTexttranslatedContent
sourceLanguageCodesourceLanguagesourceLocale
targetLanguageCodetargetLanguagetargetLocale
mimeTypecontentTypecontentFormat
Martini implementation pattern

Martini exposes or consumes an application API, validates language codes and payload limits, calls the selected Basic v2 or Advanced v3 REST operation, applies business rules for approved languages and fields, and writes the response back. Correlation identifiers and retry classification help prevent duplicate updates after timeouts.

Martini capabilities used
  • API consumption
  • API exposure
  • workflows
  • data mapping
  • validation
  • business rules
  • error handling

Pattern 2: Batch-translate documents from Cloud Storage

When to use this pattern

Use this pattern for document collections or larger translation workloads where Advanced asynchronous batch processing and Cloud Storage input and output are appropriate.

Integration direction
Google Cloud Storage
Martini
Google Cloud Translation
Google Cloud Storage
Example Mapping
Google Cloud Translation FieldCanonical FieldTarget Field
inputUrisourceDocumentLocationgcsInputUri
outputUriPrefixtranslatedDocumentLocationgcsOutputPrefix
operationNametranslationJobIdoperationName
targetLanguageCodestargetLanguagestargetLanguageCodes
Martini implementation pattern

A Martini workflow validates file type, size, access, language, and destination rules before submitting the batch job. It stores the operation name, polls through a scheduled workflow with bounded backoff, processes completed output files, and routes failed operations without blindly resubmitting unknown submissions.

Martini capabilities used
  • workflows
  • scheduled execution
  • API consumption
  • file processing
  • state persistence
  • mapping
  • retry handling

Pattern 3: Apply approved terminology with glossaries

When to use this pattern

Use this pattern when translations must follow controlled terminology for product names, technical vocabulary, regulatory language, or customer-service responses.

Integration direction
ServiceNow
Martini
Google Cloud Translation
ServiceNow
Example Mapping
Google Cloud Translation FieldCanonical FieldTarget Field
glossaryConfigterminologyPolicyapprovedGlossary
sourceLanguageCodesourceLanguagesourceLocale
targetLanguageCodetargetLanguagetargetLocale
translatedTextlocalizedTexttranslatedField
Martini implementation pattern

Martini classifies the request, selects a glossary compatible with the language pair and location, calls Cloud Translation, validates the result, and updates the downstream application. A non-compatible glossary or unsupported language is treated as a business validation error rather than retried indefinitely.

Martini capabilities used
  • workflows
  • data mapping
  • business rules
  • validation
  • API consumption
  • error handling

Pattern 4: Expose a centralized translation API

When to use this pattern

Use this pattern when multiple applications need consistent translation policies without distributing Google Cloud credentials and vendor-specific request logic to each application.

Integration direction
Salesforce
ServiceNow
Martini
Google Cloud Translation
Example Mapping
Google Cloud Translation FieldCanonical FieldTarget Field
textsourceTextcontents
localetargetLanguagetargetLanguageCode
glossaryterminologyPolicyglossaryConfig
requestIdcorrelationIdrequestMetadata
Martini implementation pattern

Martini exposes a controlled REST API that authenticates calling applications, enforces language, payload, glossary, and logging policies, invokes Cloud Translation, and returns a consistent internal response. Reusable workflows centralize retry behavior, sensitive-data handling, and operation tracking for asynchronous requests.

Martini capabilities used
  • API exposure
  • workflows
  • authentication and authorization
  • data mapping
  • business rules
  • reusable integration logic
  • monitoring

Applications commonly integrated with Google Cloud Translation

Google Cloud Translation can be used as a translation-processing step within application, content, customer-service, and document workflows. These are standards-based integration patterns rather than confirmed native product relationships.

Application Scenario Direction Martini Pattern
Salesforce Translate Case comments, Knowledge content, and customer communications for multilingual service operations. Salesforce → Martini → Google Cloud Translation → Salesforce Martini receives selected Salesforce content, validates language values, calls the Translation REST API, applies business rules, and writes the translated result back through Salesforce APIs.
ServiceNow Translate incident descriptions, service requests, knowledge articles, and employee-support content. ServiceNow → Martini → Google Cloud Translation → ServiceNow A Martini workflow consumes ServiceNow content, selects the approved language pair or glossary, submits translation, and updates the appropriate ServiceNow field with controlled retries and audit metadata.
Zendesk Translate support tickets, macros, help-center content, and customer replies. Zendesk → Martini → Google Cloud Translation → Zendesk Martini exposes or consumes an API endpoint for Zendesk events or requests, maps ticket text into Translation API payloads, and returns or stores translated content while minimizing sensitive logging.
Shopify Translate product descriptions, collection text, and storefront content for regional markets. Shopify → Martini → Google Cloud Translation → Shopify A scheduled or API-triggered workflow retrieves eligible Shopify content, normalizes locale values, translates text, and updates localized content after validation and duplicate checks.
Workday Translate selected job descriptions, organizational content, or HR communications where permitted by policy. Workday → Martini → Google Cloud Translation → Workday Martini retrieves approved Workday content, applies data-policy and language rules, calls Cloud Translation, and sends the result back through authorized Workday interfaces.
SAP S/4HANA Translate product, procurement, customer-service, or operational text for multilingual processes. SAP S/4HANA → Martini → Google Cloud Translation → SAP S/4HANA Martini orchestrates SAP API requests, transforms business text and language codes into Translation API structures, applies glossary selection rules, and writes results back with retry classification.
NetSuite Translate item descriptions, customer communications, or localized operational content. NetSuite → Martini → Google Cloud Translation → NetSuite A Martini workflow retrieves eligible NetSuite fields, validates size and locale constraints, calls Cloud Translation, and updates the target fields with correlation identifiers.
Google Cloud Storage Store source documents and translated outputs for Advanced asynchronous batch document translation. Google Cloud Storage → Martini → Google Cloud Translation → Google Cloud Storage Martini validates Cloud Storage objects, submits a batch translation operation, persists the operation name, polls completion from a scheduled workflow, and processes the translated output location.

How to build a Google Cloud Translation integration in Martini

Objective

Establish the Google Cloud project, API edition, location, and authentication model before building workflow logic.

Instructions in Martini

  • Choose Basic v2 or Advanced v3 for the use case
  • Configure OAuth 2.0, service-account, Application Default Credential, or applicable API-key settings
  • Store credentials and project configuration in secure environment settings
  • Validate IAM permissions and Cloud Storage access where required

Objective

Select an invocation model that matches the translation workload and whether the process is synchronous or asynchronous.

Instructions in Martini

  • Use a Martini API for application-initiated translation requests
  • Use a workflow trigger for document-processing requests
  • Use a scheduler trigger to poll long-running operations
  • Do not assume a native Translation webhook is available

Objective

Collect text, document metadata, glossary references, or Cloud Storage locations needed by the Translation API.

Instructions in Martini

  • Retrieve source content from the originating application
  • Validate document format, size, and storage permissions
  • Normalize source and target language values
  • Load compatible glossary and location configuration

Objective

Coordinate REST calls, asynchronous operation state, downstream updates, and exception paths in a maintainable workflow.

Instructions in Martini

  • Call the appropriate Translation REST endpoint
  • Persist operation names for asynchronous jobs
  • Separate job submission from status polling
  • Use reusable workflow logic for common translation policies

Objective

Convert application payloads and vendor responses into consistent internal and downstream data models.

Instructions in Martini

  • Map source text and language fields to Translation request structures
  • Transform translated responses or output-file metadata
  • Preserve the original business locale when normalization is required
  • Avoid logging full sensitive source or translated content

Objective

Enforce language, glossary, quota, document, and duplicate-submission policies before and after vendor calls.

Instructions in Martini

  • Reject unsupported language pairs and incompatible glossaries
  • Apply payload and concurrency limits
  • Classify validation, permission, quota, and transient errors
  • Use correlation identifiers and persisted state for idempotent processing

Common Google Cloud Translation data objects used in integrations

ObjectTypical UseCommon target systemsMartini handling
ProjectsProvide the billing, quota, API enablement, and IAM boundary for Translation requests.Google Cloud IAM, billing systems, deployment configuration, operational databasesMartini stores project configuration in secure environment settings and includes the correct project context in API requests.
LocationsIdentify the Google Cloud location associated with Advanced Translation resources and operations.Configuration stores, workflow state, Google Cloud resource managementMartini validates location values and preserves them with glossary, model, and operation metadata.
GlossariesApply approved terminology for product names, regulatory terms, technical vocabulary, and customer-service language.Content platforms, Salesforce, ServiceNow, document workflowsMartini selects compatible glossary resources based on language pair, location, API edition, and business rules.
Glossary entriesRepresent source-language terms and preferred target-language equivalents used by a glossary.Terminology repositories, content-management applications, translation governance storesMartini can transform terminology data into vendor request structures and validate language-pair compatibility.
Translation requestsSubmit synchronous text, document, or batch translation work with source and target language information.CRM, service applications, commerce platforms, content systemsMartini validates payloads, normalizes language codes, maps source content, invokes REST endpoints, and returns translated results.
Long-running operationsTrack asynchronous Advanced batch or document translation jobs until completion or failure.Workflow state stores, Google Cloud Storage, operational queuesMartini persists the operation name, polls with bounded backoff, handles completion states, and prevents duplicate submissions.

Authentication and security considerations

Google Cloud authentication

Cloud Translation uses Google Cloud authentication and authorization. Advanced v3 commonly uses OAuth 2.0 credentials, service accounts, Application Default Credentials, workload identity, or delegated user credentials. Basic v2 supports API keys for applicable requests.

IAM and secrets

IAM permissions determine access to projects, locations, glossaries, operations, and related Cloud Storage resources. Martini should store credentials, project identifiers, and sensitive configuration in secure environment settings rather than workflow mappings or request payloads.

  • Restrict service-account permissions to required resources.
  • Restrict API keys by API, application, or network where applicable.
  • Protect Cloud Storage input and output locations.
  • Minimize logging of personal, confidential, or regulated translation content.

Operational considerations for Google Cloud Translation integrations

Quotas and payload limits

Google Cloud quotas and limits apply at the project and API level. Control concurrency, monitor character and document usage, and validate text size, file format, file size, batch counts, and language compatibility before submission.

Long-running operations

Persist operation names and poll with bounded delays, maximum durations, and explicit handling for completed, failed, and cancelled states. Separate polling retries from job-submission retries to reduce duplicate work.

Data and API governance

  • Use correlation identifiers and persisted state for idempotency.
  • Handle paginated resource listings with returned page tokens.
  • Validate Cloud Storage permissions, locations, and output conventions.
  • Document whether the integration uses Basic v2 or Advanced v3.
  • Test language normalization, glossary compatibility, and document constraints.
  • Monitor workflow logs and avoid recording complete source or translated payloads.

Why use Martini instead of scripts or point-to-point integrations?

Centralized integration logic

Martini separates application workflows from Google Cloud Translation request details. A reusable workflow or API can standardize authentication, language validation, glossary selection, payload limits, and response handling across multiple applications.

Reliable orchestration

Unlike isolated scripts, Martini can coordinate synchronous REST calls, asynchronous operation polling, Cloud Storage processing, downstream updates, retries, and error routes within a maintainable workflow model.

Controlled change and operations

  • Keep credentials and environment-specific configuration outside workflow logic.
  • Apply consistent mappings and business rules across integrations.
  • Persist operation state to reduce duplicate batch submissions.
  • Expose a controlled API façade instead of distributing vendor credentials.
  • Use centralized monitoring, troubleshooting, and deployment practices.

Frequently asked questions

How can Google Cloud Translation be integrated with enterprise systems?

Google Cloud Translation can be integrated through its Basic v2 and Advanced v3 REST APIs for text, document, glossary, language, batch, and long-running operation workflows. Advanced asynchronous jobs can use Google Cloud Storage for input and output, while authentication can use Google Cloud OAuth 2.0 credentials, service accounts, IAM, or applicable API keys.

Can Martini integrate with Google Cloud Translation?

Yes. Martini can consume the Google Cloud Translation REST API, authenticate with Google Cloud credentials, map application content into translation requests, coordinate Cloud Storage document workflows, poll long-running operations, and expose a controlled Martini API for internal applications.

Do I need a connector to integrate Google Cloud Translation with Martini?

No dedicated Google Cloud Translation connector is required. Martini can integrate using the vendor's confirmed REST APIs, Google Cloud authentication methods, long-running operation polling, and Cloud Storage-based document-processing workflows.

Is there any extra Lonti cost to integrate Google Cloud Translation with Martini?

Lonti does not charge an additional per-connector or per-vendor fee to integrate Google Cloud Translation. The integration is subject to the provisioned capacity of the Martini environment. Separate costs may apply from Google Cloud, infrastructure, Cloud Storage, network services, or other third-party systems.

Which Google Cloud Translation API should an integration use?

Basic v2 is suited to straightforward text translation scenarios. Advanced v3 provides resource-oriented capabilities such as glossaries, document translation, batch translation, and long-running operations. The API edition should be selected explicitly because endpoints, request models, and authentication assumptions differ.

Does Google Cloud Translation send webhooks when a translation finishes?

A native Translation webhook or outbound callback was not confirmed. For long-running operations, the standard approach is to persist the operation name and poll its status. Martini can use a scheduled workflow for polling or coordinate completion through an adjacent application or Google Cloud service.

How should synchronization, mapping, and transformation work?

Cloud Translation is a request-oriented processing service rather than a conventional record-synchronization system. Martini can retrieve source content, normalize language and locale values, map fields to Translation request structures, apply glossary and business rules, and write translated content or output-file metadata to downstream applications.

How are errors, retries, and duplicate translation jobs handled?

Martini can classify invalid language, permission, format, quota, and transient failures, then apply bounded retries only where appropriate. For asynchronous work, it should persist the Google Cloud operation name and distinguish polling failures from submission failures so a timeout does not create a duplicate batch job. Martini can also expose a REST API façade that centralizes these policies.

Related Martini documentation

APIs

Workflows

Data

Security

Operations

Connect Google Cloud Translation with Martini

Use Martini to orchestrate secure Google Cloud Translation API calls, document workflows, glossary-based processing, asynchronous batch jobs, and downstream application updates.

EXPLORE MARTINI
BOOK A DEMO