Read first:
../conectores.md(states map) andfichas.md(index of cards).
What it does#
Reads the pages of a database (title, dates and all properties in JSON) and the workspace users via the Notion API and loads them into the Bronze layer.
Supported ingestion modes:
- Nós buscamos — Nós buscamos os dados na sua fonte.
What it's for#
Bring Notion 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 — if the subscription is overdue, suspended or canceled, the run is blocked.
- Disablement: the ingestion run can be temporarily disabled (maintenance or incident). When that happens, the screen informs that the feature is unavailable at the moment.
Prerequisites#
- A Notion account with access to the data you want to ingest.
- In Notion, create an internal integration at notion.so/my-integrations and copy the token. Then open the database, click ••• → Connections and add the integration (without this the API won't see the database). Provide the database ID (it's in the URL) 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 placed in the config of the connection, in the pipeline definition, in the export or in the DAG. By default the encrypted value is stored in the database; moving the credential from this connection to an external credentials vault is an explicit choice, made per connection after saving — see ../../administracao/credenciais-e-rotacao.md.
- Integration token (
tokenIntegracao) — Internal Integration Secret, at notion.so/my-integrations.
Secrets are never re-displayed and go through redaction in every error/log (raw token, URL-encoded and in JSON).
Form fields#
| Campo | Rótulo | Tipo | Obrigatório | Observação |
|---|---|---|---|---|
databaseId | Database ID | text | yes | Paste the database link — we extract the ID (32 characters) automatically. |
tokenIntegracao 🔒 | Integration token | password/secret | yes | secret (encrypted; external vault optional); Internal Integration Secret, at notion.so/my-integrations. |
Step-by-step#
- In the Dados → Conexões menu, use Nova conexão.
- Choose Notion in the catalog.
- Fill in the form fields (see the table above).
- 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.
- Use Salvar conexão. Saving DOES NOT start any ingestion.
- 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.
- 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):
# Exemplo sintético (valores fictícios — não são credenciais reais)
databaseId = <databaseId>
tokenIntegracao = •••••• (cifrado — nunca exibido)Expected result#
The Testar conexão returns the list of discovered tables/resources. After the first load, the 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); anti-loop guard.
- SaaS load: default
batchSize5.000,maxRows200.000 per resource. - Estimated volume: ~0.1 GB/month (catalog estimate, not measurement).
- Cost: the extraction itself is not charged by the platform; the Bronze load consumes datalake processing (billable).
Security#
- Scope by 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 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 origin.
- Redaction: all error/log output goes through secret redaction (raw, URL-encoded and in JSON).
- Production doesn't fake: a path that would fall into 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 missing the required permission. Reconnect the source (the source and history are preserved; do not recreate the source).
- Rate limit (429) — the provider asked to wait. The extraction respects
Retry-Afterand retries; if it repeats, wait and reduce the schedule frequency. - Resource not found — check the resource identifier (account, object, report) and the granted permissions.
- Stuck pagination cursor — the extraction stops when the API cursor does not advance (anti-loop guard). If this occurs in consecutive runs, open a support ticket specifying the connector and the resource.
- Empty record path — the response arrived without records in the expected location. 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 runs in the observability per connector (error rate, p50/p95, freshness).
- A schema change at the source is signaled by schema drift (new column = info; column removed/type changed = attention).
Related#
../conectores.md— connectors catalog by state../ingestao-incremental-backfill.md— full, incremental by watermark, backfill and checkpoint../pipeline-medalhao.md— Bronze/Silver/Gold layers and quality../agendamento-retry-dlq.md— scheduling, retry/backoff and DLQ../custo-limites-seguranca.md— cost, caps and workspace security
Last review: 2026-10-04. Card automatically generated from the product connector catalog.