Skip to the operations

Business data

Bling in a decision flow.

6 Bling operations a decision flow can call directly, with the credentials your own contract issued. The response is data the rest of the flow reads, branches on, and keeps in the trace.

Category
Business data
Type
Integration
Authentication
oauth2 refresh
Test environment
Production host only

Who they are

Brazilian ERP aimed at online sellers.

Bling handles orders, stock, invoicing and finances for small businesses, with a strong tilt towards e-commerce and marketplace sellers. It integrates with the Brazilian marketplaces and storefronts its customers sell through. Its current API uses the OAuth2 authorization-code grant and rotates the refresh token on every refresh.

What a flow can call

6 operations, each one a step you can place on the canvas.

  1. GET/contatos?numeroDocumento=$data.cnpj

    Find a contact by document

    Looks a customer or supplier up by CNPJ or CPF. This is the join between a decision and the ERP — everything below takes Bling's own contact id rather than a document number.

  2. GET/contas/receber?idContato=$data.bling_contact_id

    List receivables (contas a receber)

    What the company is owed and whether it arrived.

  3. GET/contas/pagar?idContato=$data.bling_contact_id

    List payables (contas a pagar)

    The other side of the ledger — what the company owes.

  4. GET/pedidos/vendas?idContato=$data.bling_contact_id

    List sales orders

    Order history for one contact — how much they buy and how often.

  5. POST/contatos

    Register a contact

    Writes the approved applicant into the ERP so the commercial team can invoice them without retyping anything.

  6. GET/produtos

    Verify the connection

    Lists products. No arguments, cheap, and it is the quickest way to confirm the token is live — which for this provider also proves the refresh cycle is working, because the token it used was almost certainly minted by a refresh rather th…

Where it sits in the decision

Business data calls have a natural place in a flow.

Accounting data describes a company's own books rather than its filings, which makes it the input for decisions about trading history and cash position. It arrives after the applicant has connected a source, so a flow reads it where it exists and falls back to submitted figures where it does not.

Whatever Bling returns is part of the run, so it is part of the record. When someone asks months later why an applicant was declined, the answer cites what came back at the time rather than re-fetching from a service whose answer has since changed.

  • 01Add Bling as a connection authenticating with oauth2 refresh.
  • 02Bling has one host for both environments, so guard test runs with your own credentials and limits.
  • 03Place a Connection node and pick an operation — “Find a contact by document” is usually the first one a flow needs.
  • 04Map the response into the fields your rules read, then test the whole path before it carries live traffic.

Common questions

Using Bling in a flow.

How do I connect Bling to a decision flow?

Add Bling as a connection in your workspace authenticating with oauth2 refresh, with the credentials your own contract issued — ArboRule calls the provider as you, and never holds a contract on your behalf. Once the connection exists, any flow in the workspace can place a Connection node and choose one of its operations. The credentials live on the connection, not in the flow, so a policy owner can use Bling in a decision without ever seeing the secret.

Can I test Bling without touching production?

Bling exposes one host for both environments, so there is no separate sandbox to point at. Test runs still execute in Sandbox and are recorded separately in decision history, but the call goes to the same place as production — so guard it with your own test credentials, rate limits, or data.

What can a flow call on Bling?

6 operations, including “Find a contact by document”, “List receivables (contas a receber)”, “List payables (contas a pagar)”. Each one is a step you place on the canvas and map into the fields your rules read, and most flows start with “Find a contact by document”. The list comes from the same manifest the engine uses to make the call, so this page cannot describe an operation the product does not have.

Where in a decision should Bling be called?

Accounting data describes a company's own books rather than its filings, which makes it the input for decisions about trading history and cash position. It arrives after the applicant has connected a source, so a flow reads it where it exists and falls back to submitted figures where it does not.

Also in Business data

Ready when you are

Wire Bling into a real decision.

Build the flow in Sandbox, connect your account, and watch the decision pull what it needs before it answers.

Read the docs