Read before:
../conectores.md(map of states) andfichas.md(index of sheets).
What it is#
Reads a CSV, JSON, or XLSX file published at a URL (GET with optional token or headers) and loads it into the Bronze layer; Parquet is recognized and loaded directly.
Supported ingestion modes:
- We fetch — We fetch the data from your source.
What it's for#
Bring data from File over HTTP 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 of the product (connectors are part of all plans; the limit is the number of sources allowed by the plan).
- Access: requires an active workspace — with the subscription overdue, suspended or canceled, runs are blocked.
- Shutdown: ingestion runs can be temporarily disabled (maintenance or incident). When that happens, the screen indicates the resource is unavailable at the moment.
Prerequisites#
- A File over HTTP account with access to the data you want to ingest.
- Provide the full file URL (CSV, JSON, XLSX or Parquet). If the server requires authentication, paste the Bearer token or the necessary headers (one per line, in the format Name: value); the token 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 does it appear in logs or error messages.
Sensitive fields. They are encrypted (AES-256-GCM) and are never stored 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 an external credential vault is an explicit choice, done per connection after saving — see ../../administracao/credenciais-e-rotacao.md.
- Token Bearer (
token) — Optional — becomes Authorization: Bearer <token>.
Secrets are never re-displayed and are redacted in every error/log (raw token, URL-encoded and in JSON).
Form fields#
| Campo | Rótulo | Tipo | Obrigatório | Observação |
|---|---|---|---|---|
url | File URL | text | yes | The table name comes from the file name in the URL (vendas.csv → vendas). |
cabecalhos | Extra headers | text | no | One header per line, in the format Name: value. |
token 🔒 | Token Bearer | password/secret | no | secret (encrypted; external vault optional); Optional — becomes Authorization: Bearer <token>. |
Step-by-step#
- In the menu Dados → Conexões, use Nova conexão.
- Choose Arquivo por HTTP in the catalog.
- Fill in the form fields (see the table above).
- Use Testar conexão. The result is split into three capabilities, each with OK, Failed, Not applicable or Not tested. In this sheet they mean: Network — the storage service endpoint is reachable from the application server; Authentication — the credential from the form (access key or service account, not username and password) was accepted; Read — it was possible to list the objects of the bucket/container under the provided prefix (the displayed count is of visible objects, not of tables).
- 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 executing anything. After that, Ativar agenda and Executar agora are separate actions.
Example — connection test#
Sample configuration (all values are fictitious; secrets appear masked):
# Exemplo sintético (valores fictícios — não são credenciais reais)
url = <url>
cabecalhos = <cabecalhos>
token = •••••• (cifrado — nunca exibido)Expected result#
Testar conexão returns the number of visible objects under the provided 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#
- Pagination: hard cap per run (default 10,000 pages / 5,000,000 rows); loop-guard is applied.
- SaaS load: default
batchSize5,000,maxRows200,000 per resource. - Estimated volume: ~0.5 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 credential 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 passes through secret redaction (raw, URL-encoded and in JSON).
- Production does not mock: a path that would hit a mock triggers the production guard (explicit failure instead of simulating success).
Common errors#
- Authentication failed — the credential for this connector is NOT username and 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 permission for 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 — check the exact bucket name and the prefix (folder). A prefix with no objects returns zero visible objects, not an error.
- File in unsupported format — object storage transports files; the pipeline must be able to read the content (CSV, JSON or Parquet). An object in another format is ignored or fails to load, depending on the pipeline policy.
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.