Docs / Data sources / Qonto

Qonto

Finance and operations

Built when you ask for it

Sync Qonto transaction, membership, label, and attachment data into your warehouse. Ingest builds this connector the first time a customer asks for it, then keeps the tables current in a data warehouse you own, on the schedule you choose.

The Qonto connector syncs your European business banking data into analytics-ready tables in your data warehouse. Pull transactions, memberships, labels, and attachments from the Qonto Business API, with Ingest handling auth, pagination, and retries so the tables stay current.

What you would get

Each of these arrives as its own table, kept current on the schedule you choose:

  • Transactions
  • Memberships
  • Labels
  • Attachments

How it gets built

  1. Choose Qonto when you set up a pipeline, with the warehouse it goes to and a schedule.
  2. Ingest reads Qonto's documentation, and you choose the tables you want.
  3. Ingest builds the connector and tests it against Qonto itself.
  4. A person at Ingest reviews and publishes it, and your pipeline starts on its own.

What you will need

API key (login:secret-key in Authorization header); OAuth 2.0 for multi-tenant integrations. Generate the key under Integrations and Partnerships > API key in the Qonto web app.

You enter it once, in a form in Ingest, and it is kept in a secret store set aside for your organization.

Questions

Does Ingest have a Qonto connector?
Not as a finished connector yet. Ingest builds it from Qonto's own documentation the first time a customer asks, tests it against the real service, and lists it once it passes.
Which warehouses can Qonto data go to?
Amazon S3, Google Cloud Storage, Azure Blob Storage, Apache Iceberg, Ingest Managed Lakehouse, MotherDuck, Postgres, Amazon Athena, Databricks, Redshift, BigQuery, ClickHouse, MySQL / generic SQL and Snowflake, in an account you own.
Do I need to write code?
No. Ingest builds, runs and maintains the connector. Someone with access to your warehouse connects it once, following a short guide.

Qonto API documentation: https://docs.qonto.com/get-started/business-api/authentication/introduction

Setting up the destination is its own short guide, one per warehouse or lake: Amazon S3, Google Cloud Storage, Azure Blob Storage, Apache Iceberg, Ingest Managed Lakehouse, MotherDuck, Postgres, Amazon Athena, Databricks, Redshift, BigQuery, ClickHouse, MySQL / generic SQL, Snowflake.

Other sources Ingest connects for ERP teams: SAP, Oracle NetSuite, Microsoft Dynamics 365, Workday, Odoo, Acumatica.

Request Qonto