Skip to content

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

Updated on 2026-10-04

Google Drive — connector

Reads CSV, JSON and XLSX files (and Google Sheets exported as CSV) from a Google Drive folder shared with the service account and loads them into the Bronze layer; Parquet is detected and loaded directly.

On this page (15)

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


What it is#

Reads CSV, JSON and XLSX files (and Google Sheets exported as CSV) from a Google Drive folder shared with the service account and loads them into the Bronze layer; Parquet is detected and loaded directly.

Supported ingestion modes:

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

What it's for#

Bring data from Google Drive 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 scheduled basis, 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 part of all plans; the limit is the number of sources allowed by the plan).
  • Access: requires an active workspace — with a past-due, suspended or cancelled subscription, the run is blocked.
  • Shutdown: ingestion runs can be temporarily disabled (maintenance or incident). When this happens, the UI indicates that the feature is unavailable at the moment.

Prerequisites#

  • A Google Drive account with access to the data you want to ingest.
  • In Google Drive, share the folder containing the files with the service account email (as Reader). Paste the folder ID (the segment after /folders/ in the URL). With ingestia's service account you do not need to generate a key; with your own, paste the JSON key.

Credentials#

Authentication method: Sharing with a service account: you share the resource (the sheet) with the service account email, granting Reader permission. We do not ask for your Google password nor access to your entire Drive.

Sensitive fields. They are encrypted (AES-256-GCM) and are never kept in the connection config, in the pipeline definition, in the export or in the DAG. By default the encrypted value is stored in the database; moving this connection's credential to the 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 any error/log (raw token, URL-encoded and in JSON).

Form fields#

CampoLabelTypeRequiredNote
folderIdFolder IDtextyesIn the folder URL: https://drive.google.com/drive/folders/<ID da pasta>.
saModeService accountselectionnodefault: plataforma; options: plataforma / propria; With ours, you only add the service account email as a reader on the Drive folder.
serviceAccountJson 🔒Service account JSON keypassword/secretnosecret (encrypted; external vault optional); shown when saMode = propria

Step by step#

  1. In the Dados → Conexões menu, use Nova conexão.
  2. Choose Google Drive in the catalog.
  3. Fill the form fields (see the table above).
  4. Use Testar conexão. The result is returned in three capabilities, each with OK, Failed, Not applicable or Not tested. In this datasheet they mean: Network — the storage service endpoint is reachable from the application server; Authentication — the form credential (access key or service account, not user+password) was accepted; Read — it was possible to list the objects of the bucket/container under the given prefix (the displayed count is of visible objects, not of tables).
  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 review, Publicar (agenda desligada) creates version 1 without running anything. Then, 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)
folderId = <folderId>
saMode = plataforma

Expected result#

The Testar conexão returns the number of visible objects under the given prefix. After the first load, the contents of those files appear in the Bronze layer of your workspace, ready for the pipeline.

Limits and costs#

  • Paging: 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: ~1 GB/month (catalog estimate, not measurement).
  • Cost: the extraction itself is not billed by the platform; the Bronze load consumes datalake processing (billable).

Security#

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

Common errors#

  • Authentication failed — this connector's credential is NOT a user+password: it is an access key (or service account). Check the pair provided in the form and whether it is still active at the provider.
  • Listing denied — the credential authenticates but cannot list the bucket. Grant bucket listing and read of objects under the prefix; read permission without listing is not enough, because the pipeline needs to discover which files exist.
  • Bucket/prefix does not exist or is empty — verify the exact bucket name and prefix (folder). A prefix with no objects returns zero visible objects, not an error.
  • File in unsupported format — object storage transports files; the pipeline needs to be able to read the content (CSV, JSON or Parquet). An object in another format is ignored or fails to load, according to the pipeline policy.

Troubleshooting#

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

Related#


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

Related links