Skip to main content
This guide explains how to connect Coalesce Quality to your MotherDuck account securely.We need this information so we can collect relevant metadata about your DuckDB tables for monitoring and data quality testing.To be able to finish this guide, you’ll need the following:
→ Access to your MotherDuck workspace and API token⏱️ Estimated time to finish: 5 minutes.

Data we collect

We collect the following from your MotherDuck account:
  • Databases, schemas, tables, views and columns
  • The estimated number of rows in each table
To build the catalog and the table metrics we read metadata only. We read your data only for the monitors and SQL tests you set up on it.

Setup MotherDuck Access

1. Get your MotherDuck account name

  1. Go to app.motherduck.com and log in.
  2. Click your profile icon in the top-right corner.
  3. In the dropdown, you’ll see your organization name and email.
    Your account name is typically your organization name (e.g. acme-corp) and often matches the prefix of your default database, for example acme-corp.db.
You’ll need this account name when filling in the MotherDuck account field in the platform.

2. Generate a MotherDuck API token

  1. While logged in to app.motherduck.com, click your profile icon again and choose Account settings.
  2. Navigate to the API Tokens tab.
  3. Click Generate new token, give it a name (e.g. synq-integration), and choose an expiry period.
  4. Copy the generated token immediately. You won’t be able to see it again once you leave the page.
  5. Paste it into the MotherDuck API token field in the platform.
Alternatively, if you’re using the CLI, you can generate a token via:

Input data in the Coalesce Quality UI

Integration name

For example MotherDuck.

MotherDuck account

The account name from step 1.

MotherDuck API token

The token from step 2. It is stored encrypted and never displayed again in our UI.

Audit table FQN (optional)

Fully qualified name (database.schema.table) of the table where Coalesce Quality writes SQL test audit logs, for example my_db.main.quality_sql_test__audit. Coalesce Quality creates the table if it does not exist. Leave it empty if you don’t run SQL tests.

Data collection options

  • Fetch table metrics (required for automatic monitors): on by default. Every 30 minutes, reads the estimated row count of each table. Automatic volume monitors stop working when it is off.
  • Catalog scope and Metrics scope restrict which databases and tables are ingested into the catalog, and which of those are scanned for metrics. Leave both empty to ingest everything the token can see.