Coalesce

Our integration with Coalesce Transform brings deeper visibility and context to your data lineage, documentation, and quality monitoring. By connecting your Coalesce environment to the Catalog, you can effortlessly trace, understand, and trust your data pipelines.

🔍 Use Cases

1. Understand Data Origins at a Glance

Quickly identify which tables in your warehouse were built via Coalesce, directly from the Catalog interface. This gives data teams immediate visibility into how and where transformation logic is applied.

2. Explore Lineage with Visual Cues

See Coalesce-built tables marked with the Coalesce logo directly in the lineage graph. This allows for fast troubleshooting and intuitive exploration of upstream dependencies and downstream consumers.

3. Enrich Documentation Automatically

Pull in external table and column descriptions directly from Coalesce, ensuring your documentation stays consistent and up to date across platforms. → This feature currently supports:

• Fullstack integration ✅: Direct sync of descriptions

• Extraction-based sync ⚙️: Pull-only (read-only) metadata

4. Monitor Data Quality

Activate Coalesce Quality as a Data Quality Source to bring test results into the Catalog. This helps teams proactively identify issues and surface data quality insights alongside technical metadata.

5. Sync Back descriptions: from Catalog to Coalesce Transform

Required Set Up

Two configuration are needed are required to unlock all features

• Setting up a Coalesce Transform API access

• Granting read access to your Git repositories

See below which features require which set up

Set up the API Connection

In the Catalog integration Page, scroll to the Transformation or Quality section, click on the Coalesce integration.

For credentials, you only have to paste your Coalesce Transform token, you can find on your deploy homepage here

Replace with your toklen and paste this code:

{
	"host": "https://<your_host>.coalescesoftware.io",
	"token": "<****>",
}

Grant access to your git repositories

For Github:

• We only need you to grant contributor access to our technical Github user techcastor to your coalesce Github repositories so we can push a new branch with the updates. For more details on this check here

• Here is the user: https://github.com/techcastor

For Gitlab:

• We need a Project Access Token (PAT) to your dbt Gitlab repository, more information here

• In token configuration the only scope needed is write_repository and Contributor role must be selected so we can push a new branch with the updates

• The token should then be sent to our support either through [email protected] or Slack alongside the HTTP needed to clone the repository