--- title: "Qonto Integration" description: "Automate finance work on your Qonto business accounts. Agents read organizations and account balances, list and inspect transactions for reconciliation, pull invoice and receipt attachments, and look up beneficiaries, labels, and team members." url: https://flowrunner.ai/integrations/qonto date_modified: 2026-08-01T02:40:32-07:00 --- # Qonto [Payments](https://flowrunner.ai/integrations/category/finance-accounting) Automate finance work on your Qonto business accounts. Agents read organizations and account balances, list and inspect transactions for reconciliation, pull invoice and receipt attachments, and look up beneficiaries, labels, and team members. [Verified](https://flowrunner.ai/integrations/verified "What does verified mean?") · 7 actions · API key · available [Qonto website](https://qonto.com/) · [Platform Documentation](https://api-doc.qonto.com/) · Capability data verified 2026-07-28 1. The daily close window opens at 7 a.m. 2. Get Organization pulls every bank account with its IBAN, status, and current balance 3. List Transactions pages through yesterday's settled activity, most recent first 4. Get Transaction enriches notable entries with VAT detail, label IDs, and attachment references 5. Each debit's counterparty is compared against List Beneficiaries, and balances against the operating floor 6. The finance lead reviews the exceptions, the debit to an IBAN no trusted beneficiary carries, the balance dipping toward the floor, and decides what happens next 7. Get Attachment pulls the signed download URL for each receipt so ledger entries carry their documents 8. The reconciled ledger lands in the accounting sheet and the exceptions post to the finance channel ## What This Integration Enables A bank account is the one system in the company that never lies, which is exactly why finance teams spend so many hours copying out of it. Qonto exposes the business account as structured data: accounts with live balances, transactions with VAT detail and labels, attachments carrying the actual invoices, and the register of trusted beneficiaries. FlowRunner agents read all of it on a schedule, so reconciliation, monitoring, and document filing become standing processes, and the judgment calls surface to a person the day they arise instead of at month end. - Sync settled transactions into spreadsheets and ledgers for daily reconciliation - Watch balances and new debits against thresholds and known payees, with same-day alerts - Pull invoice and receipt attachments off transactions into document workflows - Categorize activity with the organization's own labels and attribute it to team members - Check counterparties against the trusted beneficiary register before anything else trusts them ### Without FlowRunner **Reconciliation is a month-end dig**: Transactions get exported at close and matched by hand, weeks after the money moved **Balance surprises**: You find out the account dipped when a payment fails, not when the trend started **Receipts chased by email**: The invoice is attached in the bank, the ledger entry lives elsewhere, and a person carries files between them ### With FlowRunner **A ledger that closes daily**: Settled transactions land in the books categorized by label, VAT detail attached, the morning after **Thresholds watched on schedule**: Balances, large debits, and named payees are checked every day and flagged the day they appear **Documents filed with the entry**: Attachment URLs are pulled off transactions and stored with the matching ledger record automatically ## Use Case Scenarios ### The reconciliation ledger that fills itself Each morning the agent calls Get Organization to enumerate accounts, then List Transactions for each, walking the pagination until yesterday is fully captured. Every settled transaction becomes a row in [Google Sheets](https://flowrunner.ai/integrations/google-sheets) with amount, side, operation type, settlement date, and label. Get Transaction adds VAT detail where the accountant needs it. Month-end close starts from a ledger that already agrees with the bank, and the accountant's time goes to the ten entries that need thought, not the four hundred that need typing. ### The debit that gets noticed in hours, not weeks The daily sweep flags anything above the alert threshold and any payee appearing for the first time. When List Transactions surfaces a large debit, the agent attaches the label, the settlement date, and, via List Memberships, which team member's card or transfer it traces to, then posts the package to the finance channel in [Slack](https://flowrunner.ai/integrations/slack). Most alerts take five seconds to dismiss. The one that matters is worth every false positive. ### From bank attachment to accounts payable record Suppliers' invoices arrive attached to the transactions that paid them. The agent reads each new transaction's attachment references, calls Get Attachment for the signed download URL, fetches the document while the link is fresh, and creates the matching bill in [Xero](https://flowrunner.ai/integrations/xero). The AP trail becomes complete without anyone forwarding a PDF, and audits stop involving a search through three inboxes. ## Human-in-Loop Highlight The register behind List Beneficiaries is a list of counterparties your organization has decided to trust with transfers, and the most expensive fraud in B2B finance works by getting one untrusted IBAN treated as if it were on that list. So when the daily sweep finds a debit whose counterparty matches no trusted beneficiary, or a known supplier suddenly paid on a new IBAN, the agent does not label it and move on. It assembles the case, transaction detail from Get Transaction, the attachment via Get Attachment, the nearest beneficiary match with its trust status, and puts it in front of the finance lead before any further payment to that counterparty is prepared. Money that has settled does not come back, so the [human-in-the-loop](https://flowrunner.ai/concepts/human-in-the-loop) review happens while it can still change the outcome. 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 7 actions ### Accounts 1 - **Get Organization** Retrieves the authenticated organization with all of its bank accounts, each carrying slug, IBAN, BIC, currency, status, and current balance. The starting point that scopes every other query. ### Transactions 3 - **List Transactions** Lists a bank account's transactions most recent first, with status filtering and full pagination metadata for walking large result sets. The backbone of reconciliation and monitoring flows. - **Get Transaction** Retrieves one transaction with amount, side, operation type, settlement and emission timestamps, VAT details, and linked attachment and label IDs. The enrichment step behind ledger entries and alert context. - **Get Attachment** Retrieves an attachment's metadata and a short-lived signed download URL for the invoice or receipt. Fetched just before use, because the URL expires. ### Reference Data 3 - **List Beneficiaries** Lists the trusted payment beneficiaries with name, IBAN, BIC, and trust status. The register that counterparty checks run against. - **List Labels** Lists the organization's labels, including nested parent relationships. The categorization vocabulary for transaction workflows. - **List Memberships** Lists team members with name, email, and role. Used to attribute transactions to the person behind them and to build assignee options for review steps. ## Frequently Asked Questions ### What can FlowRunner do with Qonto? FlowRunner agents can run Get Organization, List Transactions, and Get Transaction in Qonto, plus 4 more actions. ### Does connecting Qonto to FlowRunner require OAuth? No. Qonto connects to FlowRunner with an API key, no OAuth flow required. ### Can Qonto trigger a FlowRunner workflow automatically? Qonto doesn't currently expose triggers in FlowRunner. It connects as an action step inside workflows started by another trigger. **Work at Qonto?** This integration exposes Qonto to AI agents on every FlowRunner plan, including through MCP, at no cost to you. [See what FlowRunner offers integration partners](https://flowrunner.ai/integrations/partners), including how to keep this page current. --- Markdown version of https://flowrunner.ai/integrations/qonto. Site index: https://flowrunner.ai/llms.txt