Introducing Flights: agent-native data pipelines in MotherDuckJoin the livestream

Skip to main content

Airbyte

Airbyte is a data integration platform for connecting data sources to warehouses. It integrates with MotherDuck for loading data from operational systems, APIs, files, or event streams.

How it works with MotherDuck​

Airbyte can load data into MotherDuck with the MotherDuck destination connector.

Prerequisites​

  • An Airbyte workspace with permission to create destinations.
  • A MotherDuck access token.
  • An existing MotherDuck database to use as the destination.

Setup​

  1. In MotherDuck, create an access token for Airbyte.
  2. In Airbyte, create a new destination and select MotherDuck.
  3. Set Destination DB to an md: database path, for example md:analytics.
  4. Paste the token into MotherDuck Access Token.
  5. Optional: set Schema Name. Airbyte namespaces map to MotherDuck schemas.
  6. Save the destination and use it in a connection.

Authentication and configuration​

  • Use Airbyte's MotherDuck Access Token field instead of putting the token in the md: URI.
  • Use destination_path for the database path.
  • Use the Airbyte schema field to control the default schema for loaded streams.

Important notes​

  • Airbyte warns against putting the token in the connection string because it can be printed in execution logs.
  • The destination supports full refresh and incremental sync modes.
  • Airbyte's connector reference includes local DuckDB file options. For MotherDuck, use the md: destination path.

Use cases​

  • Replicate SaaS, API, file, or database sources into MotherDuck.
  • Land Airbyte streams into a dedicated MotherDuck schema.
  • Use Airbyte Destinations V2 final tables as downstream analytics sources in MotherDuck.

Related content​