Skip to the operations

Business data

Omie in a decision flow.

6 Omie 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
body credentials
Test environment
Production host only

Who they are

Cloud ERP for Brazilian small and mid-sized businesses.

Omie runs the back office of a Brazilian small business — invoicing, receivables, payables, stock and the accounting that follows from them. It sells largely through accounting firms, which is why so many of their clients end up on it. Its API is RPC over HTTP: one address per resource, with the method named in the request body.

What a flow can call

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

  1. POST/geral/clientes/

    List customers

    Pages through the customers registered in the Omie company.

  2. POST/geral/clientes/

    Find a customer by CNPJ

    Looks one customer up by document. This is the join between a decision and the ERP: the flow knows a CNPJ, and everything below needs Omie's own codigo_cliente_omie.

  3. POST/financas/contareceber/

    List receivables (contas a receber)

    What the company is owed and whether it arrived.

  4. POST/financas/contapagar/

    List payables (contas a pagar)

    The other side of the ledger — what the company owes its own suppliers.

  5. POST/geral/clientes/

    Register a customer

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

  6. POST/geral/empresas/

    Verify the credential

    Lists the companies the credential can see. Cheapest way to confirm a connection works and to check which Omie company the key pair belongs to — which matters, because a key is scoped to one company and a customer with several needs one…

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 Omie 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 Omie as a connection authenticating with body credentials.
  • 02Omie has one host for both environments, so guard test runs with your own credentials and limits.
  • 03Place a Connection node and pick an operation — “List customers” 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 Omie in a flow.

How do I connect Omie to a decision flow?

Add Omie as a connection in your workspace authenticating with body credentials, 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 Omie in a decision without ever seeing the secret.

Can I test Omie without touching production?

Omie 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 Omie?

6 operations, including “List customers”, “Find a customer by CNPJ”, “List receivables (contas a receber)”. Each one is a step you place on the canvas and map into the fields your rules read, and most flows start with “List customers”. 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 Omie 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 Omie 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