Fidoo

Fidoo is a Czech corporate expense-management platform with prepaid company cards, expense approval, and travel reports. Agents load and unload cards, manage users, approve expenses, read travel requests and reports, and read the accounting dimensions each item is coded against.

Verified 62 actions API key available

Fidoo website Platform Documentation Capability data verified 2026-08-25

The monthly allowance run starts from the payroll calendar

List Users returns who is active and List Cards resolves each person's card

List Personal Billings pulls what each employee still owes or is owed back

Get Accounts confirms the funding account covers the run total

The agent drops leavers and anyone whose card is inactive

The agent posts the load list with names, amounts, and the run total

Finance approves the list, and only then does Load Cards queue the run

What This Integration Enables

Fidoo funds spending before it happens. Money moves onto a prepaid company card, an employee spends it, and the expense comes back coded against the cost, project, category, and VAT dimensions that the finance team owns. That order of operations is what makes the platform worth automating, because the interesting work sits either side of the card: deciding what to fund, and turning what was spent into a bookkeeping entry.

FlowRunner agents run the funding side, load and unload cards, and poll the asynchronous status of both. They keep users in step with the HR system, read card, cash, and account transactions, approve or reject expenses in batches, and maintain every accounting dimension expenses are coded against. They also cover the travel and mileage side, where a journey's type is a payroll input rather than a label. The connector's write operations are where FlowRunner's human-in-the-loop discipline earns its place, because loading a card is the moment company money becomes an employee's to spend.

Without FlowRunner

Funding by spreadsheet Someone assembles the monthly load list by hand and keys it into the card portal

Coding decided at close Cost allocation, project, and VAT coding get sorted out weeks after the money was spent

Approvals in a queue nobody owns Expenses wait for whoever notices them, and the mileage log is reconstructed from memory

With FlowRunner

Funding as a reviewed run The agent builds the list from live user and card data and a person approves it once

Coding carried on the record Dimensions are kept current from the source systems, and the accounting key rides the expense through approval

Approvals routed with context Expenses arrive where the approver already works, with the receipt and the items attached

Use Case Scenarios

The monthly allowance run

The payroll calendar starts the flow. The agent calls List Users filtered on last modification to catch joiners and leavers since the previous run, resolves each person's card with List Cards, and drops anyone deactivated or without an active card. Get Accounts confirms the funding account covers the total. The proposed list posts into Slack with names, amounts, and the run total. Once finance approves, Load Cards queues the run with the payroll run id set as Customer Process ID, and Get Load Status is polled until every card reports finished. Failures come back per card, so one refusal does not strand the rest.
Expenses coded and pushed to the ledger

On a schedule the agent lists expenses modified since the last pass, pulls their line items with Get Expense Items, and reads the VAT breakdown and accounting codes on each. Items that match a known vendor pattern get stamped with the accounting system's key through Edit Expense, since that reference survives the whole approval chain. Approved expenses and their receipts flow into Xero or a general ledger staged in Google Sheets. Anything above a threshold, or coded to a project with no budget left, is held for a person rather than pushed.
A mileage log that survives an inspection

Company vehicles accumulate journeys that a tax inspection reads as a continuous odometer trail. On a schedule the agent calls Get Journey Log Period for each vehicle, which returns the previous period alongside the current one, and compares the closing reading of one with the opening reading of the next. A gap means an unlogged journey. The agent posts the vehicle, the two readings, and the size of the gap into Microsoft Teams for the fleet owner, who either supplies the missing trip or records it as personal. Journey Type is not cosmetic here, because a personal journey in a company car is what a taxable benefit is computed from.

Human-in-Loop Highlight

Load Cards is the operation that turns company money into an employee's balance, and it is asymmetric on purpose. The load is queued, not immediate, so the confirmation arrives later from Get Load Status. Once it lands, the card is spendable, and the only way back is Unload Card, whose Full Unload sweeps whatever is left rather than what you put on. Overload a hundred cards and the recoverable amount is only the part nobody spent in the meantime. So the allowance agent builds the list and stops. It posts: "Monthly load run, 84 cards, 412,000 CZK against an account balance of 505,000 CZK. Three people joined this month and two left, both dropped. Approve to queue?" Finance answers once, for the run. The agent handles the polling, the per card failures, and the retries.

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

62 actions

Account

Get User Info Tests the connection and returns who the API key belongs to.
Get Accounts Returns the Fidoo accounts with their currency and balance. The pre-flight check before any bulk card load, because the money comes from here.

Users

List Users Lists users with full-text search and state filtering. The date filters read last modification, which is what makes an incremental sync possible.
Get User Retrieves one user by their Fidoo id.
Get User By Email Finds a user by email address. The lookup to use when a flow starts in an HR system.
Get User By Employee Number Finds a user by payroll employee number. The join key most payroll and accounting systems already hold.
Add User Creates a user. Phone is required rather than optional, because it backs card and application security.
Update User Updates a user's details, cost centre, or default project. Omitted fields are left alone.
Activate User Reactivates a deactivated user.
Deactivate User Deactivates a user without deleting them. The step a leaver process actually wants, because history stays intact.
Delete User Permanently deletes a user. Refused unless they hold no role, no tasks, no reports, and no card.
Activate Application Access Gives a user access to the application and sends the activation email. Can set their email at the same time.

Cards

List Cards Lists the prepaid company cards, optionally narrowed to one user.
Load Card Moves money from the Fidoo account onto one card. Asynchronous, so the reply is a process token rather than a funded card.
Load Cards Loads many cards in one call. The monthly allowance run, with each card succeeding or failing on its own.
Get Load Status Reports where queued loads have got to. It takes the same list shape the load returned.
Unload Card Takes money back off a card. Full Unload sweeps whatever remains without reading the balance first, which avoids a race against live spending.
Unload Cards Unloads many cards in one call. The end of project or end of year sweep.
Get Unload Status Reports where queued unloads have got to.

Transactions

List Card Transactions Lists card transactions over a settlement date range. Held authorizations can be included, but the vendor warns they may change or disappear, so they are for showing an employee their spend rather than for reconciling.
List Cash Transactions Lists cash transactions, the petty cash side of the ledger.
List Account Transactions Lists movements on the Fidoo account itself, including top-ups, loads, unloads, and fees.
List Personal Billings Lists what each employee owes the company or is owed back once their expenses settle.

Expenses

List Expenses Lists expenses across a large filter set, including last modification, which turns a nightly full export into an incremental one.
Get Expense Items Returns the line items on one expense, with VAT breakdown and accounting codes.
Edit Expense Renames an expense or stamps your own reference on it. External Reference ID is the join back to the accounting system and survives the whole approval chain.
Approve Expenses Approves up to fifty expenses in one call. The reply carries a per expense result, so one failure does not fail the batch.
Reject Expenses Rejects up to fifty expenses in one call, sending them back down the approval chain.
Download Receipt Downloads a receipt image or PDF. It needs both the receipt id and the expense it belongs to.

Travel

List Travel Requests Lists travel requests, the permission side, before a trip happens.
Get Travel Request Retrieves one travel request with its trips and estimated costs, plus the link to what the trip actually cost.
List Travel Reports Lists travel reports, the settlement side, after the trip.
Get Travel Report Retrieves one travel report with its trips and the request it came from.

Journey Log

Add Journey Records a journey in the mileage log. Odometer readings and distance must be whole kilometers.
Update Journey Updates a journey. The vendor's contract repeats every required field, so read the record first and pass its current values through.
Get Journey Retrieves one journey with its refueling and break entries.
Delete Journey Permanently deletes a journey from the mileage log.
Get Journey Log Period Returns a vehicle's journeys for a period and the period before it. The previous period is what shows whether the odometer readings join up.

Vehicles

List Vehicles Lists the vehicles the mileage log can be kept against.
Add Vehicle Adds a vehicle. Owner ID is required for a private or individually assigned car and must be empty for a pool car, since the vendor reads its presence rather than a flag.
Update Vehicle Updates a vehicle. Every required field must be resent, not just the ones changing.
Delete Vehicle Deletes a vehicle. Setting its state to inactive is the softer option when it already has journeys against it.

Accounting Dimensions

List Cost Centres Lists the primary dimension expenses are coded against.
Add Cost Centre Creates one.
Update Cost Centre Updates one. Code, name, and state are all required even when unchanged.
Delete Cost Centre Deletes one. Setting its state to deleted instead keeps historical coding readable.
List Projects Lists the second dimension expenses are coded against.
Add Project Creates a project, optionally with a manager and a budget.
Update Project Updates a project. Sending an explicit null for manager or budget removes it, so omit the field to leave it alone.
Delete Project Deletes a project.
List Accounting Categories Lists the categories expense items are classified under.
Add Accounting Category Creates one.
Update Accounting Category Updates one.
Delete Accounting Category Deletes one.
List Account Assignments Lists the debit and credit pairs that turn an expense into a bookkeeping entry.
Add Account Assignment Creates one. Its type is fixed at creation and cannot be changed afterward.
Update Account Assignment Updates one. The vendor publishes no type on this route.
Delete Account Assignment Deletes one.
List VAT Breakdowns Lists the VAT codes expense items are split by.
Add VAT Breakdown Creates one. Code and name are capped at fifty characters.
Update VAT Breakdown Updates one.
Delete VAT Breakdown Deletes one.

Frequently Asked Questions

What can FlowRunner do with Fidoo?

FlowRunner agents can run Get User Info, Get Accounts, and List Users in Fidoo, plus 59 more actions.

Does connecting Fidoo to FlowRunner require OAuth?

No. Fidoo connects to FlowRunner with an API key, no OAuth flow required.

Can Fidoo trigger a FlowRunner workflow automatically?

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

Start building with Fidoo

Free plan, no card required. Connect in minutes.

Start Building Free Talk to us