Leia antes:
../conectores.md(state map) andfichas.md(index of sheets).
What it is#
Reads contacts, sales orders, customer invoices and products via Odoo's JSON-RPC API and loads them into the Bronze layer.
Supported ingestion modes:
- Nós buscamos — We fetch the data from your source.
What it's for#
Bring Odoo 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 billing overdue, suspended or canceled, the run is blocked.
- Disablement: ingestion runs can be temporarily turned off (maintenance or incident). When that happens, the screen indicates the feature is currently unavailable.
Prerequisites#
- An Odoo account with access to the data you want to ingest.
- In Odoo, create an integration user with read access to Contacts, Sales, Billing and Inventory. In Preferences → Account Security, generate an API key and paste it as the password. Provide the server URL and the database name (Settings → Technical or the database selection screen).
Credentials#
Authentication method: user login that opens a temporary session.
Sensitive fields. They are encrypted (AES-256-GCM) and never live 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 this connection's credential to the external credential vault is an explicit choice, made per connection after saving — see ../../administracao/credenciais-e-rotacao.md.
- Senha ou chave de API (
senha) — Prefer an API key of the integration user.
Secrets are never re-displayed and are redacted across all errors/logs (raw token, URL-encoded and in JSON).
Form fields#
| Campo | Rótulo | Tipo | Obrigatório | Observação |
|---|---|---|---|---|
urlServidor | URL do servidor | texto | sim | Endereço do Odoo (SaaS ou próprio), sem barra no fim. |
banco | Banco de dados | texto | sim | Nome do banco do Odoo (no SaaS costuma ser o subdomínio). |
usuario | Usuário (login) | texto | sim | — |
senha 🔒 | Senha ou chave de API | senha/segredo | sim | segredo (cifrado; cofre externo opcional); Prefira uma chave de API do usuário de integração. |
Step by step#
- In the Dados → Conexões menu, use Nova conexão.
- Choose Odoo 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. Later, 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)
urlServidor = <urlServidor>
banco = <banco>
usuario = <usuario>
senha = •••••• (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
batchSize5,000,maxRows200,000 per resource. - Estimated volume: ~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#
- Workspace scope: 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 credential vault is optional and linked per connection; without it, the encrypted value is stored in the database. Changing the value here DOES NOT revoke the credential at the source.
- Redaction: all errors/logs go through secret redaction (raw, URL-encoded and in JSON).
- Production does not mock: a path that would fall into mock triggers the production guard (explicit failure instead of simulated 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).
- Rate limit (429) — the provider asked to wait. The extraction respects
Retry-Afterand retries; if repeated, wait and reduce the schedule frequency. - Resource not found — check the resource identifier (account, object, report) and the granted permissions.
- Pagination cursor stuck — the extraction stops when the API cursor does not advance (anti-loop guard). If this happens in consecutive runs, open a support ticket specifying the connector and the resource.
- Empty record path — the response arrived without records in the expected place. 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 connector observability (error rate, p50/p95, freshness).
- A schema change at the source is signaled by schema drift (new column = info; removed column/type change = attention).
Related#
../conectores.md— connector 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. Sheet automatically generated from the product connector catalog.