Skip to content

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

Updated on 2026-10-04

Airtable — connector

Reads the records of a table (columns inferred from the table itself) and the base's table metadata via the Airtable Web API and loads them into the Bronze layer.

On this page (15)

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


What it is#

Reads the records of a table (columns inferred from the table itself) and the base's table metadata via the Airtable Web API and loads them into the Bronze layer.

Supported ingestion modes:

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

Purpose#

Bring Airtable data 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 in the plan).
  • Access: requires an active workspace — with the subscription overdue, suspended or canceled, the run is blocked.
  • Shutdown: the ingestion run can be turned off temporarily (maintenance or incident). When that happens, the screen informs that the feature is unavailable at the moment.

Prerequisites#

  • An Airtable account with access to the data you want to ingest.
  • In Airtable, create a personal access token at airtable.com/create/tokens with the scopes data.records:read and schema.bases:read, granting access to the base. Provide the Base ID (starts with app, is in the URL), the table name or ID and paste the token — it is encrypted and never shown again.

Credentials#

Authentication method: Access Token pasted by you. It is encrypted (AES-256-GCM) and never shown again, nor appears in logs or error messages.

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

  • Personal access token (tokenAcesso) — Token with scopes data.records:read and schema.bases:read.

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

Form fields#

CampoRótuloTipoObrigatórioObservação
baseIdID da basetextosimTrecho da URL da base que começa com app (airtable.com/app…/…).
tabelaTabelatextosimNome exato da tabela (ou o ID que começa com tbl).
tokenAcesso 🔒Personal access tokensenha/segredosimsegredo (cifrado; cofre externo opcional); Token com os escopos data.records:read e schema.bases:read.

Step-by-step#

  1. In the menu Dados → Conexões, use Nova conexão.
  2. Choose Airtable in the catalog.
  3. Fill out 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. 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)
baseId = <baseId>
tabela = <tabela>
tokenAcesso = •••••• (cifrado — nunca exibido)

Expected result#

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

Limits and costs#

  • Pagination: hard cap per run (default 10,000 pages / 5,000,000 rows); anti-loop guard.
  • SaaS load: default batchSize 5,000, maxRows 200,000 per resource.
  • Estimated volume: ~0.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 (<prefix>_bronze / _silver / _gold); there is never leakage between workspaces.
  • Secrets encrypted: sensitive material is encrypted with AES-256-GCM before being written. The external credentials vault is optional and enabled per connection; without it, the encrypted value stays in the database. Changing the value here DOES NOT revoke the credential at the source.
  • Redaction: every error/log goes 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#

  • Credential rejected (401/403) — the provider did not accept the credential: expired, revoked or lacking required permission. Reconnect the source (the source and history are preserved; do not recreate the source).
  • Request limit (429) — the provider asked to wait. The extraction respects Retry-After and retries; if it repeats, wait and reduce the schedule frequency.
  • Resource not found — check the resource identifier (account, object, table) and the granted permissions.
  • Pagination cursor stuck — the extraction stops when the API cursor does not advance (anti-loop guard). If it happens in consecutive runs, open a support ticket indicating the connector and the resource.
  • Empty records path — the response arrived without records at the expected path. Check the selected resource and filters (period, account, status) before assuming there is no data.

Troubleshooting#

  • Use Testar conexão to isolate credential/network issues before scheduling.
  • Monitor the runs in 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 revision: 2026-10-04. Sheet automatically generated from the product's connector catalog.

Related links