Skip to content

Automatic translation — the Portuguese version is the reference. View in Portuguese

Updated on 2026-10-04

Bling ERP — connector

Extracts orders, products, stock and financial data from the Bling ERP API and loads them into the Bronze layer.

On this page (15)

Read first: ../conectores.md (state map) and fichas.md (index of sheets).


What it is#

Extracts orders, products, stock and financial data from the Bling ERP API and loads them into the Bronze layer.

Supported ingestion modes:

  • Nós buscamos — We pull the data from your source.

What it's for#

Bring Bling ERP 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 the subscription overdue, suspended or canceled, the run is blocked.
  • Disablement: the ingestion run can be temporarily turned off (maintenance or incident). When that happens, the UI informs that the feature is unavailable at the moment.

Prerequisites#

  • A Bling ERP account with access to the data you want to ingest.
  • Create an application at developer.bling.com.br, authorize it on your Bling account (OAuth flow) and provide the generated Client ID, Client Secret and refresh token. Secrets are encrypted (AES-256-GCM) and are never shown again. Note: Bling rotates the refresh token on each renewal — we always store the newest one.

Credentials#

Authentication method: OAuth 2.0 (client id/secret + refresh token). All secrets are encrypted (AES-256-GCM) and never shown again. If authorization expires, just reconnect — the source and history are preserved.

Sensitive fields. They are encrypted (AES-256-GCM) and never reside 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 the credential of this connection to the external credential vault is an explicit choice made per connection after saving — see ../../administracao/credenciais-e-rotacao.md.

  • Client Secret (clientSecret)
  • Refresh token (refreshToken) — Issued during the application's OAuth authorization flow. It is automatically renewed at each synchronization.

Secrets are never re-shown and are redacted in all error/log output (raw token, URL-encoded and in JSON).

Form fields#

FieldLabelTypeRequiredNote
clientIdClient IDtextyesGenerated when creating the application in the Bling developer portal (developer.bling.com.br → Aplicativos).
clientSecret 🔒Client Secretpassword/secretyessecret (encrypted; external vault optional)
refreshToken 🔒Refresh tokenpassword/secretyessecret (encrypted; external vault optional); Issued in the application's OAuth authorization flow. It is automatically renewed at each synchronization.

Step-by-step#

  1. In the menu Dados → Conexões, use Nova conexão.
  2. Choose Bling ERP in the catalog.
  3. Fill in the form fields (see the table above).
  4. 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.
  5. Use Salvar conexão. Saving does NOT start any ingestion.
  6. 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.
  7. 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):

text
# Exemplo sintético (valores fictícios — não são credenciais reais)
clientId = exemplo-client-id-ficticio
clientSecret = •••••• (cifrado — nunca exibido)
refreshToken = •••••• (cifrado — nunca exibido)

Expected result#

Testar conexão returns the list of discovered tables/resources. After the first load, rows appear in your workspace's Bronze layer, ready for the pipeline.

Limits and costs#

  • Pagination: hard ceiling per run (default 10,000 pages / 5,000,000 rows); anti-loop guard.
  • SaaS load: default batchSize 5,000, maxRows 200,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#

  • 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 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 source.
  • Redaction: all error/log output is passed through secret redaction (raw, URL-encoded and in JSON).
  • Production does not fake: a path that would fall into a mock triggers the production guard (explicit failure instead of simulating success).

Common errors#

  • Credential refused (401/403) — the provider did not accept the credential: expired, revoked or missing necessary 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-After and retries; if it recurs, 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 terminates when the API cursor does not advance (anti-loop guard). If it happens in consecutive runs, open a support ticket with the connector and resource information.
  • Empty records 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 observability per connector (error rate, p50/p95, freshness).
  • A schema change at the source is flagged by schema drift (new column = info; removed column/type changed = attention).

Related#


Last review: 2026-10-04. Sheet auto-generated from the product connector catalog.

Related links