Qonto Zapier integrationAutomate Qonto with Zapier.
The Qonto Zapier integration gives you 9 triggers, 3 actions and 0 searches. Zapier can react to a balance change, a new transaction, a new transfer or an edit on a transaction, then move money between accounts, pay a beneficiary or attach a file.
Verified Trustpilot reviews · AI, automation & growth agency
What the Qonto Zapier integration does for your finance work
Qonto is a bank designed to make day-to-day finance simpler for companies. Connected to Zapier, it becomes both a source and a destination: a movement on an account starts a Zap, and Zapier can order a transfer or add a receipt to a transaction in return, without anyone opening the banking app.
Three outcomes cover most of what finance teams set up. An account that tops itself up. Bank Account Balance Change watches a sub-account, and Create Internal Transfer moves money from the main account when it runs low. A payment that leaves on its own. Create External Transfer sends money to a beneficiary IBAN, with the amount and the reference mapped from the step before. Bookkeeping that keeps up. The triggers on attachments, labels and VAT tell you when a transaction has been tidied, and Add Attachment puts a file on a transaction from another tool.
Now what Zapier does not do with Qonto. Every one of the 9 triggers works by polling: Zapier checks your account on a timer, so nothing reacts the second money moves. There is no search, so a Zap cannot look up a past transaction or a beneficiary. And actions stop at transfers and attachments: no card, no invoice, no label written from Zapier.
If you want to compare before committing, the Qonto Make integration covers the same bank on Make, and our Make vs Zapier comparison sets out the criteria.
Zapier words, in plain English
Eight terms come back on every line of this page. Here they are, in everyday words.
- Zap
- The automation you build on Zapier: one trigger, then one or more actions that run every time the trigger event happens.
- Trigger
- The event that starts the Zap. With Qonto: a balance that moves, a new transaction, a new transfer, or an edited transaction.
- Action
- What the Zap does once started. Here, ordering a transfer or attaching a file to a Qonto transaction for you.
- Task
- The unit Zapier bills: one action that completes successfully. Your plan gives you a monthly count of these.
- Polling trigger
- A trigger Zapier checks on a timer, asking Qonto for new items and keeping only what it has not seen before.
- Filter
- A step that lets the Zap continue only when what arrived meets the condition you set, and stops it otherwise.
- Connection
- Your Qonto account linked to Zapier once, then reused by every step that touches Qonto in any of your Zaps.
- Multi-step Zap
- Any Zap beyond one trigger and one action. A filter or a second action makes one, and it then needs a paid plan.
What a Qonto Zap really costs
Watching your accounts is free. What you pay for is each action that goes through.
- Free plan100 tasks a month
- Free plan Zap sizeTwo steps: one trigger, one action
- Premium appNo, works on the free plan
Each transfer ordered or file attached in a successful run counts as one task. A failed action is not billed, and neither the trigger nor Zapier's checks cost anything, however often they run. Qonto is not a premium app, so the free plan accepts it: 100 tasks a month and two-step Zaps, which is enough for one trigger plus one transfer. Add a filter, which you will want before moving money, and the Zap becomes multi-step and needs a paid plan.
Connect Qonto to Zapier in three steps
- 01
Open the Apps page
In your Zapier account, go to Apps and click + Add connection. Type Qonto in the search box of the dialog that opens, then pick it from the list of results.
- 02
Sign in to Qonto
Click Add connection. Qonto opens in a new tab: sign in with the account that can see the bank accounts your Zaps will watch or debit. An existing Qonto account is required.
- 03
Grant access
Accept the access request so Zapier can read your accounts and act on them. The connection then appears on the Apps page, and every Qonto step of every Zap reuses it.
Your first Zap: keep an expense account topped up
GoalWhen the balance of your expense sub-account changes and falls under your floor, Qonto moves a fixed amount from the main account into it.
- 01
Set the trigger
In the editor, pick Qonto and
Bank Account Balance Change. Enter the IBAN of the expense sub-account, the one you want to keep funded. - 02
Test it
Run the test. Zapier brings back the three most recent items of the connected account, so you map from real data, not from an example.
- 03
Add the filter
Add a Filter step on the balance, with a number rule and your floor as the value. A text rule would never pass on a number, so pick the number one.
- 04
Add the transfer
Pick
Create Internal Transfer. Debit the main account IBAN, credit the sub-account IBAN, then type the amount, the currency and a reference. - 05
Test, then publish
Test each step with a small amount and check both balances in your Qonto app. Then click Publish to switch the Zap on for good.
The 9 Qonto triggers
9 events start a Zap when something happens in Qonto. Zapier checks for them at the interval your plan allows.
Bank Account Balance Change
Polling triggerIn Zapier“Triggers when the balance of a bank account changes.”
Starts your Zap when the balance of one account moves, whatever caused it. You point it at the account through its IBAN, so one trigger watches one account.
New Bank Account
Polling triggerIn Zapier“Triggers when a new bank account is detected.”
Reacts when Qonto detects a bank account that did not exist before in your organization. It is the only Qonto trigger that needs no IBAN, since the account is brand new.
New Transaction (Legacy)
Polling triggerIn Zapier“Triggers when a new transaction is detected.”
The older version of the new-transaction trigger, still listed by Zapier and still working on a given IBAN.
New Transaction
Polling triggerIn Zapier“Triggers when a new transaction is detected.”
Fires on every new transaction that shows up on the account whose IBAN you set. Zapier puts it forward on its Qonto page, and it is the current version of this trigger.
Updated Transaction
Polling triggerIn Zapier“Triggers when a transaction is updated.”
Picks up a transaction that already existed and has just been changed, on the IBAN you choose. It is the broad one: any update counts, not one kind in particular.
Transaction Updated Attachments
Polling triggerIn Zapier“Triggers when the attachments of a transaction gets updated.”
Goes off when the attachments of a transaction change on the account you set, typically when someone adds a receipt or an invoice to it.
Transaction Updated Labels
Polling triggerIn Zapier“Triggers when the labels of a transaction gets updated.”
Watches the labels of transactions on one IBAN and starts the Zap when they change, which makes it useful when labels drive your sorting.
Transaction Updated VAT
Polling triggerIn Zapier“Triggers when the VAT of a transaction gets updated.”
Reacts when the VAT information of a transaction is updated on the account you monitor, which makes it the trigger to follow tax corrections.
New Transfer
Polling triggerIn Zapier“Triggers when a new transfer is detected.”
Triggers when Qonto detects a new transfer on the IBAN you set. It focuses on transfers rather than on every kind of transaction.
The 3 Qonto actions
Qonto gives you 3 actions. For each one: what it does for you, when to reach for it, and what to watch out for.
Create External Transfer
ActionIn Zapier“Transfers to a given beneficiary Iban”
Sends money from one of your accounts to a beneficiary IBAN outside your organization, with the amount, currency and reference you map.
Create Internal Transfer
ActionIn Zapier“Transfers between accounts of the same organization”
Moves money between two accounts of the same Qonto organization: you give the IBAN to debit, the IBAN to credit, the amount, the currency and a reference.
Add Attachment
ActionIn Zapier“Adds a new attachment to a transaction”
Puts a file on an existing transaction, found by its Transaction ID, with the file itself, its name and its extension.
When a Qonto Zap breaks
Zapier attaches no help article to Qonto and no limit specific to the app is documented. What goes wrong comes from Zapier's general rules and from the money-moving actions.
With a bank, a broken Zap is rarely silent: it either misses a movement or moves money twice. Six cases to read before you publish.
A transfer that restarts its own Zap
An internal transfer changes the balance of both accounts. If the trigger watches the same account, the Zap sets itself off again and burns tasks.The same Idempotency Key twice
Create External Transfer needs a key unique to each transfer. A fixed value mapped there breaks that rule on the second run.Past movements are not picked up
A Zap only reacts to what happens after it is switched on. Last month's transactions stay out; handling that backlog is a separate job.A wrong IBAN in the trigger
Nearly every trigger watches one IBAN. A typo points the Zap at the wrong account, and the signed-in user needs access to the account you meant.A big batch held back
After an import or a burst of activity, a trigger that returns a huge batch at once can be held back by Zapier's flood protection.Legacy trigger in a new Zap
New Transaction (Legacy) still appears in the list. Building on it today means relying on the older version when New Transaction exists.
Need help automating Qonto with Zapier?
A person reads every message.



