How does Well match Gmail records to entries in Qonto?

Well parses each Gmail attachment into a structured invoice, then probes your Qonto ledger for an open bill or vendor with the same amount, due date, and supplier name. The probe ranks candidates by counterparty proximity, date window, and total match; above 85% it links the parsed PDF to the existing Qonto entry, otherwise the parsed invoice queues for sign-off with the candidates surfaced.

What happens to historical Gmail data when I first connect to Qonto?

Gmail exposes the last full year through its API on a connected account. The window Well actually pulls is configurable from the integration settings page; each record is matched against your existing Qonto ledger, and re-running the backfill is safe because Well tracks the Gmail record IDs and updates existing Qonto entries instead of duplicating them.

How does Well prevent duplicates when posting Gmail records to Qonto?

Every Gmail message has a stable message ID, and Well stores it the moment the attachment is parsed. If the same email is reprocessed (label change, mailbox migration, or a manual rerun), Well recognises the message ID and skips the duplicate, or updates the linked Qonto entry if a downstream field changed. Forwarded copies of the same invoice are caught by counterparty-plus-amount matching before they reach Qonto.

Can I customise which Gmail fields are sent to Qonto?

The default mapping turns every parsed Gmail attachment into a Qonto-shaped record (vendor, amount, due date, tax). From the integration settings page you can adjust the parsing prompt, force a vendor mapping, attach the original PDF on a specific Qonto field, or compute a tag from your connected data. Custom mappings are versioned so a change does not retroactively touch already-posted Qonto entries.

What happens if a Gmail record fails to post to Qonto?

When a record fails to post to Qonto (validation rule, missing field, transient 5xx), Well retries automatically with backoff. Auth failures short-circuit the retry loop and notify the workspace owner; schema rejections are kept on the integration status page with a one-click retry-after-fix action pointing back at the original Gmail record. Nothing silently drops.

How does Well authenticate with Gmail and Qonto?

Gmail runs a manual OAuth 2.0 flow that you approve inside Gmail; Well receives a refresh token scoped to the resources it needs to read. For the delivery side, once a record clears the matching threshold Well posts it directly to Qonto over the connected API; the credential is held per-workspace and never exchanged across tenants. Tokens are encrypted in transit under TLS 1.3. Anything Well holds between Gmail and Qonto is encrypted at rest and handled in line with GDPR.

Gmail to Qonto

AvailableNative · GmailNative · Qonto

Connect Gmail to Qonto with Well

When a supplier emails a payment confirmation, Well anchors it to the next Qonto debit so the bank line is reconciled before the supplier even checks back in.

Connect both toolsView all integrations

Active in production

On this connection

15workspaces

Live in production since November 2025.

27% also use Google Drive

Most common third connector on this pair

Business & productivity software · Bank, FX & payment-processing fees · Meals & entertainment

Most-matched vendor categories

6,708

Matches analyzed to date across these workspaces

684

Records synced to date across these workspaces

4,753

Invoices processed to date across these workspaces

99%

Auto-post-ready across Well, to date

Adoption figures for this connection · updated 2026-07-07. Auto-post-ready % is a platform-wide rate across all of Well, to date (confidence ≥ 0.85). Numbers anonymised; no customer identifying data.

Gmail

Source

The Gmail integration turns your inbox into an automated invoice capture flow.

Qonto

Target

Qonto is two separate authorisations, not one.

Why this pair

Suppliers email invoices as PDF attachments, and Qonto exposes a separate supplier-invoice upload path that is not linked to the bank transaction by default.

Connecting Gmail to Qonto through Well uploads each emailed invoice to Qonto's supplier-invoices via the /v2/supplier_invoices/bulk endpoint, then reconciles it inside Well against the eventual bank-line outflow so one record carries both the invoice and the payment. Gmail pushes new message events to Well via Pub/Sub; Well POSTs the supplier invoice PDF to Qonto over OAuth at that cadence.

What Well does between Gmail and Qonto

One-way: Gmail into Well into Qonto
Sync mode: Real-time webhooks
Events arrive within a minute

Trigger from Gmail

5 events · pick one

Well engine·recipe·When an invoice PDF arrives as an attachment

Source

from email · live webhook

Air France

via Gmail

Invoice

When an invoice PDF arrives as an attachment

INV-2026-04-100 · 22 Apr 2026€1,284.00

Extract

6 fields read from Gmail

6 fields read

VendorAir France
Invoice numberINV-2026-04-100
Issue date22 Apr 2026
Total€1,284.00
Tax€256.80

Enrich

against your historical record graph

5 fields added

Legal entityAir France
Tax idFR45420495178
Domainairfrance.com
Ledger account6251 · Travel

Confidence97%

<55% refused55–85% review≥85% auto-posts

Post

reconcile as supplier invoices

Push a supplier invoice PDF to Qonto

auto-posted

posted

TypeSupplier invoice
VendorAir France
Amount€1,284.00
Ledger6251 · Travel
Source docattached
Confidence97%

audit linkto Qonto

Action in Qonto

1 compatible with this trigger

Push a supplier invoice PDF to Qonto

What Well does with Gmail invoices on the way to Qonto.

01Featured

Capture an invoice from email

Well reads an invoice PDF from a Gmail attachment with its sender and date, so the document is ready to match.

Match against Qonto invoices

Well reads the supplier invoices and attachments from Qonto and matches each to the invoice from Gmail, so the supplier is resolved.

Keep the email trail

The sender, subject, and date from Gmail stay attached to the matched document, so each invoice traces to its message.

One document, not copies

When the same invoice arrives twice in Gmail, Well keeps one before matching, so Qonto records do not double up.

7 signals and actions across Gmail and Qonto

When an email with an invoice attachment is received
Pulls from your Gmail inbox. Well picks up any received email with a PDF attachment; forwarded headers are recovered automatically. Pushed to Qonto's supplier-invoices via the /v2/supplier_invoices/bulk endpoint over OAuth.
Trigger·Invoice
When an email with a bill attachment is processed by Well
Pulls from your Gmail inbox. Well's AI extracts the bill from the attached PDF and matches the vendor against your existing records. Pushed to Qonto's supplier-invoices via the /v2/supplier_invoices/bulk endpoint over OAuth.
Trigger·Invoice
When an email arrives from a sender domain not yet in your vendor list
Pulls from your Gmail inbox. Well prepares a new vendor record from the email and document headers for your confirmation. Pushed to Qonto's supplier-invoices via the /v2/supplier_invoices/bulk endpoint over OAuth.
Trigger·Invoice
When an invoice PDF arrives as an attachment
Pulls from your Gmail inbox. Picks up emails matching has:attachment filename:pdf and runs the document through extraction. Pushed to Qonto's supplier-invoices via the /v2/supplier_invoices/bulk endpoint over OAuth.
Trigger·Invoice
When an email attachment is processed by Well
Pulls from your Gmail inbox. Receipts, invoices, statements: any PDF attachment is read and captured into your records. Pushed to Qonto's supplier-invoices via the /v2/supplier_invoices/bulk endpoint over OAuth.
Trigger·Document
When an email arrives from a sender domain already in your vendor list
Pulls from your Gmail inbox. The vendor is matched against your existing company records. Pushed to Qonto's supplier-invoices via the /v2/supplier_invoices/bulk endpoint over OAuth.
Trigger·Invoice
Push a supplier invoice PDF to Qonto
Driven by emailed invoices, receipts, and notifications. 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

Reference

Field mapping for Gmail → Qonto

9 fields across 2 record types, open to see the full table.

Invoice fields

6 fields flow from Gmail into Qonto.

Gmail field	Label		Qonto field	Label
extracted.invoice_number	Invoice number	→	invoice_number	Invoice number
extracted.issue_date	Issue date	→	issue_date	Issue date
extracted.due_date	Due date	→	due_date	Due date
extracted.total	Total	→	total_amount	Total
extracted.tax	Tax	→	tax_amount	Tax
extracted.currency	Currency	→	currency	Currency

Company fields

3 fields flow from Gmail into Qonto.

Gmail field	Label		Qonto field	Label
extracted.vendor_name	Vendor name	→	supplier_name	Supplier
extracted.vendor_domain	Vendor domain	→	supplier_website	Website
extracted.vendor_tax_id	Vendor tax id	→	supplier_tax_id	Tax id

Connect Gmail and Qonto in three steps.

1
Connect Gmail
Click Connect with Google; Google asks which mailbox to scope and returns a refresh token and authorise read access to invoice and receipt PDFs from email attachments, plus the sender, subject, and date headers. Access tokens are exchanged and refreshed automatically before they expire, and the grant is revocable from your Google Workspace.
- AuthConnect
2
Map your accounts
Well discovers the Gmail attachments matching your invoice pattern (invoice and receipt PDFs from email attachments, plus the sender, subject, and date headers) and the the Qonto supplier-invoices section. Tune the parsing prompt once on the first ten records; Well saves the mapping and applies it to every subsequent attachment above 85% confidence.
- Auto-post above85% confidence
- Overridemanual anytime
3
Connect Qonto
Click Connect with Qonto; Well's OAuth proxy handles Qonto authorisation through Dynamic Client Registration. Qonto's MCP server registers a write-scoped Well client through DCR; no credential paste, no shared secret.
- AuthOAuth 2.0
- First sync~30 min

24 agent skills run on Gmail and Qonto.

Each one answers a question from the data this pair brings in. The required ones return nothing until a source like it is connected.

Needs a source like these

Runway

Know exactly how many months and days of cash you have left.

Cash position

Know exactly how much cash you have, and which accounts it came from.

Cost structure

See where your company's money actually goes, no spreadsheets required.

Receivables aging

See who owes you money, and how long they've been sitting on it.

Bills due

See exactly what's coming due, in what order, and how much cash it adds up to.

Rank clients by LTV

Find out who your best customers really are, ranked by what they've actually paid.

Company profile

Everything you know about one company, in one view.

Payment and invoice lookup

Find what payment settled an invoice, or catch every payment that never got one.

Missing receipts

Find the bills with no paperwork attached, before an auditor does.

Draft invoice

Turn a sentence into a real invoice in Well, PDF attached, no template hunting.

Burn rate

Know what you actually spend each month, averaged over real months.

Recurring revenue

Know what you can count on earning each month, averaged over real months.

Cash forecast

See where your cash lands if nothing new comes in.

Cash movement

See the bridge from last month's balance to this one.

Missing supplier invoices

See which suppliers owe you paperwork, before your accountant asks.

Assign missing invoices

Put a name on every settled expense that still has no invoice.

Missing invoice sweep

Walk the whole month-end sweep in one prompt.

Close the books

Drive the month-end close to the point of approval.

Categorize your suppliers

Close the category gaps behind your spend before you close a month.

Answers better with these connected

FX exposure

See how much of your cash and receivables sit outside your home currency.

Invoice fetching agents

See exactly which agents would run, before any of them does.

Convert currencies

Turn mixed currencies into one number you can actually audit.

Connects and checks them

Check your connections

See what is connected, what is syncing, and what is missing.

Connect your bank

Get the bank feed in, and confirm it is really live.

Browse all skills

How Gmail and Qonto stay secure with Well

Well calls Gmail with an OAuth 2.0 token scoped to read-only access. Gmail's consent screen lists the scopes before you approve; access tokens are exchanged and refreshed automatically before they expire. Anything Well holds between Gmail and Qonto is encrypted at rest and handled in line with GDPR.

OAuth 2.0Encrypted at restGDPR compliant

Scopes Well requests

Read Gmail records
Scoped to invoice and receipt PDFs from email attachments, plus the sender, subject, and date headers. No access to anything else in your Gmail account.
granted
Post approved records to Qonto
Over Qonto's API, scoped to supplier invoice PDFs pushed via OAuth to /v2/supplier_invoices you have approved (case-by-case or via a per-rule auto-post threshold).
granted
Modify or delete Gmail records
Not granted. Gmail is read-only on Well's side; the source of truth never moves.
refused
Read other workspaces' data
Not granted. A session resolves only to the workspaces your account belongs to, and Well checks that membership before it returns any record.
refused

Disconnect any time from Well settings or Gmail’s admin panel.

Frequently asked questions about Gmail and Qonto on Well

01How does Well match Gmail records to entries in Qonto?: Well parses each Gmail attachment into a structured invoice, then probes your Qonto ledger for an open bill or vendor with the same amount, due date, and supplier name. The probe ranks candidates by counterparty proximity, date window, and total match; above 85% it links the parsed PDF to the existing Qonto entry, otherwise the parsed invoice queues for sign-off with the candidates surfaced.
02What happens to historical Gmail data when I first connect to Qonto?: Gmail exposes the last full year through its API on a connected account. The window Well actually pulls is configurable from the integration settings page; each record is matched against your existing Qonto ledger, and re-running the backfill is safe because Well tracks the Gmail record IDs and updates existing Qonto entries instead of duplicating them.
03How does Well prevent duplicates when posting Gmail records to Qonto?: Every Gmail message has a stable message ID, and Well stores it the moment the attachment is parsed. If the same email is reprocessed (label change, mailbox migration, or a manual rerun), Well recognises the message ID and skips the duplicate, or updates the linked Qonto entry if a downstream field changed. Forwarded copies of the same invoice are caught by counterparty-plus-amount matching before they reach Qonto.
04Can I customise which Gmail fields are sent to Qonto?: The default mapping turns every parsed Gmail attachment into a Qonto-shaped record (vendor, amount, due date, tax). From the integration settings page you can adjust the parsing prompt, force a vendor mapping, attach the original PDF on a specific Qonto field, or compute a tag from your connected data. Custom mappings are versioned so a change does not retroactively touch already-posted Qonto entries.
05What happens if a Gmail record fails to post to Qonto?: When a record fails to post to Qonto (validation rule, missing field, transient 5xx), Well retries automatically with backoff. Auth failures short-circuit the retry loop and notify the workspace owner; schema rejections are kept on the integration status page with a one-click retry-after-fix action pointing back at the original Gmail record. Nothing silently drops.
06How does Well authenticate with Gmail and Qonto?: Gmail runs a manual OAuth 2.0 flow that you approve inside Gmail; Well receives a refresh token scoped to the resources it needs to read. For the delivery side, once a record clears the matching threshold Well posts it directly to Qonto over the connected API; the credential is held per-workspace and never exchanged across tenants. Tokens are encrypted in transit under TLS 1.3. Anything Well holds between Gmail and Qonto is encrypted at rest and handled in line with GDPR.