Read first:
../conectores.md(state map) andfichas.md(index of sheets).
What it is#
Ingests CSV files, which you upload to the receiving area of your environment (mode "You deposit"). To read from a bucket of yours, the connector is the one for the storage service itself.
Supported ingestion modes:
- You deposit — You deposit the data in our cloud.
What it's for#
Bring CSV 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.
Avoid sending files with an unstable schema without first checking profiling and schema drift.
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 canceled subscription, the run is blocked.
- Shutdown: the ingestion run can be temporarily disabled (maintenance or incident). When this happens, the screen indicates the feature is unavailable at the moment.
- Upload (mode "You deposit"): the file goes to the receiving area of your workspace.
Prerequisites#
- The files you will upload (mode "You deposit").
Credentials#
This connector requires no secrets of its own (upload mode / no credential on the platform).
Secrets are never re-displayed and are redacted in every error/log (raw token, URL-encoded and in JSON).
Form fields#
Mode "You deposit" (push)
| Field | Label | Type | Required | Notes |
|---|---|---|---|---|
delimiter | Delimiter | select | no | default: ,; options: , / ; / \t / | |
Step-by-step#
- In the menu Dados → Conexões, use Nova conexão.
- Choose CSV in the catalog and select the ingestion mode.
- Fill in the form fields (see the table above).
- Upload the files. A file format only accepts deposit — there is no connection to test here.
- 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. Afterwards, Ativar agenda and Executar agora are separate actions.
Example — connection test#
Sample configuration (all values fictitious; secrets appear masked):
# Exemplo sintético (valores fictícios — não são credenciais reais)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.
- Estimated volume: ~0.5 GB/month (catalog estimate, not a 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 in their own datalake (
<prefix>_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 origin.
- Redaction: every error/log is redacted for secrets (raw, URL-encoded and in JSON).
- Production doesn't mock: a path that would fall into mock triggers the production guard (explicit failure instead of simulating success).
Common errors#
- Delimiter/encoding (CSV) — check the delimiter and prefer UTF-8; glued columns usually indicate the wrong delimiter.
- JSON format — choose between lines (ndjson) and a single array according to the file.
Troubleshooting#
- Use Testar conexão to isolate credential/network issues before scheduling.
- Monitor the 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#
../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.