Read before:
../conectores.md(state map) andfichas.md(index of datasheets).
What it is#
Reads CSV, JSON and XLSX files from a Backblaze B2 bucket (S3-compatible API, application key, SigV4) and loads into the Bronze layer; Parquet is recognized and loaded directly.
Supported ingestion modes:
- Nós buscamos — We fetch the data from your source.
What it's for#
Bring data from Backblaze B2 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 by 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 allowed by the plan).
- Access: requires an active workspace — with a delinquent, suspended or canceled subscription, the run is blocked.
- Shutdown: ingestion runs can be temporarily disabled (maintenance or incident). When that happens, the UI indicates the feature is currently unavailable.
Prerequisites#
- A Backblaze B2 account with access to the data you want to ingest.
- In Backblaze, under Application Keys, create a key restricted to the bucket with read permissions (listBuckets, listFiles, readFiles). Provide the S3 endpoint shown on the bucket page, the bucket name and the keyID / applicationKey pair; the key is encrypted and never shown again.
Credentials#
Authentication method: API Key generated in the provider console, sent in header/parameter.
Sensitive fields. They are encrypted (AES-256-GCM) and are never stored in the connection config, pipeline definition, export or DAG. By default the encrypted value is stored in the database; moving the credential from this connection to an external secrets vault is an explicit choice made per connection after saving — see ../../administracao/credenciais-e-rotacao.md.
- applicationKey (
secretAccessKey)
Secrets are never re-displayed and go through redaction in any error/log (raw token, URL-encoded and in JSON).
Form fields#
| Campo | Rótulo | Tipo | Obrigatório | Observação |
|---|---|---|---|---|
endpoint | Endpoint S3 | text | yes | Shown on the bucket page (Endpoint). Region is inferred from the endpoint. |
bucket | Bucket | text | yes | — |
prefix | Prefix / folder | text | no | Each subfolder becomes a table; sibling files become partitions of the same table. |
region | Region | text | no | — |
accessKeyId | keyID | text | yes | — |
secretAccessKey 🔒 | applicationKey | password/secret | yes | secret (encrypted; external vault optional) |
Step by step#
- In the menu Dados → Conexões, use Nova conexão.
- Choose Backblaze B2 in the catalog.
- Fill in the form fields (see the table above).
- Use Testar conexão. The result is reported across three capabilities, each with OK, Failed, Not applicable or Not tested. In this datasheet they mean: Network — the storage service endpoint is reachable from the application server; Authentication — the credential in the form (access key or service account, not username/password) was accepted; Read — it was possible to list the objects in the bucket/container under the provided prefix (the displayed count is of visible objects, not 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 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 are masked):
# Exemplo sintético (valores fictícios — não são credenciais reais)
endpoint = <endpoint>
bucket = meu-bucket-exemplo
prefix = dados/2026/
region = us-east-1
accessKeyId = AKIAEXEMPLOFICTICIO0
secretAccessKey = •••••• (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 ceiling per run (default 10,000 pages / 5,000,000 rows); loop-guard in place.
- SaaS load: default
batchSize5,000,maxRows200,000 per resource. - Estimated volume: ~3 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 (
<prefix>_bronze/_silver/_gold); there is never leakage between workspaces. - Encrypted secrets: sensitive material is encrypted with AES-256-GCM before being persisted. The external credentials 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 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 a mock triggers the production guard (explicit failure instead of simulating success).
Common errors#
- Authentication failed — this connector's credential is NOT username/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 of 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 — verify the exact bucket name and prefix (folder). A prefix with no objects returns zero visible objects, not an error.
- File in unsupported format — object storage transports files; the pipeline needs to be able to read the content (CSV, JSON or Parquet). An object in another format is ignored or fails the load, according to 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, ceilings and workspace security
Last revision: 2026-10-04. Datasheet automatically generated from the product connector catalog.