FLOWii

Connect AI agents to FLOWii, a Slovak CRM and business management suite for small businesses. Agents create partners and business cases, log communications, assign tasks, and read the orders and goods catalog behind each deal.

27 actions Custom auth available

Platform Documentation ↗

A lead list, a form submission, or a scheduled poll starts the run

Get Allowed Companies returns the company databases this account can actually reach

Get User Permissions confirms the connection may write into the chosen company

List Partners searches the resolved company for an existing partner before anything is created

Create Partner writes the customer, and Create Business Case opens the opportunity against it

Create Communication logs the call or email that started the conversation

The owner is told which company database was written to and what was created there

A person confirms the company id and the enum mapping before a batch import commits

What This Integration Enables

FLOWii is a Slovak business management suite, and the shape of its API tells you it was built for real small businesses rather than for a spec sheet. Records are partners rather than accounts and contacts, deals are business cases, and activity is communications, because that is the vocabulary the businesses using it already had. The single most consequential design fact is that a FLOWii account can hold several separate company databases, and almost every action requires a Company. That is not a parameter to be filled in and forgotten. It is the choice of which legal entity's books an agent is about to write into, which is why Get Allowed Companies is the first call any serious flow makes.

Two further details shape how agents behave here. Enum fields are stored as numbers with Slovak labels, so partner type, task state, communication state, and communication direction are submitted as numeric codes while the dropdowns present the vendor's exact labels, for example the task states Prebieha, Dokončené, and Zrušená. The connector maps label to wire value, but any flow that constructs a code from data rather than from a picker is asserting something it should be able to justify. Reads come back in the JSON:API shape with a zero based page index, so paging is explicit. Authentication is a two legged exchange: the configured API Key, User Name, and Password are traded at the token endpoint for a short lived bearer token, and both the Api-Key header and the bearer travel on every subsequent call, with the token expiring in roughly ten minutes and being renewed automatically within a run. FLOWii ships no triggers to FlowRunner, so change detection is polling: List Partners, List Business Cases, and List Communications on a schedule, comparing against what the last run saw. Read the scope honestly before you design around it. Partners, business cases, and tasks support full create, update, and delete. Communications support create and read but no update or delete. Orders and Goods are read only here, so a flow can report on the catalog and on orders but cannot raise one. Deletes on partners, business cases, and tasks are permanent, which is where the digital andon cord belongs.

Without FlowRunner

Several company databases, one habit An import runs against whichever company was last used and nobody checks which

Slovak labels meet English integrations Task and communication states get written as guessed numbers because the labels do not translate cleanly

Activity never reaches the record Calls and emails happen and the business case shows no sign of them a month later

With FlowRunner

The destination is resolved first The allowed companies are listed and the target database is named before a single record is written

Enum codes are mapped, not guessed Numeric wire values are resolved from the vendor's own labels and confirmed before a batch commits

Communications land on the case Calls, emails, and meetings are logged against the right partner and user as they happen

Use Case Scenarios

A lead list that lands in the right company database

Prospects collect in Google Sheets from a trade show. Before writing anything, the agent calls Get Allowed Companies to enumerate the company databases the connection can reach, and Get User Permissions to confirm the account may write into the intended one. It then calls List Partners scoped to that company, filtering on name, to find out who already exists. New companies become Create Partner with the partner type resolved from the vendor's own label rather than a hardcoded number, and each gets a Create Business Case opening the opportunity. Get Partner Contacts is used on matched partners to see who the business already knows there, so a second contact is not created for the same person. The operator opens FLOWii to find the trade show already filed under the correct entity.

Calls and emails that become a legible history

Sales conversations happen in an inbox and on a phone, and by default they leave no trace in the CRM. On a schedule the agent reads completed calls and sent emails from the tools where they actually happened, matches each to a partner using List Partners within the resolved company, and calls Create Communication with the direction and state set from the vendor's Slovak labels. Where the conversation belongs to an open opportunity, Read Business Case loads the current record and Update Business Case reflects the new expected value or stage. A row is appended to a shared activity log for reporting. The business case stops being a name and a number and starts being a record of what was actually said.

A weekly picture assembled from the modules that hold it

Each week the agent walks List Business Cases through its zero based pages for the resolved company, joining each case to its partner with Read Partner and to its follow up work with List Tasks. It reads List Orders and Read Order to see which cases have already converted into real orders, and List Goods to resolve the catalog items involved, both of which are read only surfaces so nothing is written back. The result is a summary sent to the owner through Brevo naming open business cases with no communication logged in the period, tasks past their due date, and cases whose value changed. Where the report shows a newly won deal, a separate flow sends the customer an onboarding message and adds them to a nurture list.

Human-in-Loop Highlight

The gate on FLOWii is not the content of a record. It is the destination. Almost every action on this connector requires a Company, because a FLOWii account can hold several separate company databases, and the API will accept a valid company id without any interest in whether it is the one you meant. An import that resolves the wrong company does not fail. It succeeds completely, writing a hundred real partners and a hundred real business cases into a different legal entity's database, where they are indistinguishable from records the business actually created. Delete Partner and Delete Business Case are permanent with no recovery, so cleaning up afterwards means destroying records in a database the operator did not intend to touch in the first place, using an irreversible operation, under time pressure. The enum mapping compounds it: partner type, task state, and communication state are numeric wire values behind Slovak labels, so a batch that also guessed a code writes a hundred records that are in the wrong place and in the wrong state. So the agent resolves and asks before it commits. It calls Get Allowed Companies and Get User Permissions, prepares the first record without sending it, and posts to the operator: "Ready to import 118 partners and open a business case for each. Target company resolved as id 4, name Stavby s.r.o., one of 3 companies this connection can reach. Partner type mapped to the label Odberateľ, business case state mapped to Prebieha. Sample record attached. 14 rows matched an existing partner in company 4 and will be updated instead of created. Confirm company 4 is the right database and the two mappings are right?" One reply covers both questions. Only then does Create Partner run, and it runs scoped to the company a person named out loud.

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

27 actions

Account

Get Allowed Companies Returns the company databases the connection can reach. This is the first call in any flow that writes, because it resolves which entity's records are about to change.
Get User Permissions Returns what the authenticated user is permitted to do. Used as the preflight check before a batch commits, so a run fails at the start rather than halfway through.

Partners

List Partners Returns partners for a company in the JSON:API shape, paged with a zero based page index. Used to find an existing customer before creating a second one.
Read Partner Retrieves a single partner. Used to load the customer record behind a business case, an order, or a communication.
Create Partner Creates a partner (a company or a person) within the resolved company. Partner type is submitted as a numeric code behind the vendor's own Slovak label.
Update Partner Updates an existing partner. Used to keep customer details aligned with a source of truth outside FLOWii.
Delete Partner Deletes a partner permanently with no recovery. Runs only on a set a person has approved.
Get Partner Contacts Returns the contacts attached to a partner. Used to avoid creating a second record for someone the business already knows.

Business Cases

List Business Cases Returns business cases (sales opportunities) for a company, paged with a zero based index. Used as the polling target for pipeline change detection, since no trigger is available.
Read Business Case Retrieves a single business case. Used to confirm the current state and value before proposing a change.
Create Business Case Opens a business case against a partner. Used when a qualified opportunity appears from a form, a call, or an import.
Update Business Case Updates a business case, including its value and state. Used to keep the pipeline in step with quoting and delivery.
Delete Business Case Deletes a business case permanently. Held behind human approval, since the opportunity history goes with it.

Tasks

List Tasks Returns tasks for a company with paging. Used for follow up coverage and overdue reporting.
Read Task Retrieves a single task with its state. Used to confirm whether work was actually completed.
Create Task Creates a task and assigns it to a user. Task state is a numeric code behind labels such as Prebieha, Dokončené, and Zrušená.
Update Task Updates a task, including its state and assignment. Used to close out follow ups the flow itself satisfied.
Delete Task Deletes a task permanently.

Communications

List Communications Returns logged communications for a company. Used to detect business cases that have gone quiet.
Read Communication Retrieves a single communication with its state and direction. Used to load the detail of a logged interaction.
Create Communication Logs a call, email, or meeting against a partner and a user, with state and direction submitted as numeric codes behind the vendor's labels. Communications can be created and read through this connector but not updated or deleted.

Orders

List Orders Returns orders for a company. Read only, used to see which business cases have converted into real orders.
Read Order Retrieves a single order. Read only, used to reconcile an opportunity against what was actually ordered.

Goods

List Goods Returns the goods catalog for a company. Read only, used to resolve catalog items referenced by orders and business cases.
Read Good Retrieves a single catalog item. Read only, used to attach a real product name and price to a report.

Users

List Users Returns the users on the account. Used to resolve an owner or assignee before writing a task or a communication.
Get Current User Returns the user the connection is authenticated as. Used to confirm which identity a flow's writes will be attributed to.

Frequently Asked Questions

What can FlowRunner do with FLOWii?

FlowRunner agents can run Get Allowed Companies, Get User Permissions, and List Partners in FLOWii, plus 24 more actions.

Does connecting FLOWii to FlowRunner require OAuth?

FLOWii uses a custom authentication method to connect to FlowRunner.

Can FLOWii trigger a FlowRunner workflow automatically?

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

Start building with FLOWii

$100 in credits. No card required. Connect in minutes.

Start Building Free Talk to us