Skip to main content
Bling is a comprehensive business management platform that provides tools for invoicing (NFe), inventory control, sales management, and financial operations. It helps businesses streamline their operations with integrated solutions for e-commerce, accounting, and logistics.

​
Configuring Bling as a Source

In the Sources tab, click on the “Add source” button located on the top right of your screen. Then, select the Bling option from the list of connectors. Click Next and you’ll be prompted to add your access.

​
1. Add account access

You’ll need OAuth credentials to connect to Bling. You’ll need to provide:
  • Authorization: Log in with your Bling account to generate the access token. Make sure you use an account with sufficient privileges to access your Bling data.

​
2. Select streams

Choose which data streams you want to sync - you can select all streams or pick specific ones that matter most to you. The available streams include NFe (electronic invoices for products), NFSe (electronic invoices for services), products and sales orders.
Tip: The stream can be found more easily by typing its name.
Select the streams and click Next.

​
3. Configure data streams

Customize how you want your data to appear in your catalog. Select a name for each table (which will contain the fetched data) and the type of sync.
  • Table name: we suggest a name, but feel free to customize it. You have the option to add a prefix and make this process faster!
  • Sync Type: you can choose between INCREMENTAL and FULL_TABLE.
    • Incremental: every time the extraction happens, we’ll get only the new data - which is good if, for example, you want to keep every record ever fetched.
    • Full table: every time the extraction happens, we’ll get the current state of the data - which is good if, for example, you don’t want to have deleted data in your catalog.
Bling API only allows fetching historical data from 2025-01-01.
Once you are done configuring, click Next.

​
4. Configure data source

Describe your data source for easy identification within your organization, not exceeding 140 characters. To define your Trigger, consider how often you want data to be extracted from this source. This decision usually depends on how frequently you need the new table data updated (every day, once a week, or only at specific times). Optionally, you can determine when to execute a full sync. This will complement the incremental data extractions, ensuring that your data is completely synchronized with your source every once in a while. Once you are ready, click Next to finalize the setup.

​
5. Check your new source

You can view your new source on the Sources page. If needed, manually trigger the source extraction by clicking on the arrow button. Once executed, your data will appear in your Catalog.
For you to be able to see it on your Catalog, you need at least one successful source run.

​
Streams and Fields

Below you’ll find all available data streams from Bling and their corresponding fields:
Stream for managing electronic invoices (NFe).Key Fields:
  • id: Unique identifier for the NFe
  • tipo: The NFe type
  • situacao: The NFe status
  • numero: The NFe number
  • dataEmissao: The emission date (YYYY-MM-DD HH:MM:SS format)
  • dataOperacao: The operation date (YYYY-MM-DD HH:MM:SS format)
  • chaveAcesso: The access key
  • contato: Contact information including:
    • Basic info (id, nome)
    • Document info (numeroDocumento, ie, rg)
    • Contact details (telefone, email)
    • Address (endereco, numero, complemento, bairro, cep, municipio, uf, pais)
  • naturezaOperacao: Nature of operation information (id)
  • loja: Store information (id)
Stream for detailed NFe information.Key Fields:
  • id: Unique identifier for the NFe
  • tipo: The NFe type
  • situacao: The NFe status
  • numero: The NFe number
  • dataEmissao: The emission date
  • dataOperacao: The operation date
  • chaveAcesso: The access key
  • serie: The NFe series
  • valorNota: The invoice value
  • valorFrete: The freight value
  • xml: The XML content
  • linkDanfe: The DANFE link
  • linkPDF: The PDF link
  • optanteSimplesNacional: Simple National taxpayer flag
  • numeroPedidoLoja: Store order number
  • contato: Contact information (same as NFe stream)
  • naturezaOperacao: Nature of operation information
  • loja: Store information
  • transporte: Transport information including:
    • Freight details (fretePorConta)
    • Transporter info (nome, numeroDocumento)
    • Volumes
    • Label information (nome, endereco, etc.)
  • vendedor: Seller information
  • itens: Array of items with:
    • Basic info (codigo, descricao, unidade)
    • Quantities and values (quantidade, valor, valorTotal)
    • Product details (tipo, pesoBruto, pesoLiquido)
    • Fiscal information (classificacaoFiscal, cest, cfop)
    • Tax information (impostos)
  • parcelas: Payment installments with:
    • Basic info (data, valor)
    • Payment method (formaPagamento)
    • Additional details (observacoes, caut)
Stream for managing electronic service invoices (NFSe). Unlike NFe which is for products, NFSe is specifically for service-based transactions.Key Fields:
  • id: Unique identifier for the NFSe
  • numero: The NFSe number
  • numeroRPS: The RPS (Recibo Provisório de Serviços) number
  • serie: The NFSe series
  • situacao: The NFSe status
  • dataEmissao: The emission date (YYYY-MM-DD format)
  • valor: The service value
  • contato: Contact information including:
    • id: The contact ID
    • nome: The contact name
    • numeroDocumento: The document number
    • email: Email address
Stream for managing product catalog.Key Fields:
  • id: Unique identifier for the product
  • idProdutoPai: The parent product ID
  • nome: The product name
  • codigo: The product code
  • preco: The product price
  • precoCusto: The product cost price
  • estoque: Stock information including:
    • saldoVirtualTotal: Total virtual stock balance
  • tipo: The product type (P = Product, S = Service)
  • situacao: The product status (A = Active, I = Inactive)
  • formato: The product format (S = Simple, V = Variable)
  • descricaoCurta: Short product description
  • imagemURL: Product image URL
Stream for detailed product information.Key Fields:
  • id: Unique identifier for the product
  • nome: The product name
  • codigo: The product code
  • preco: The product price
  • tipo: The product type
  • situacao: The product status
  • formato: The product format
  • descricaoCurta: Short product description
  • imagemURL: Product image URL
  • dataValidade: Product validity date
  • unidade: Product unit
  • pesoLiquido: Net weight
  • pesoBruto: Gross weight
  • volumes: Number of volumes
  • itensPorCaixa: Items per box
  • gtin: GTIN code
  • gtinEmbalagem: Package GTIN code
  • categoria: Category information
  • estoque: Stock information including:
    • Limits (minimo, maximo)
    • Location (localizacao)
    • Balance (saldoVirtualTotal)
  • fornecedor: Supplier information including:
    • Basic info (id, codigo)
    • Contact details
    • Pricing (precoCusto, precoCompra)
  • dimensoes: Product dimensions
  • tributacao: Taxation information including:
    • Basic info (origem, ncm, cest)
    • Tax details (percentualTributos)
    • Additional codes and values
  • midia: Media information including:
    • Video URL
    • Images (external and internal)
  • estrutura: Product structure information
  • variacoes: Product variations with all relevant details
Stream for managing sales orders.Key Fields:
  • id: Unique identifier for the sales order
  • numero: The sales order number
  • numeroLoja: The store order number
  • data: The order date (YYYY-MM-DD format)
  • dataSaida: The departure date
  • dataPrevista: The expected delivery date
  • totalProdutos: The total products value
  • total: The total order value
  • contato: Customer information including:
    • Basic info (id, nome)
    • Type (tipoPessoa)
    • Document (numeroDocumento)
  • situacao: Order status information (id, valor)
  • loja: Store information (id)

​
Data Model

The following diagram illustrates the relationships between the core data streams in Bling. The arrows indicate the join keys that link the different entities.