Mattering Automations Google Translate integration

Connect the Google Cloud Translation API to Mattering Automations: translate text and detect languages as workflow steps.

Get the credential Connect Verify Node reference Troubleshooting

The Mattering Automations Google Translate integration adds the Cloud Translation API to your automation canvas: translate one or more strings into a target language and detect what language a string is written in.

Setup is one Google Cloud API key. If you already use another Google API-key integration on Mattering (PageSpeed, YouTube, and the rest of the family), the same key works here once the Translation API is enabled on its project.

Before you start

A Google Cloud project with billing enabled (the Translation API requires it; Google's pricing includes a monthly free character tier).
A Mattering workspace with access to the Automations app.

Create or reuse a Google API key

The connector authenticates with a Google Cloud API key sent as a query parameter. One key serves every Google API-key integration on Mattering.

In the Google Cloud console, select your project and enable the Cloud Translation API (search for translate.googleapis.com in the API Library).

Open APIs and Services > Credentials and click Create credentials > API key, or reuse the key you already use for other Mattering Google integrations.

One Google API key serves every Google API-key integration on Mattering (PageSpeed, YouTube, Translate, and the rest of the family). Each API just needs enabling on the key's project.

Optionally restrict the key: under API restrictions, select the Google APIs you use with Mattering so a leaked key cannot call anything else.

Copy the key (it starts with AIza).

Connect Google Translate to Mattering

In Mattering Automations, open Connectors and click Add Connector.

Choose Google Cloud Translation from the list.

Click Create new credential, paste the API key, and save. The credential is stored encrypted in Google Secret Manager.

Click Connect. Both translation nodes appear in your canvas palette.

Verify it works

Open an automation canvas and drop Google Translate Text onto it. Set text to any sentence and target to a language code like es, then run a test step: a successful response returns the translated string and the detected source language.

If the response reports the API is not enabled, the Translation API is missing on the key's project; enable it in the API Library and retry.

Node reference

2 nodes, generated from the connector itself so this reference always matches what ships.

Read and query nodes 1

Google Detect Language

gapi_detect_language

Detect the source language of one or more strings.

Action nodes 1

Google Translate Text

gapi_translate

Translate one or more strings into a target language.

Using the integration

On the automation canvas

Chain Detect Language into a condition to branch by language, then Translate Text where conversion is needed. Both nodes accept template references, so text can come from any prior step.

From AI assistants over MCP

Both nodes speak MCP, the open protocol for connecting AI assistants to tools. Claude, ChatGPT, and Matter can translate and detect through the same nodes your workflows use.

Cost awareness

Google bills the Translation API per character with a monthly free tier; Google's pricing page is the source of truth. Keep an eye on high-volume loops, and prefer batching multiple strings into one Translate Text call.

Troubleshooting

The node returns a 403 error

Either the Translation API is not enabled on the key's project, billing is not enabled, or the key's API restrictions exclude the Translation API. Check all three in the Google Cloud console.

Translations return but the language looks wrong

Auto-detection can misread very short strings. Pass the source language code explicitly when you know it.

The same key works for YouTube but not Translate

Each Google API must be enabled individually on the project, and key restrictions apply per API. Enable the Cloud Translation API and add it to the key's allowed APIs.

The Google Translate MCP

What connecting Google Translate unlocks for AI agents and automations, with common uses and FAQs.

More guides

All Automations documentation

Every integration guide, plus how connectors, credentials, and workflows fit together.

Google Translate is a trademark of its respective owner. Mattering uses platform names to identify the services these integrations connect to; no endorsement or affiliation is implied.