How often does Dropbox data sync to Qonto?

Well polls the Dropbox API every fifteen minutes for new records; new activity reaches the downstream target on the next polling cycle. Records collected during a polling window are matched in a batch, then ranked by confidence; the Qonto write happens at the end of the window, never mid-sync.

How does Well match Dropbox records to entries in Qonto?

Well parses each Dropbox 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.

Does Well handle multi-currency records between Dropbox and Qonto?

Dropbox carries the original transaction currency on every record and Qonto natively ledgers in multiple currencies. Well preserves the original amount, applies your Qonto chart-of-accounts conversion rules at posting time, and Well writes both the source and converted amounts onto the record it posts to Qonto, so the entry keeps both sides of the trade.

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

Every Dropbox 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.

What happens if a Dropbox 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 Dropbox record. Nothing silently drops.

How does Well authenticate with Dropbox and Qonto?

Dropbox runs a manual OAuth 2.0 flow that you approve inside Dropbox; 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 at rest and in transit under TLS 1.3. Qonto hosts in the EU and Dropbox hosts outside the EU; Well processes records per the storage region configured for your workspace.

Dropbox to Qonto

AvailableNative · DropboxNative · Qonto

Connect Dropbox to Qonto with Well

Anchor Dropbox payment notifications against the next Qonto debit, so the bank line carries the original supplier reference.

Connect both toolsView all integrations

Dropbox

Source

The Dropbox connection lets Well write processed documents into your Dropbox folder.

Qonto

Target

The Qonto connection works on supplier invoices in both directions.

Why this pair

Connect Dropbox to Qonto through Well so records flow without manual rework.

What Well does between Dropbox and Qonto

One-way: Dropbox into Well into Qonto
Sync mode: Polling every 15 minutes
Up to 4 syncs/hour

Trigger from Dropbox

2 events · pick one

Well engine·recipe·When an invoice file lands in the watched Dropbox folder

Source

from upload · 15-min poll

WeWork France

via Dropbox

Invoice

When an invoice file lands in the watched Dropbox folder

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

Extract

6 fields read from Dropbox

6 fields read

VendorWeWork 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 entityWeWork France
Tax idFR48818717128
Domainwework.com
Ledger account6132 · Co-working

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
VendorWeWork France
Amount€1,284.00
Ledger6132 · Co-working
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 Dropbox invoices on the way to Qonto.

01Featured

Match supplier confirmations to outbound transfers

Payment confirmations arriving in Dropbox from a supplier are parsed for amount, reference, and date, then matched against the next Qonto debit window. Above the auto-link threshold the bank line carries the confirmation PDF; below it the queue surfaces the candidate transfer alongside.

Catch double-charge attempts from email

If a Dropbox message asks for a second payment that you have already settled out of Qonto, Well flags it before any action. The original Qonto debit is shown alongside the parsed amount and counterparty so finance can refuse the second request with one click.

Anchor inbound wire references

Inbound wire notifications in Dropbox carry a free-text reference that Qonto statements often abbreviate. Well harmonises the references so the next Qonto credit collapses onto the right invoice or receivable in the downstream ledger without manual lookup.

4 signals and actions across Dropbox and Qonto

When a document file lands in the watched Dropbox folder
Picks up a new receipt or supporting document from the watched folder and stores it as a Well document for matching. Pushed to Qonto's supplier-invoices via the /v2/supplier_invoices/bulk endpoint over OAuth.
Trigger·Document
When a supplier is detected on a parsed Dropbox file
Extracts the supplier named on a parsed file and matches it against your existing companies. Pushed to Qonto's supplier-invoices via the /v2/supplier_invoices/bulk endpoint over OAuth.
Trigger·Company
When an invoice file lands in the watched Dropbox folder
Reads the new PDF from the watched Dropbox folder and parses it into a structured invoice with supplier, amount, date, and tax. Pushed to Qonto's supplier-invoices via the /v2/supplier_invoices/bulk endpoint over OAuth.
Trigger·Invoice
Push 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

Reference

Field mapping for Dropbox → Qonto

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

Invoice fields

6 fields flow from Dropbox into Qonto.

Dropbox field	Label		Qonto field	Label
parsed.total_amount	Total amount	→	total_amount	Total
parsed.currency	Currency	→	currency	Currency
parsed.invoice_date.issue_date	Invoice date	→	issue_date	Issue date
parsed.due_date	Due date	→	due_date	Due date
parsed.invoice_number	Invoice number	→	invoice_number	Invoice number
parsed.tax_total.tax	Tax total	→	tax_amount	Tax

Company fields

3 fields flow from Dropbox into Qonto.

Dropbox field	Label		Qonto field	Label
parsed.supplier_name	Supplier name	→	supplier_name	Supplier
parsed.supplier_tax_id	Supplier tax id	→	supplier_tax_id	Tax id
parsed.vendor_domain	Domain	→	supplier_website	Website

Connect Dropbox and Qonto in three steps.

1
Connect Dropbox
Click Connect with Dropbox; you authorise the folder Well watches through Apideck's file-storage connection and authorise read access to supplier-invoice and document files read from a watched folder via Apideck file-storage. Access tokens are exchanged and refreshed automatically before they expire, and the grant is revocable from your Dropbox.
- AuthConnect
2
Map your accounts
Well discovers the Dropbox attachments matching your invoice pattern (supplier-invoice and document files read from a watched folder via Apideck file-storage) 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; you approve the connection inside Qonto and authorise the supplier_invoice.write scope so Well can POST PDFs to /v2/supplier_invoices. Access tokens are exchanged and refreshed automatically before they expire, and the grant is revocable from your Qonto.
- AuthConnect
- First sync~30 min

How Dropbox and Qonto stay secure with Well

Well calls Dropbox with an OAuth 2.0 token scoped to read-only access. Dropbox's consent screen lists the scopes before you approve; access tokens are exchanged and refreshed automatically before they expire. Well processes records per the storage region configured for your workspace; only fields strictly required by the write surface are ferried across regions.

OAuth 2.0EU residency optionGDPR-aligned

Scopes Well requests

Read Dropbox records
Scoped to supplier-invoice and document files read from a watched folder via Apideck file-storage. No access to anything else in your Dropbox 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 Dropbox records
Not granted. Dropbox is read-only on Well's side; the source of truth never moves.
refused
Read other workspaces' data
Encryption keys are per-workspace; another tenant's records are inaccessible by design.
refused

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

Frequently asked questions about Dropbox and Qonto on Well

01How often does Dropbox data sync to Qonto?: Well polls the Dropbox API every fifteen minutes for new records; new activity reaches the downstream target on the next polling cycle. Records collected during a polling window are matched in a batch, then ranked by confidence; the Qonto write happens at the end of the window, never mid-sync.
02How does Well match Dropbox records to entries in Qonto?: Well parses each Dropbox 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.
03Does Well handle multi-currency records between Dropbox and Qonto?: Dropbox carries the original transaction currency on every record and Qonto natively ledgers in multiple currencies. Well preserves the original amount, applies your Qonto chart-of-accounts conversion rules at posting time, and Well writes both the source and converted amounts onto the record it posts to Qonto, so the entry keeps both sides of the trade.
04How does Well prevent duplicates when posting Dropbox records to Qonto?: Every Dropbox 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.
05What happens if a Dropbox 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 Dropbox record. Nothing silently drops.
06How does Well authenticate with Dropbox and Qonto?: Dropbox runs a manual OAuth 2.0 flow that you approve inside Dropbox; 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 at rest and in transit under TLS 1.3. Qonto hosts in the EU and Dropbox hosts outside the EU; Well processes records per the storage region configured for your workspace.