Oblio

Oblio is Romanian invoicing and stock software. Agents issue proformas, delivery notices, and invoices, record collections, file e-Factura to the national SPV system, and look up the nomenclatures every document has to reference.

1 trigger 22 actions Session available

Oblio website Platform Documentation Capability data verified 2026-08-24

An order or a contract completion reaches the flow

List Clients and List Products resolve the counterparty and the rows

List VAT Rates confirms each row names a rate whose name and percentage both match a configured rate

Create Invoice issues the invoice in the chosen series, optionally raised from a proforma

Get Document reads it back with its collections, because a clean HTTP response is not an outcome here

The filing candidate posts to the finance owner with the fiscal code, the rows, and the total

A person confirms the fiscal details before Send E-Invoice files the invoice with the national system

What This Integration Enables

Oblio is Romanian invoicing and stock software, and this connector's center of gravity is not invoicing. It is e-Factura. The Romanian national system, SPV, is where an invoice goes to become something the state has seen, and Send E-Invoice is the operation that puts it there. That changes what an agent's job is on this integration. Assembling a correct document is the easy half. The valuable half is refusing to hand a document to a national registry until somebody has looked at the fields the registry cares about.

Everything else on the connector supports that. The nomenclature reads exist because a document has to name things Oblio already knows: a series with its next number, a VAT rate by name and percentage together, a client, a product, a stock management. Three registers are issued from here, and they mean different things. A proforma is a quote with no accounting effect. A notice is a delivery note whose stock movement is on by default, so it takes goods off stock unless you switch that off, which is the opposite of what the other two documents do. An invoice is the fiscal document. Create Invoice covers three shapes in one call: a plain invoice, an invoice raised from a proforma or notice with the rows carried across, and a reversal that also removes the collection recorded against the original.

Without FlowRunner

Issuing and filing treated as one act The invoice is considered done when the software accepted it

Success read from the response code A filing that was rejected for errors reports as a success, because the transport succeeded

Numbering repaired after the fact Documents are deleted out of the middle of a series and the gap has to be explained later

With FlowRunner

Issuing and filing kept apart The document exists locally first, and the submission to the state is its own reviewed step

Success read from the returned code The filing's own code is what decides whether it was accepted, still processing, rejected, or never sent

Numbering kept intact Unwinding a document uses the cancel path that keeps its number, and deletion stays where it is permitted

Use Case Scenarios

Storefront order to a Romanian invoice, filed once

An order completes in PrestaShop and the payment settles through Stripe. The agent resolves the buyer against List Clients and the lines against List Products, then checks each row's VAT rate against List VAT Rates, since a row has to name both the rate name and its percentage and both must match a configured rate. It issues the invoice with Create Invoice in the series that List Series says is next, and records the payment in the same call with the collect fields when the money has already arrived. The document then waits. Filing it with SPV is a separate, reviewed step, because that is the step that cannot be taken back.
Proforma out, invoice raised from it

For customers who need to approve a price before being billed, the agent issues a proforma with Create Proforma and stores the PDF with Download Document. A proforma has no accounting effect, so this costs nothing to get slightly wrong. When the customer accepts, Create Invoice raises the invoice from that proforma by naming it as the reference document, and the rows come across without the client or the product rows being restated. If the customer later cancels, the reversal shape of the same operation produces a document that also removes the collection recorded against the original, which is cleaner than assembling a credit note by hand.
Watching the register without trusting the delivery

The On Oblio Event trigger fires when an invoice is saved, updated, or canceled, when a collection is recorded, or when stock moves. Oblio does not sign its deliveries, so the agent treats each one as a notification rather than as data: it reads the referenced document back with Get Document before acting on anything in it. Confirmed events become a running feed into Slack for the finance team, with cancellations called out separately, since a canceled document keeps its number in the register and someone usually wants to know why.

Human-in-Loop Highlight

Send E-Invoice files an invoice with the national SPV system, and that is the point on this connector where Oblio's own safety net stops applying. Inside Oblio, unwinding is survivable: Cancel Document marks a document void and keeps it in the register with its number, and Restore Document puts it back in force. Oblio can undo what Oblio did. It cannot undo what the state received. Delete Document does not help either, because Oblio only permits deleting the last document in a series; anything earlier has to be canceled so the numbering stays unbroken.

The filing also refuses to fail loudly. Send E-Invoice answers with its own code, where one means filed, zero means it reached SPV and is still processing, two means rejected for errors, and minus one means it was never sent. A flow that reads the HTTP status instead of that code will report a rejected filing as a success and move on. So the agent does the assembly, reads the code rather than the status, and stops before the submission: "Invoice OBL 2026-1187 for 14,280 lei is ready to file. The client's fiscal code came from the storefront checkout field, not from a verified client record, and two rows use the reduced VAT rate. Confirm the fiscal code and the rates, or hold this one?" A person answers in a moment. What they are approving is not the invoice. It is the act of putting it in front of a national registry, which is a different decision and deserves its own.

Agent processes routinely

Detects exception requiring judgment

Clear match Continues automatically

Ambiguous Routes to human via preferred channel

Human decides

Agent resumes with decision

Agent Capabilities

22 actions

Nomenclatures

List Companies Lists the companies this account can reach, which is where the fiscal code every other operation needs comes from.
List VAT Rates Lists the VAT rates configured for a company. A document row has to name both the rate name and its percentage, and both must match one of these.
List Clients Lists the clients of a company, optionally narrowed by name or fiscal code.
List Products Lists the products of a company. A stocked product carries a stock breakdown per management, and a service does not.
List Series Lists the document series with the next number each will assign, which is where the series name every document needs comes from.
List Languages Lists the foreign languages a company can issue documents in. Romanian is always available and is the default.
List Managements Lists the stock managements of a company. It answers only when stock keeping is switched on for that company.

Documents

Create Invoice Issues an invoice, optionally raised from a proforma or notice and optionally collected in the same call. An issued invoice cannot be edited afterwards.
Create Proforma Issues a proforma, which has no accounting effect and is the document an invoice is later raised from.
Create Notice Issues a delivery notice. Unlike the other documents its stock movement is on by default, so it takes goods off stock unless that is switched off.
Get Document Reads one document by its type, series name, and number, including the collections recorded against it. The read back step after any event delivery.
Download Document Downloads a document as a PDF into FlowRunner file storage, following the link Oblio returns for it.
List Invoices Lists the invoices issued in a company, filtered by series, date range, client, or state.
Collect Invoice Records a payment against an invoice. A receipt collection needs a receipt series; every other kind needs the payment document's number.
Cancel Document Marks a document canceled, keeping it and its number in the register. The normal way to unwind a document.
Restore Document Restores a document that was canceled, returning it to force.
Delete Document Deletes a document. Only the last document in a series can be deleted; anything earlier has to be canceled instead so the numbering stays unbroken.

e-Factura

Send E-Invoice Files an invoice with the Romanian e-Factura SPV system. The answer carries its own code, where one is accepted, zero is still processing, two is rejected for errors, and minus one is not sent. The operation this page's human gate exists for.
Download E-Invoice Archive Downloads the e-Factura SPV archive of an invoice into FlowRunner file storage.

Webhooks

List Webhooks Lists the webhooks registered on the account, including any the trigger installed.
Create Webhook Registers a webhook. The endpoint must answer with the challenge value Oblio sends it, or Oblio refuses to register it.
Delete Webhook Removes a webhook from the account by its identifier.

Triggers

1 triggers

Event Triggers

On Oblio Event Fires when Oblio reports the chosen event, such as an invoice being saved or a collection being recorded. Oblio verifies the callback by challenge at registration and on every delivery, which FlowRunner answers automatically. It does not sign its deliveries, so a payload is a notification to act on rather than trusted data, and a flow that cares about the contents should read the record back with Get Document.

Frequently Asked Questions

What can FlowRunner do with Oblio?

FlowRunner agents can run List Companies, List VAT Rates, and List Clients in Oblio, plus 19 more actions.

Does connecting Oblio to FlowRunner require OAuth?

No. Oblio connects to FlowRunner with session-based authentication, no OAuth flow required.

Can Oblio trigger a FlowRunner workflow automatically?

Yes. Oblio supports 1 trigger that can start a FlowRunner workflow automatically.

Start building with Oblio

Free plan, no card required. Connect in minutes.

Start Building Free Talk to us