Tidely

Tidely is a German liquidity-planning and cash-flow platform with a Public API and a Partner API. Agents read bank accounts, balances, and transactions, manage invoices, plans, and categories, read scenarios, pull the cash-flow forecast, and onboard customer accounts.

Verified 44 actions Custom auth available

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

The planning team publishes a revised budget in the workbook everyone works from

The agent reads the planned figures and maps each row to a Tidely category by path or id

Signs are checked, since a negative amount is an expense and a positive one is income

The agent compares every target category and scenario against the plans already loaded there

A staged summary is assembled showing what exists today, what would be added, and what would be replaced

The summary posts to the finance owner with the replace flag called out per category

The finance owner confirms each category before Create Plans (Bulk) writes anything

What This Integration Enables

Tidely is a forecast, not a ledger. Get Cashflow returns opening and closing balances, actual and prognosed and planned side by side, per category, with plan deviation, and it runs into the future. Every other operation in this connector exists to feed that one. Understanding that changes how you build on it: a write here is a write into a prediction the finance team steers by, so a bad row does not produce an error, it produces a wrong number that looks exactly like a right one.

FlowRunner agents load bank accounts and their reference balances, push transactions in bulk with deduplication in front of them, keep invoices current so receivables and payables land in the correct future period, and set planned figures against scenarios. The same connector covers Tidely's Partner API for white label integrators, so a workflow can provision a customer account, create its users, and mint a single use token that drops that customer straight into the embedded frontend. Because Tidely publishes no webhooks, flows poll Get Cashflow or the transaction list on a schedule rather than waiting for an event.

Without FlowRunner

The forecast is a workbook Cash position is accurate on the day somebody rebuilds it and drifts every day after

Budget imports that double A load runs twice, the planned figures add instead of replacing, and the forecast quietly inflates

Statements imported twice A re-imported bank file skews every balance from that day forward with nothing reporting an error

With FlowRunner

The forecast is the system of record Balances, transactions, invoices, and plans feed one forward looking cash view

Replace or add is a stated decision Every plan import names which categories it would replace and which it would add to before it runs

Deduplication before loading A batch is filtered down to the rows that are genuinely new before any of it is written

Use Case Scenarios

Bank activity into the forecast without double counting

Transactions arrive from a bank feed or from the ledger in Xero, each carrying the source system's own key. The agent sends up to a thousand of those keys to Check Transactions Exist, keeps only the ones that answered false, and loads the remainder with Create Bank Account Transactions (Bulk). It then reads the response body rather than the status code, because the bulk route reports created, failed with per row errors, and skipped counts, and a partly rejected batch still returns success. Rejected rows post to Slack with the reason attached, so a person fixes ten rows instead of re-running a thousand.
Receivables that reflect what is still owed

Invoices from Stripe or Lexoffice sync into the forecast with Create Invoices (Bulk). The agent writes the open amount rather than the total gross, because a partially paid invoice should contribute only its remainder to future liquidity. When a payment lands, Update Invoice reduces the open amount and the forecast moves with it. Where invoices originate in an ERP integration Tidely treats them as read only, so the flow corrects the source system instead of trying to patch the copy, and posts a note saying so rather than failing quietly.
Onboarding a client into a white label liquidity view

An advisory firm running Tidely under its own brand takes on a new client. One flow calls Create Customer Account to provision the account, its main company, and its first admin, then Create User for each additional person and Create Bank Account for each account the client banks with. When the client is ready to look at their own numbers, Create SSO Init Token mints a single use token that logs them straight into the embedded frontend, with no separate password to issue. A scheduled job then calls Get Cashflow per account and writes a portfolio level view into Google Sheets for the firm's own review.

Human-in-Loop Highlight

Loading a budget into Tidely has no surgical undo. Create Plans (Bulk) defaults to adding rather than replacing, so a re-run stacks a second copy of the budget on top of the first. The only correction available is Delete Plans, which removes every plan for a category and scenario combination, not just the ones this run created, because Tidely publishes no delete-a-single-plan route at all. That asymmetry is why the agent never imports a budget on its own authority. It stages the run, then posts: "Import touches nine categories in the Base scenario. Six are empty. Three already carry plans loaded in March. Replace those three, or add to them?" The finance owner answers per category, and only then does the write happen. The agent does the mapping, the sign checking, the period alignment, and the diff. The choice that cannot be reversed one row at a time belongs to a person.

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

44 actions

Account

Verify Authentication Confirms the credentials work and reports whose they are. The cheapest connection check, and the fastest way to tell a wrong header from a wrong key.
List Companies Lists the companies in the account with their currency, country, and industry. Used to resolve which company a workflow should write against.
Get Company Retrieves one company by id.

Cashflow

Get Cashflow Returns the forecast itself, per period bucket: opening and closing balances as actual, prognosed, total, and plan, with sales and purchase totals, per category amounts, plan deviation, income and expense detail, overdraft and liquidity figures, and any non-financial indicators. The reason most flows connect to Tidely at all. The from date must be the first day of a period and the to date the last, so a monthly view runs first to last of the month.

Scenarios

List Scenarios Lists the planning scenarios the account works with. Used to resolve which scenario a plan or a forecast read belongs to.
Get Scenario Retrieves one scenario by id.

Bank Accounts

List Bank Accounts Lists the accounts feeding the forecast along with their reference balances.
Get Bank Account Retrieves one bank account by id.
Create Bank Account Adds a bank account. The reference balance and its date anchor every past and future balance on that account, so the value set here propagates through the whole forecast.
Update Bank Account Updates an account, including its reference balance. Changing the anchor shifts the entire series computed from it.
Delete Bank Account Deletes an account and everything derived from it, including its transactions and its contribution to the forecast.
Get Bank Account Balances Returns the daily balance series for one account, the actual past from which the forecast projects forward.

Transactions

List Bank Account Transactions Lists one account's transactions. There is no cross account listing, so a full picture means one call per account.
Get Bank Account Transaction Retrieves one transaction by id.
Create Bank Account Transaction Adds a single transaction to an account. Used for one off corrections rather than for loading a statement.
Create Bank Account Transactions (Bulk) Loads up to a thousand transactions onto one account in a single call, and reports created, failed, and skipped counts in the body. A flow that reads only the status code cannot tell a full load from a partial one.
Check Transactions Exist Asks which of up to a thousand external ids are already on an account. The deduplication step that belongs in front of every bulk load, because a double import produces wrong balances rather than an error.
Update Bank Account Transaction Updates a transaction, most often to code it to a category, which is what moves it onto the right forecast line.
Delete Bank Account Transaction Deletes a transaction and its effect on every balance after it.

Invoices

List Invoices Lists invoices. The sales or purchases filter is mandatory on every invoice call, so a complete picture is two calls.
Get Invoice Retrieves one invoice, again scoped to sales or purchases.
Create Invoice Adds an invoice to the forecast. The open amount rather than the total gross is what an unpaid invoice should contribute to future liquidity.
Create Invoices (Bulk) Loads up to a thousand invoices in one call and reports the created and failed counts in the body.
Update Invoice Updates an invoice, typically to reduce the open amount as payments land. Invoices that originate from an ERP integration are read only and refuse this.
Delete Invoice Deletes an invoice. Also refused on invoices owned by an ERP integration.

Plans

Create Plan Adds one planned figure to a category and scenario. The sign carries the meaning: a negative amount is an expense and a positive one is income.
Create Plans (Bulk) Loads many planned figures in one request, which is how a whole budget arrives. Replacing current values is off by default, so an unguarded re-run adds a second copy of the budget rather than overwriting the first.
Delete Plans Deletes every plan for one category and scenario combination. Tidely publishes no route for deleting a single plan, so removing one figure means clearing the category and reloading it.

Partner

List Customer Accounts Lists the customer accounts under your partner grant.
Get Customer Account Retrieves one customer account.
Create Customer Account Provisions a new customer in one call: the account, its main company, and its first admin user.
Update Customer Account Renames a customer account's main company.
Delete Customer Account Deletes a customer account and everything inside it. The most destructive operation in the connector, and one no scheduled job should hold.
List Users Lists the users in the customer account named by the connection.
Get User Retrieves one user.
Create User Adds a user to a company inside the customer account.
Update User Updates a user's first and last name. Roles and email addresses are not changeable through the API.
Delete User Removes a user from the customer account.
Create SSO Init Token Mints a single use token that logs one user straight into the embedded Tidely frontend, so a client reaches their own liquidity view without a separate credential being issued.

Frequently Asked Questions

What can FlowRunner do with Tidely?

FlowRunner agents can run Verify Authentication, List Companies, and Get Company in Tidely, plus 41 more actions.

Does connecting Tidely to FlowRunner require OAuth?

Tidely uses a custom authentication method to connect to FlowRunner.

Can Tidely trigger a FlowRunner workflow automatically?

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

Start building with Tidely

Free plan, no card required. Connect in minutes.

Start Building Free Talk to us