Linking Qonto as a source
Let AI connect your sources for you
Skip the manual setup — run this in your project and the wizard auto-detects your databases and APIs and connects them to PostHog.
This source is currently in alpha. The interface and available tables may change.
The Qonto connector syncs your business banking data into the PostHog data warehouse, so you can analyze transactions, transfers, and account activity alongside your product data.
Qonto is a European business finance platform. This source syncs bank accounts, transactions, labels, memberships, and SEPA transfers. The transactions and transfers tables support incremental sync using the updated_at field, so only new or updated rows are fetched after the initial sync.
Prerequisites
You need a Qonto account with API access. You can find your credentials in the Qonto dashboard under Integrations and Partnerships > API key. You'll need your organization login and secret key.
Adding a data source
- In PostHog, go to the Sources tab of the data pipeline section.
- Click + New source and click Link next to this source.
- Enter your credentials (see Configuration below) and click Next.
- Select the tables you want to sync, choose a sync method and frequency, then click Import.
Once the syncs are complete, you can start querying this data in PostHog.
When linking Qonto, you'll need:
- Organization login – your Qonto organization login, found in your Qonto dashboard under Integrations and Partnerships > API key.
- Secret key – your Qonto API secret key, found on the same page.
Sync modes
Each table can be synced in one of several modes, depending on what the source supports:
- Webhook (when available) – the source pushes changes to PostHog in real time. Fastest freshness, lowest ongoing cost, and the only mode that reliably captures updates and deletes.
- Incremental – only new or updated rows are synced on each run, using a cursor field (such as an
updated_attimestamp). Cheaper than a full refresh, but deletes aren't captured. - Append only – new rows are appended using a cursor field; existing rows are never updated. Ideal for immutable, append-only tables like event logs.
- Full refresh – the whole table is reloaded on every sync. Use it when a table has no reliable cursor or when you need deletions reflected.
See sync methods for a full explanation of how each mode works and how to choose between them.
Configuration
| Option | Type | Required |
|---|---|---|
Organization login | text | Yes |
Secret key | password | Yes |
Supported tables
| Table | Description | Sync method | Incremental field | Primary key |
|---|---|---|---|---|
bank_accounts | Qonto bank accounts for the authenticated organization, including balances and account details. | Full refresh | — | — |
transactions | Transactions across Qonto bank accounts, including pending, declined, completed, and reversed transactions. | Incremental, Full refresh | updated_at | — |
labels | Labels that classify transactions for the authenticated organization. | Full refresh | — | — |
memberships | Users with access to the organization's Qonto account. | Full refresh | — | — |
transfers | SEPA transfers for the authenticated organization. | Incremental, Full refresh | updated_at | — |
Troubleshooting
- If you see an authentication error, your organization login or secret key is invalid or has been revoked. Generate a new API key in your Qonto dashboard under Integrations and Partnerships > API key, then reconnect.
- If you see a permissions error, the API key does not have permission to read this data. Check the key's permissions in your Qonto dashboard.
- This source only syncs accounts owned by your organization. Connected external accounts are excluded.
If your sync is failing or data looks wrong, see the Data warehouse troubleshooting guide. If that doesn't help, contact support – we're happy to help.