Resources · Make integration

Qonto Make integrationAutomate Qonto with Make.

Can Make keep Qonto in step with the rest of your tools? The Qonto Make integration gives you 25 modules: 2 triggers that watch transactions, 16 actions and 7 searches. This guide helps finance and ops teams connect Qonto and build a first scenario.

Try the Qonto integration on MakeSee the 25 modules

Verified Trustpilot reviews · AI, automation & growth agency

What you can automate

What can the Qonto Make integration do for you?

The Qonto Make integration links your Qonto business account to Make, a visual tool where you build a scenario (the automation itself) out of modules, each one a single brick: a trigger, an action or a search. Once connected, Make can spot new or edited transactions, send transfers, file receipts and create client invoices in Qonto on your behalf.

Receipts that find their transaction. Watch New Transactions picks up each new payment and Add an Attachment pins the matching receipt to it, so the pile of missing proofs your accountant chases keeps shrinking.

Invoices born from a closed deal. When a sale is marked won in your CRM, Create a Client registers the customer in Qonto and Create a Client Invoice issues the bill right after. Sales reps never open the banking app.

Onboarding without the admin chase. A confirmed hire in your HR tool can run Create a Membership, which invites that person to your Qonto organization, while Create a Team keeps departments organized.

Two limits to know first. Qonto only opens its Make app to paid Qonto accounts, and both triggers are scheduled: Make checks Qonto on the scenario's schedule instead of being called when money moves. For anything the 25 modules leave out, Make an API Call reaches the rest of the Qonto API with the same connection.

Weighing another platform? The n8n vs Make comparison sets out the differences, Make pricing explains how operations are counted, and the Make training walks newcomers through the editor.

Connect

How do you connect Qonto to Make?

  1. 01

    Add a Qonto module

    Open a scenario in Make, click the + and type Qonto. Pick any Qonto module, Watch New Transactions for instance, then click Create a connection. A connection is your Qonto account linked to Make once and reused by every Qonto module.

  2. 02

    Name it and save

    Make shows a Connection name field. Filling it is optional, yet a clear name helps you recognize the right account later when you pick it from a module. Then click Save.

  3. 03

    Confirm access in Qonto

    If Qonto prompts you, sign in to your Qonto account and confirm that Make may access it. Back in the editor, the connection sits in the module, and Make can now list the Qonto items it is allowed to read.

First scenario

Your first scenario with Qonto

GoalWhen a deal is won in another app, Make creates the client in Qonto and then issues the client invoice.

  1. 01

    Create the scenario

    From the Scenarios page, create a new scenario and click the +. The first module comes from the app where deals are won, your CRM for example, shown here as the neutral bubble.

  2. 02

    Add Create a Client

    Click the + to the right of that first module, search Qonto and choose Create a Client. Select your connection, then map the customer details coming from the CRM module into the client fields.

  3. 03

    Chain Create a Client Invoice

    Add one more module with the +: Create a Client Invoice. Map the client produced by the previous module and fill the invoice from the deal data. No need to know the fields by heart: Make lists what it can read in Qonto.

  4. 04

    Test with Run once

    Click Run once with a test deal. Each module shows the bundles it received, a bundle being one item passed along, here one client. Open Qonto and check the invoice before going further.

  5. 05

    Schedule and switch on

    Open the clock on the first module to set the schedule. A new scenario runs every 15 minutes by default, the shortest interval on the Free plan. Then switch the scenario on.

Triggers

Qonto triggers in Make

2 modules start a scenario when something happens in Qonto. A scheduled trigger is checked by Make on the scenario's schedule; an instant one is called by Qonto as soon as it happens.

Qonto1Watch New Transactions

Watch New Transactions

Scheduled trigger

In Make“Watches new transactions.”

Watch New Transactions notices each transaction that lands in your Qonto account and starts the scenario with it, so every payment in or out can set off the next step without anyone copying it by hand. Each transaction arrives as its own bundle.

How it fires
scheduled. Make checks Qonto on the scenario's schedule, every 15 minutes by default and down to 1 minute on paid plans.
When to use it
you want a receipt request, a team alert or a bookkeeping row each time a card payment or an incoming transfer shows up.
Watch out
nothing happens between two checks, so a payment waits for the next scheduled run before your scenario sees it.
Qonto2Watch Updated Transactions

Watch Updated Transactions

Scheduled trigger

In Make“Watches updates of transactions.”

Watch Updated Transactions reacts when a transaction already in Qonto changes, rather than when a new one appears. That makes it the trigger for follow-up work: an edit made in Qonto after the payment feeds the scenario again.

How it fires
scheduled. Make checks Qonto on the scenario's schedule and runs the scenario for the updates it finds.
When to use it
your team completes transactions in Qonto after the fact, and those edits should reach a spreadsheet or your bookkeeping tool.
Watch out
it only looks at changes, so a brand-new transaction that nobody edits never reaches this scenario; pair it with Watch New Transactions when you need both.
Modules

What the Qonto modules do

Qonto gives you 23 modules in 12 groups. For each one: what it does for you, when to reach for it, and what to watch out for.

External transfers

3 modules
Qonto1

Get an External Transfer

Action

In Make“Gets a single external transfer, given it's ID.”

Get an External Transfer pulls up one transfer you sent to an outside account, using its ID, and hands its details to the next module. Handy for confirming what went out before you notify anyone.

When to use it
an earlier step already gave you the transfer ID, from Create an External Transfer for example, and you need the full record to log or share.
Watch out
without an ID it has nothing to fetch; List External Transfers suits a broader lookup.
Qonto2

List External Transfers

Search

In Make“Retrieves a list of external transfers.”

List External Transfers returns the transfers your organization sent to outside beneficiaries, one bundle per transfer, so you can review or export them together.

When to use it
building a payment log in a spreadsheet, or checking which supplier payments already left before a reminder goes out.
Watch out
a search returns zero, one or many bundles, and every module after it runs once per bundle, which adds operations, the unit Make counts on your plan.
Qonto3

Create an External Transfer

Action

In Make“Transfers to a given beneficiary IBAN.”

Create an External Transfer sends money from Qonto to a beneficiary IBAN, straight from your scenario. An approved payment request becomes a real transfer without anyone reopening the banking app.

When to use it
a supplier invoice gets approved in your workflow tool and the payment should follow on its own.
Watch out
Run once executes the scenario for real, so a test sends an actual transfer; try it with a small amount and a beneficiary you control.

Attachments

2 modules
Qonto4

Add an Attachment

Action

In Make“Adds a new attachment to a transaction.”

Add an Attachment pins a file, typically a receipt, to a transaction in Qonto. Your transactions reach the books with their proof already in place.

When to use it
right after Watch New Transactions, when the receipt comes from an inbox or a cloud folder read by another module.
Watch out
the file has to come from a previous module, and on the Free plan Make handles files of 5 MB at most, so large scans may not go through.
Qonto5

Get an Attachment

Action

In Make“Gets an attachment by its ID.”

Get an Attachment retrieves one file already stored in Qonto, by its ID, so you can copy it elsewhere or confirm it is there.

When to use it
archiving receipts in your accounting drive, or sending them to an accountant who does not work in Qonto.
Watch out
it needs the attachment ID, mapped from an earlier module; on its own it cannot browse the files of a transaction.

Labels

2 modules
Qonto6

List Labels

Search

In Make“Retrieves a list of all labels within the organization.”

List Labels returns every label defined in your Qonto organization, one bundle each. Your scenario then works with the exact label names your team already uses instead of hard-coded guesses.

When to use it
syncing Qonto labels to a spreadsheet or a budgeting tool so categories match on both sides.
Watch out
each label becomes a bundle, so a long label list multiplies the operations of the modules placed after it.
Qonto7

Get a Label

Action

In Make“Retrieves a single label within the organization.”

Get a Label fetches a single label from your organization when you already know which one you want. Think of it as the precise counterpart to List Labels.

When to use it
a previous step handed you a label ID and a report needs the readable name instead.
Watch out
Make classes it as an action, not a search, so it brings back that one label and never a filtered list of several.

Memberships

3 modules
Qonto8

List Memberships

Search

In Make“Watches all memberships within the organization.”

List Memberships shows everyone who belongs to your Qonto organization, each member as a separate bundle, which is the quickest way to see who holds access.

When to use it
an access review before an audit, or copying the member list into your HR tool.
Watch out
the Make documentation describes it as watching memberships, yet it is a search: it runs when the scenario reaches it, never on its own.
Qonto9

Get Membership

Action

In Make“Retrieves the details of the authenticated Membership.”

Get Membership returns the details of the membership behind your connection, meaning the Qonto user that Make acts as. Good to know whose rights a scenario runs with.

When to use it
checking which account a shared scenario relies on before it sends transfers or creates invoices.
Watch out
it does not look up other people in the organization; for them, List Memberships is the right module.
Qonto10

Create a Membership

Action

In Make“Creates a new membership and invite it to the authenticated organization.”

Create a Membership adds a new person to your Qonto organization and sends them an invitation, so onboarding a colleague no longer waits on whoever holds the admin login.

When to use it
a hire is confirmed in your HR tool or through a form, and finance access should follow.
Watch out
this module opens your company banking tool to someone; put an approval step before it rather than letting any form entry reach it.

Organizations

1 module
Qonto11

Get Current Organization

Action

In Make“Reads the current organization.”

Get Current Organization reads the Qonto organization tied to your connection and returns its details in a single bundle. A simple way to tag data with the right company.

When to use it
a group runs several Qonto organizations, each with its own connection, and a shared report must show which one every line comes from.
Watch out
it always reads the organization of the current connection; switch connection to read another one.

Transactions

1 module
Qonto12

Get a Transaction

Action

In Make“Retrieves a single transaction within a particular bank account, given it's ID.”

Get a Transaction fetches one transaction from a given Qonto bank account by its ID, with its full details. It fills the gaps when an earlier step only passed an ID along.

When to use it
a spreadsheet row stores a transaction ID and you want the complete record before attaching a file or updating that row.
Watch out
it needs both the account and the ID; right after a watch trigger, the transaction usually arrives complete already.

Internal Transfers

1 module
Qonto13

Create an Internal Transfer

Action

In Make“Transfers between accounts of the same organization.”

Create an Internal Transfer moves money between two accounts of the same Qonto organization, for instance topping up an account set aside for taxes.

When to use it
client payments land in the main account and a share should move to a reserve account as soon as Watch New Transactions spots them.
Watch out
the money stays inside the organization, but Run once still performs the transfer, so test it with a small amount.

Client Invoices

2 modules
Qonto14

List Client Invoices

Search

In Make“Retrieve all client invoices within a particular Organization. The response contains the list of the client invoices and all the related data and attachments.”

List Client Invoices returns the invoices your organization issued, together with their related data and attachments, one bundle per invoice.

When to use it
feeding a cash-collection dashboard, or dropping invoice copies into the folder your accountant shares with you.
Watch out
every invoice is a bundle and each later module runs for each one, so a long billing history quickly adds operations; keep the modules after it few.
Qonto15

Create a Client Invoice

Action

In Make“Create a single client invoice for a particular organization. See further details below.”

Create a Client Invoice issues an invoice in Qonto for one of your clients, so billing follows a sale without anyone retyping the order.

When to use it
a deal is marked won in the CRM or an order is paid on your store, and the invoice belongs in Qonto.
Watch out
the invoice is addressed to a Qonto client, so run List Clients or Create a Client first and map that client in.

Clients

3 modules
Qonto16

Get a Client

Action

In Make“Get information about client(s) that constitute(s) the addressee of client invoices for a particular organization based on a search on attributes.”

Get a Client finds one of the clients you invoice by searching on the attributes you provide, then passes the details of that client to the scenario.

When to use it
before invoicing, to check that a customer from your CRM already exists in Qonto and reuse that record.
Watch out
Make lists it as an action while List Clients is a search; prefer List Clients when several clients could match.
Qonto17

List Clients

Search

In Make“Get information about client(s) that constitute(s) the addressee of client invoices for a particular organization based on a search on attributes.”

List Clients searches your Qonto clients on the attributes you set and returns every match as its own bundle. It lets a scenario check the client list before adding someone new.

When to use it
avoiding duplicates: search first, and only create a client when the search comes back empty.
Watch out
an empty result is still a valid run; decide what the scenario does when zero bundles come back.
Qonto18

Create a Client

Action

In Make“Create a client that constitutes the addressee of client invoices for a particular organization. See further details below.”

Create a Client registers a new customer in Qonto as someone you can invoice. Your client list then fills up from the sales tools you already use, not from manual typing.

When to use it
a new signup, a signed quote or a first order should open a client record ready for billing.
Watch out
every run creates a record. If a customer can come back, search with List Clients first.

Credit Notes

2 modules
Qonto19

List Credit Notes

Search

In Make“Gets a list of credit notes for an organization.”

List Credit Notes returns the credit notes of your organization, one bundle each, so refunds and corrections become visible outside Qonto.

When to use it
matching credit notes against your sales records, or passing them to your accountant alongside the invoices.
Watch out
it covers credit notes only; invoices come from List Client Invoices, so a full sales export needs both modules.
Qonto20

Get a Credit Note

Action

In Make“Gets details of credit note for an organization.”

Get a Credit Note opens one specific credit note and returns its details, which is enough when you already know which refund you are dealing with.

When to use it
a customer questions a refund and your support tool needs the credit note details to answer.
Watch out
it reads a single credit note; to go through a batch, List Credit Notes does the job in one step.

Teams

2 modules
Qonto21

List Teams

Search

In Make“Lists teams in an organization.”

List Teams returns the teams set up in your Qonto organization, each as a bundle, giving your scenario the current team structure to work with.

When to use it
mirroring Qonto teams in a spreadsheet, or checking that a department exists before creating it again with Create a Team.
Watch out
if both modules share a scenario, place this search before the creation step, or the check comes too late.
Qonto22

Create a Team

Action

In Make“Creates a new team to the authenticated organization.”

Create a Team adds a new team to your Qonto organization, so a new department or project gets its own space without a trip to the Qonto settings.

When to use it
a new cost center is approved in your planning tool and finance wants it mirrored in Qonto.
Watch out
it creates a team on every run, so check List Teams first when the same department name can come back.

Custom API Call

1 module
Qonto23

Make an API Call

Action

In Make“Performs an arbitrary authorized API call.”

Make an API Call reaches any endpoint of the Qonto API from your scenario, reusing the connection you already set up. It covers whatever the dedicated modules leave out.

When to use it
you need a Qonto feature that has no module of its own here, and you are ready to read the Qonto API documentation.
Watch out
you write the request yourself, so this is the one module on the page that expects some technical reading.
Need help

Need help automating Qonto with Make?

A person reads every message.

FAQ

Qonto and Make: frequent questions

01Is the Qonto Make integration free?
Yes on the Make side: Qonto is a standard app, available from the Free plan. That plan keeps 2 scenarios active, runs scheduled scenarios every 15 minutes at the shortest, stops an execution after 5 minutes and handles files up to 5 MB, with 512 MB of data transfer. Paid Make plans (Core, Pro, Teams and Enterprise) bring the interval down to 1 minute, lift the cap on active scenarios and allow 40 minutes per execution. On the Qonto side, the app only works with a paid Qonto account, so that subscription is a prerequisite.
02What does it take to connect Qonto to Make?
A paid Qonto account and a Make account. In a scenario, add any Qonto module, click Create a connection, give it a name if you like and click Save. If Qonto asks, sign in and confirm the access. That single connection then serves every Qonto module, so nothing needs repeating when you later add Create a Client Invoice or Watch New Transactions. If the connection fails on the first try, the Qonto subscription is the first thing to check.
03Do the Qonto triggers in Make fire instantly?
No. Both Qonto triggers, Watch New Transactions and Watch Updated Transactions, are scheduled: Make checks Qonto at the interval set on the scenario instead of being notified when a transaction happens. A new scenario checks every 15 minutes by default. On a paid Make plan the interval can go down to 1 minute, while 15 minutes is the floor on the Free plan. When speed matters, start the scenario from the tool where the event begins, such as the app where the sale is made.
04What if a Qonto module is missing in Make?
Use Make an API Call. It sends a request to any endpoint of the Qonto API with the connection you already have, so a feature without its own module stays reachable from the same scenario. The 25 modules cover transactions, transfers, attachments, labels, memberships, teams, clients, client invoices and credit notes, and the Make documentation lists no numeric limit for this app. Expect to read the Qonto API reference to shape the request, since this module leaves the details to you.
05Make or n8n for Qonto?
It depends on the tool your team already builds in. Make offers 25 ready modules for Qonto, including 2 scheduled triggers and Make an API Call for the rest, all assembled in a visual editor. The same app often has an n8n node as well, so check the n8n catalogue if that platform is already part of your setup. List the Qonto actions you actually need and compare them on both sides before deciding, rather than choosing a platform first and hoping the Qonto part fits.
Same platform

Other docs you might need on this stack.

Browse all integrations