Termene

Termene.ro is a Romanian company-data provider covering identity, financials, shareholders, insolvency, public procurement, court cases and tax-authority records. Agents look up a company by CUI and pull whichever data family a schema key selects.

Verified 2 actions Basic auth available

Termene website Platform Documentation Capability data verified 2026-08-27

A Romanian contract, invoice, or supplier form arrives carrying a CUI

Agent reads the CUI, strips an RO prefix, and checks the digit shape before spending a query

List Data Families reconciles the checks this workflow wants against the schema keys the account actually holds

Get Company Data runs once per held schema key and collects identity, financials, and whichever families are entitled

Agent posts a coverage summary naming the families it read and the ones it could not reach

The counterparty owner decides whether that coverage is enough to approve, or whether a missing family has to be bought first

What This Integration Enables

Termene.ro is built on a decision most data vendors do not make out loud. There is one route, one request body, and one field that determines what comes back: the schema key. Identity, financials, shareholders, insolvency, public procurement, court cases, and tax-authority records all arrive through the same call, and which of them your workflow can see is decided by the keys Termene issued to your account rather than by anything in the code. That is why this connector has two operations instead of twelve. There is genuinely nothing else to vary.

The practical consequence is worth stating plainly, because it shapes every workflow built on this connector: a Termene blind spot is a contractual fact, not a technical one. An agent cannot discover a family it has no key for, and it cannot infer one family from another. List Data Families exists to make that visible, naming what Termene sells so a workflow can say which checks it ran and which it could not. FlowRunner agents built on this connector are therefore explicit about their own reach, and the automation exceptions they raise are as often about missing entitlement as about a bad counterparty.

Without FlowRunner

Coverage assumed, never stated A due diligence file says what was found, not what was never checked

Identifiers gathered by hand Somebody retypes a CUI off a PDF before any check can start

An outage looks like a clean result A vendor-side failure returns nothing, and nothing reads like no findings

With FlowRunner

Coverage travels with the answer Every result names the data families read and the ones the account cannot reach

Identifiers read off the document The agent pulls and validates the CUI locally before the first billed call

Silence is treated as silence A failed call becomes an exception, never an empty section in a diligence report

Use Case Scenarios

Supplier onboarding that starts from the document

A new Romanian supplier returns a signed contract. The agent reads the CUI off it, strips the RO prefix that invoices commonly carry, and validates the digits locally so a typo fails immediately instead of consuming a query. It then calls Get Company Data with the identity key and pulls the registered name, address, and status, comparing them against what the supplier typed on the form. Where the account also holds a financial key, the same call pattern brings back the filed figures. The buyer sees one record with both halves already reconciled, rather than a lookup result and a form sitting in different tabs.
A periodic sweep across the Romanian book of business

On a schedule, the agent walks the active Romanian counterparties and runs Get Company Data with each key the account holds. Movements matter more than levels here: a change of registered status, a new shareholder, a first appearance in a court case family. Anything that moved appends to a review sheet in Google Sheets and posts as a short digest to Slack. Because Termene sells by monthly query volume rather than by rate, the sweep is sized against the plan rather than throttled against a per-second limit, and the agent checks its own consumption before fanning out over a long list.
A VAT position that is assembled from more than one source

Romanian VAT work rarely rests on a single register. The agent pulls the Termene record for identity and tax-authority context, then confirms the VAT position on a specific date through Verificare TVA and, for an intra-community supply, through VIES API. Where the three sources agree, the invoice moves. Where they disagree, or where one of them is unreachable, the agent assembles what each one said and hands it over. Whether the supply qualifies for a particular treatment is a tax position, and a tax position is taken by the people who sign the return.

Human-in-Loop Highlight

Termene's API has no lookup by name. Version 2 resolves a company by CUI and by nothing else, so when the identifier on a document is wrong, unreadable, or absent, there is no route that turns a company name back into a CUI. The agent cannot search its way out, and guessing an identifier would attach a diligence file to the wrong legal entity. Compounding this, a credential or entitlement failure here does not arrive as a clean 401: Termene validates the request body before it authenticates, so a bad key comes back as a server error that reads like an outage. Both cases end the same way. The agent stops and asks: "Contract SC-2291 names Alfa Distributie SRL but the CUI on the header does not resolve. I have no route from a name to a CUI, and no key for the insolvency family on this account. Confirm the CUI, or approve the counterparty on identity and financials alone?" A person answers, because approving a supplier on partial coverage is a risk decision, and recording an unreachable family as a clean result would be a lie the workflow told quietly.

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

2 actions

Companies

Get Company Data Reads data about a Romanian company by its CUI. Termene publishes one endpoint for everything, so which data comes back is decided by the Schema Key rather than by the route: the same call returns identity, financials, shareholders, court cases, or procurement records depending on the key supplied. Use it once per family the workflow needs, and set a default key on the connection for the family used most.

Reference

List Data Families Names the data families Termene sells, as a reference for which Schema Key to request from the vendor. It makes no API call, because the keys are issued per account and cannot be discovered. Use it to state what a workflow is entitled to read before it claims a check was performed.

Frequently Asked Questions

What can FlowRunner do with Termene?

FlowRunner agents can run Get Company Data and List Data Families in Termene.

Does connecting Termene to FlowRunner require OAuth?

No. Termene connects to FlowRunner with basic authentication (a username and password), no OAuth flow required.

Can Termene trigger a FlowRunner workflow automatically?

Termene doesn't currently expose triggers in FlowRunner. It connects as an action step inside workflows started by another trigger.

Start building with Termene

Free plan, no card required. Connect in minutes.

Start Building Free Talk to us