Skip to the operations

Business data

Conta Azul in a decision flow.

5 Conta Azul 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

Accounting and financial management for Brazilian small businesses.

Conta Azul keeps a small company's books — sales, receivables, bank reconciliation and the reports an accountant needs — and is often set up by that accountant rather than by the business itself. It sits closer to the accounting end of the market than the operational ERPs do. Access is by OAuth2 authorization code.

What a flow can call

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

  1. GET/v1/customers?search=$data.cnpj

    Find a customer

    Looks a customer up by document or name. The join between a decision and the books: the calls below take Conta Azul's own uuid rather than a CNPJ.

  2. GET/v1/sales?customer_id=$data.contaazul_customer_id

    List sales

    Sales recorded against one customer — how much they buy and how often.

  3. GET/v1/financial-events?start_date=$data.period_start&end_date=$data.period_end

    List financial events

    Money in and out over a period. This is the affordability read for a company: what the books say actually moved, rather than what the applicant declared.

  4. POST/v1/customers

    Register a customer

    Writes the approved applicant into the books so the finance team can invoice them without retyping anything.

  5. GET/v1/person

    Verify the connection

    Returns the account the token belongs to. Cheapest way to confirm the connection works — and for this provider that also proves the refresh cycle is working, because the token in play was probably minted by a refresh rather than by the i…

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 Conta Azul 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 Conta Azul as a connection authenticating with oauth2 refresh.
  • 02Conta Azul 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 customer” 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 Conta Azul in a flow.

How do I connect Conta Azul to a decision flow?

Add Conta Azul 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 Conta Azul in a decision without ever seeing the secret.

Can I test Conta Azul without touching production?

Conta Azul 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 Conta Azul?

5 operations, including “Find a customer”, “List sales”, “List financial events”. 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 customer”. 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 Conta Azul 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 Conta Azul 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