When a supplier invoice is uploaded to Qonto
Detects supplier invoices uploaded into the Qonto invoicing inbox.
Trigger·Invoice
Integrations · Business bankingConnect Qonto to Well
Read Qonto supplier invoices and their PDF attachments into Well over OAuth, and push approved supplier-invoice PDFs back to Qonto. It is the one connector Well writes to directly through a provider API.
What flows between Well and Qonto
Well writes reconciled supplier invoice, invoice attachment, supplier back to Qonto after they clear your review queue, with the source-record link preserved. Use Qonto as the destination for entries enriched across your other connected tools.
| From Qonto | In Well | Relation | |
|---|---|---|---|
| Supplier invoice | Workspace invoice | Becomes | |
| Invoice attachment | Source document | Captures as | |
| Supplier | Vendor | Resolves to | |
| Approved invoice PDF | Qonto supplier invoice | Pushes back as |
- Sync mode
- incremental polling
- Refresh
- scheduled
- Direction
- Qonto ⇄ Well
3 triggers and actions in Qonto.
When a Qonto supplier invoice is updated
Picks up any update to a Qonto supplier invoice the next time Well checks for updates.
Trigger·InvoicePush a supplier invoice PDF to Qonto
Well POSTs the supplier invoice PDF to Qonto's /v2/supplier_invoices/bulk endpoint via OAuth so the invoice appears under your Qonto supplier invoices.
Action·Document
What Well does with your Qonto connection
Connect
Connect Qonto over OAuth 2.0: you approve on Qonto's authorize screen, so the password never reaches Well; Well holds only a scoped token it can refresh.
Sync
Well brings supplier invoice, invoice attachment, and supplier in from Qonto on a recurring poll that fetches only what changed since the last read. The first sync backfills history in the background and the connection stays live after.
Enrich
Well resolves each Qonto entity into workspace invoice, source document, and vendor, assigns categories, and links every record to an audit trail across the rest of your connected tools.
Available
Your data from Qonto lands as workspace invoice, source document, and vendor you can search, chart, and automate, and approved records flow back to Qonto once they clear your review queue.
Questions Qonto unlocks
Ask in plain language. Well answers from your connected Qonto connection, resolved against the rest of your stack.
Ask Well
Ask anything about your Qonto connection
Summarise this month
What needs attention?
Find unmatched records
Ask about your Qonto connection…
Connect Qonto in three steps
- 01
Authorise Qonto over OAuth
Select Qonto in Well's Connections panel and complete the OAuth 2.0 authorisation. You approve organisation read and supplier-invoice read and write on Qonto's screen; no key is pasted into Well.
- AuthOAuth 2.0 (auth code)
- Scopessupplier_invoice.read / .write, organization.read
- WritePOST supplier invoice from PDF
- 02
Map your entities
Well reads your Qonto supplier invoices and their PDF attachments into the workspace as structured invoices with the source document. It does not read bank transactions, transfers, or cards; the scope is supplier invoices only.
- Mappingpreconfigured by Well
- 03
Use the data
Once a supplier-invoice PDF clears review, Well pushes the file back to Qonto through its bulk supplier-invoice endpoint and Qonto creates the invoice. This direct API write makes Qonto the cohort's only write target; Qonto stays the system of record.
- First syncstarts as soon as connect completes
The OAuth handshake completes in about a minute. Supplier invoices read on connect; approved invoice PDFs push back as they clear your queue. Qonto developer docs.
How Qonto stays secure with Well
Qonto authorises over OAuth 2.0 with scopes limited to organisation read and supplier-invoice read and write, so Well holds no Qonto API key and the grant cannot reach bank transactions, transfers, or cards. Well reads supplier invoices in and, uniquely in this cohort, writes approved supplier-invoice PDFs back through Qonto's bulk endpoint. The token can do exactly two things: read your supplier invoices and create one from a PDF you approved.
OAuth 2.0Encrypted at restGDPR compliant
Read the full privacy and security policyScopes Well requests
- granted
Read Qonto records
Endpoints the Qonto API token grants, scoped by your consent.
- granted
Resolve supplier invoice, invoice attachment, supplier, and approved invoice PDF across your stack
Match identifiers in Qonto against the same entities your other connected tools expose, so each record carries cross-tool context.
- granted
Post approved records to Qonto
Over Qonto's API, only records you've approved (case-by-case or via a per-rule auto-post threshold).
- refused
Store Qonto passwords or session cookies
Authentication runs through OAuth 2.0 tokens we never see.
Disconnect any time from Well settings or Qonto’s admin panel.
Frequently asked questions about Qonto and Well
Choose Qonto in Well's Connections panel and authorise over OAuth 2.0. Well requests organisation read plus supplier-invoice read and write scopes, which you approve on Qonto's own screen. The grant is narrow on purpose: it covers reading your supplier invoices and pushing supplier-invoice PDFs back, and nothing wider.
Well reads your Qonto supplier invoices and their PDF attachments, bringing each one into the workspace as a structured invoice with its source document. It does not pull bank transactions, transfers, cards, or account balances; the Qonto connector is scoped to supplier invoices, so that is exactly what comes across. What you see synced is what the scope grants.
After a supplier-invoice PDF clears your review, Well pushes the file to Qonto through its bulk supplier-invoice endpoint, and Qonto creates the supplier invoice from it. This is a genuine OAuth API write, not an email-in handoff, which makes Qonto the only direct write target in the cohort. Well writes only the supplier-invoice file you approved; it cannot move money or touch transfers.
Not from Qonto directly, because Well does not read Qonto's bank transactions; the connector handles supplier invoices, not the transaction feed. Bank-movement reconciliation comes from a banking source you connect for that purpose. On the Qonto side, the value is the supplier-invoice round trip: read the invoices in, push approved invoice PDFs back out.
Well reads supplier invoices from Qonto in the background and folds new and updated ones into the workspace as it picks them up, with the first connect bringing in the existing set. You can query the invoices that have arrived while the rest fill in. Qonto stays the system of record; Well keeps a queryable copy and pushes approved invoice PDFs back.
Disconnect Qonto in Well and the OAuth token is dropped, so Well stops reading supplier invoices and can no longer push any back. Because the write is limited to supplier-invoice PDFs you approved, there is nothing else to reverse. Invoices Well already mirrored stay in your workspace, and the supplier invoices created in Qonto remain in Qonto.
Connect Qonto with
Ready-to-ship workflows that pair Qonto with another tool through Well.
Pairs well with Qonto
More in Business banking
Anytime
Connect Anytime to Well to sync business bank accounts and transactions.
Blank
Connect Blank to Well to sync business bank accounts and transactions.
Bourso Business
Connect Bourso Business to Well to sync business bank accounts and transactions.
Husk
Connect Husk to Well to sync business bank accounts and transactions.
Popular cross-category
Ready to connect Qonto?
Connect once. Every supplier invoice, invoice attachment, supplier from Qonto becomes searchable, queryable, and ready for your agents and tables. Disconnect any time.