Bling on Orkestia

Orkestia is the backbone that connects software, AI, and the real world. Bling is a Brazilian ERP a lot of shops already keep stock, contacts, and billing in. This post is the connection: OAuth once, then bling.* workflows read and write what the catalog exposes.

Bling is a catalog domain, the same shape as Omie, Stripe, and GitHub. It is not a homepage product. If the books are in Bling, list them there. Do not keep a parallel spreadsheet as the ledger.

Omie is a different ERP. Pick the one you actually run. Omie on Orkestia.

Connect with OAuth

Bling uses OAuth2 against API v3. In Orkestia you start the authorize URL, sign in to Bling, and come back through the callback. By the time the connection is stored, an access token already exists. The provider verifies it and holds the session. You do not paste a long-lived password into a form.

Create an account, open Connections, pick Bling, finish the OAuth. If get_workflow_schema says has_prerequisites: true, that prerequisite is this connection.

What you run

The live names are in the catalog, filtered to Bling. Typical jobs are contacts, products, orders, and financial documents the library exposes. Writes follow whatever the catalog marks as available. If a type is missing, it is not a documentation omission. It is not in the catalog.

Start with a list. Read the payload. Then a mutate, after get_workflow_schema.

From MCP

whoami()
list_workflow_types(prefix="bling.")
get_workflow_schema("<type>")
get_workflow_prerequisites("<type>")
start_workflow(workflow_type="<type>", initial_data={...})
watch_workflow(workflow_id)

The token stays on the connection. An agent that lists products does not see it.

OAuth, then a list, then a write

The OAuth dance is easy to abandon halfway. If the connection test fails, start authorize again from the console. Do not paste a Bling token into MCP initial_data.

Once the connection tests, list. Contacts or products, whichever schema you opened. Confirm the payload is the Bling account you thought you connected. Only then a write.

Bling is the system of record for that company's books when you chose Bling. Orkestia will not keep a second ledger for you. Local files in an agent are staging, not the books. If the company is on Omie instead, use Omie. Connecting both and joining them on email is how duplicates appear.

Staff actors can run the same bling.* types a person can, under the roles you bound. Staff: actors that run the work.

What to read next

• The catalog
• Connect your AI tool, then run your first workflow
• Documentation
• Pricing

hello@orkestia.dev