how to use google.TTS

Thanks for reaching out, Sajjad. I'm an AI assistant and I'm here to help. Give me a moment while I research this topic.

help wiring credentials into your app?

You're asking how to wire Google Cloud credentials for

google.TTS

. Below are three supported ways and short examples so you can pick the one that fits your deployment. 1) Use

GOOGLE_APPLICATION_CREDENTIALS

(credentials file) • Save your service-account JSON to a secure path (e.g.,

/secrets/gcloud-sa.json

). • Set the env var in your environment/container: ◦ Linux/macOS:

export GOOGLE_APPLICATION_CREDENTIALS="/secrets/gcloud-sa.json"

◦ Docker: use

-e GOOGLE_APPLICATION_CREDENTIALS=/secrets/gcloud-sa.json

and mount the file. • No additional code required;

google.TTS

will use ADC and the file. 2) Pass

credentials_file

to

google.TTS

• Point the plugin directly at the file path:

from livekit.plugins import google

session = AgentSession(
    tts = google.TTS(
        credentials_file="/secrets/gcloud-sa.json",
        voice_name="en-US-Standard-H",
    ),
)

3) Pass credentials inline via

credentials_info

(dictionary) • Load the JSON and pass it as a dict (useful if you store secrets in a vault):

import json
from livekit.plugins import google

with open("/secrets/gcloud-sa.json") as f:
    creds = json.load(f)

session = AgentSession(
    tts = google.TTS(
        credentials_info=creds,
        voice_name="en-US-Standard-H",
    ),
)

Security notes • Keep service-account keys restricted and stored in a secure secret store where possible. • Prefer ADC or secret manager → environment file over committing keys in source code. Would you like a sample Docker Compose snippet or an example using a secret manager (AWS Secrets Manager / GCP Secret Manager)? , with interactive elements

wher this file is placed

Good question — here are recommended places to put the Google service-account JSON and how to reference it for each environment. Local development • Put the file somewhere not in your repo, e.g.

~/secrets/gcloud-sa.json

or a project-level

./secrets/gcloud-sa.json

. • Set the env var: ◦ macOS/Linux:

export GOOGLE_APPLICATION_CREDENTIALS="/path/to/secrets/gcloud-sa.json"

◦ Windows (PowerShell):

$env:GOOGLE_APPLICATION_CREDENTIALS="C:\path\to\secrets\gcloud-sa.json"

Containerized (Docker) • Store the file on the host (outside source tree) and mount it into the container: ◦

docker run -v /host/secrets/gcloud-sa.json:/secrets/gcloud-sa.json -e GOOGLE_APPLICATION_CREDENTIALS=/secrets/gcloud-sa.json your-image

• Or inject via your container orchestrator’s secret mechanism (Kubernetes Secret, Docker secrets) and set

GOOGLE_APPLICATION_CREDENTIALS

to the mounted path. Production / Cloud • Prefer a secret manager (GCP Secret Manager, AWS Secrets Manager, HashiCorp Vault). Retrieve the secret at startup and either: ◦ Write to a local file path and set

GOOGLE_APPLICATION_CREDENTIALS

to that path, or ◦ Pass the JSON into

google.TTS

with

credentials_info

(dictionary) so you never write the file to disk. Examples of referencing the path in code • Environment-based (no code changes): rely on ADC after setting

GOOGLE_APPLICATION_CREDENTIALS

. • Direct plugin:

google.TTS(credentials_file="/secrets/gcloud-sa.json", ...)

• Inline: load secret and pass

credentials_info=creds_dict

Security tips • Don’t commit the JSON to source control. • Limit the service account permissions to only needed TTS scopes. • Rotate keys and store them in a secrets manager when possible. Do you want a Docker Compose example or a Kubernetes Secret + deployment example? , with interactive elements

where this file is passed

You're asking where to pass the Google service-account JSON so

google.TTS

can authenticate. Here are the three ways and exactly where to pass the file/data in each case. 1) Environment variable (ADC) • Place the JSON on disk (outside your repo), e.g.

/secrets/gcloud-sa.json

. • Set the env var so the runtime picks it up: ◦ Linux/macOS:

export GOOGLE_APPLICATION_CREDENTIALS="/secrets/gcloud-sa.json"

◦ Docker:

-e GOOGLE_APPLICATION_CREDENTIALS=/secrets/gcloud-sa.json -v /host/secrets/gcloud-sa.json:/secrets/gcloud-sa.json

• Where it’s passed: the Google client library reads the path from `GOOGLE_APPLICATION_CREDENTIALS`; no code changes required. 2)

credentials_file

argument to

google.TTS

• Place the JSON file on disk and point the plugin at it:

from livekit.plugins import google

session = AgentSession(
    tts=google.TTS(
        credentials_file="/secrets/gcloud-sa.json",
        voice_name="en-US-Standard-H",
    ),
)

• Where it’s passed: directly into the plugin via the

credentials_file

parameter. 3) Inline

credentials_info

(dict) • Retrieve the JSON from your secret store at runtime (vault, secret manager, env var) and load it into a dict:

import json
from livekit.plugins import google

creds = json.loads(os.environ["GC_SA_JSON"])  # or load from secret manager
session = AgentSession(
    tts=google.TTS(
        credentials_info=creds,
        voice_name="en-US-Standard-H",
    ),
)

• Where it’s passed: as the

credentials_info

parameter in code — no file necessary. Recommended placements by environment • Local dev:

~/secrets/gcloud-sa.json

and set

GOOGLE_APPLICATION_CREDENTIALS

. • Docker: host path mounted into container at

/secrets/gcloud-sa.json

and set env var or use

credentials_file

. • Kubernetes / Production: use your secret manager (GCP Secret Manager, Kubernetes Secret, Vault). Either: ◦ Mount the secret to a file path and set

GOOGLE_APPLICATION_CREDENTIALS

, or ◦ Fetch secret at startup and pass it as

credentials_info

to avoid writing to disk. Security reminders • Don’t commit the JSON to source control. • Prefer secret managers or ADC. • Least-privilege the service account. Do you want a Docker Compose snippet or a Kubernetes Secret + Deployment example for your environment? , with interactive elements