Skip to content

Automatic translation — the Portuguese version is the reference. View in Portuguese

Updated on 2026-10-04

Google Sheets — connector

Reads the tabs of a Google Sheets spreadsheet (real columns, configurable header) and loads each tab as a table into the Bronze layer of your workspace.

On this page (15)

Read before: ../conectores.md (state map) and fichas.md (index of datasheets).


What it is#

Reads the tabs of a Google Sheets spreadsheet (real columns, configurable header) and loads each tab as a table into the Bronze layer of your workspace.

Supported ingestion modes:

  • Nós buscamos — Nós buscamos os dados na sua fonte.

What it's for#

Bring data from Google Sheets into your datalake and make it available to the Bronze/Silver/Gold layers, BI models and the natural language question wizard.

When to use / when not to use#

Use when you need to consolidate this source into the datalake on a schedule, with isolation per workspace.

Remember that the first run with a real credential is followed by our team before the connector is fully released.

Plan and permissions#

  • Plan: core product (connectors are included in all plans; the limit is the number of sources in the plan).
  • Access: requires an active workspace — with the subscription overdue, suspended or cancelled, runs are blocked.
  • Shutdown: an ingestion run can be temporarily disabled (maintenance or incident). When that happens, the screen indicates the resource is unavailable at the moment.

Prerequisites#

  • A Google Sheets account with access to the data you want to ingest.
  • Share the spreadsheet (Reader permission) with the service account email. We don't ask for your Google password or access to your entire Drive.

Credentials#

Authentication method: Sharing with a service account: you share the resource (the spreadsheet) with the service account email, with Reader permission. We don't ask for your Google password or access to your entire Drive.

Sensitive fields. They are encrypted (AES-256-GCM) and are never stored in the connection config, pipeline definition, export or DAG. By default the encrypted value is kept in the database; moving the credential of this connection to an external credential vault is an explicit choice, made per connection after saving — see ../../administracao/credenciais-e-rotacao.md.

  • Service account JSON key (serviceAccountJson)

Secrets are never re-displayed and are redacted in every error/log (raw token, URL-encoded and in JSON).

Form fields#

CampoRótuloTipoObrigatórioObservação
spreadsheetLink or spreadsheet IDtextyesPaste the link from the address bar — we extract the ID by ourselves.
sheetTitlesTabstextnoSeparate with commas or semicolons. Empty lists all tabs in the spreadsheet.
headerRowHeader rownumbernodefault: 1; Row where the column names are located (almost always 1).
saModeService accountselectionnodefault: plataforma; options: plataforma / propria; With ours, you only share the spreadsheet with the email shown below.
serviceAccountJson 🔒Service account JSON keypassword/secretnosecret (encrypted; optional external vault); appears when saMode = propria

Step-by-step#

  1. In the menu Dados → Conexões, use Nova conexão.
  2. Choose Google Sheets in the catalog.
  3. Fill the form fields (see the table above).
  4. Use Testar conexão. The result is shown broken down into Conectividade, Autenticação and Listagem/leitura — each with OK, Failed, Not applicable or Not tested. A capability with no test of its own for this connector shows as Not applicable, and Not applicable never counts as success.
  5. Use Salvar conexão. Saving does NOT start any ingestion.
  6. On the connection card, use Montar extração (or go to Orquestração → Pipelines and use Conectar fonte). The pipeline points to the saved connection — the credential is not copied.
  7. In the review, Publicar (agenda desligada) creates version 1 without running anything. Afterwards, Ativar agenda and Executar agora are separate actions.

Example — connection test#

Example configuration (all values are fictitious; secrets appear masked):

text
# Exemplo sintético (valores fictícios — não são credenciais reais)
spreadsheet = https://docs.google.com/spreadsheets/d/1AbCexemploFicticio/edit
sheetTitles = Vendas; Clientes
headerRow = 1
saMode = plataforma

Expected result#

Testar conexão returns the list of discovered tables/resources. After the first load, rows appear in the Bronze layer of your workspace, ready for the pipeline.

Limits and costs#

  • Pagination: hard cap per run (default 10,000 pages / 5,000,000 rows); loop-guard.
  • SaaS load: default batchSize 5,000, maxRows 200,000 per resource.
  • Estimated volume: ~0.2 GB/month (catalog estimate, not a measurement).
  • Cost: the extraction itself is not charged by the platform; the Bronze load consumes datalake processing (billable).

Security#

  • Workspace scope: each customer reads and writes only to their own datalake (<prefix>_bronze / _silver / _gold); there is never leakage between workspaces.
  • Encrypted secrets: sensitive material is encrypted with AES-256-GCM before being written. The external credential vault is optional and linked per connection; without it, the encrypted value remains in the database. Changing the value here DOES NOT revoke the credential at the origin.
  • Redaction: every error/log goes through secrets redaction (raw, URL-encoded and in JSON).
  • Production does not mock: a path that would fall into a mock triggers production guard (explicit failure instead of simulating success).

Common errors#

  • Spreadsheet not shared (403) — share the spreadsheet with the service account email shown in Testar conexão, with Reader permission.
  • Tab not found — the tab title changed or the tab was removed; the error is recorded for that table and other tabs continue.
  • Request limit (429) — the extraction respects Retry-After and retries; if it repeats, wait and reduce the schedule frequency.

Troubleshooting#

  • Use Testar conexão to isolate credential/network issues before scheduling.
  • Monitor runs in the connector observability (error rate, p50/p95, freshness).
  • A schema change at the source is flagged by schema drift (new column = info; removed column/type change = attention).

Related#


Last review: 2026-10-04. Datasheet automatically generated from the product connectors catalog.

Related links