This guide will walk you through how to connect your Coalesce Transform workspace to SYNQ to track pipeline runs, job statuses, and metadata changes.To finish this guide, you’ll need the following:
→ Admin access to your SYNQ workspace
→ Admin access to your Coalesce Transform workspace
→ Ability to generate API tokens in Coalesce⏱️ Estimated time to finish: 10 minutes.
→ Admin access to your SYNQ workspace
→ Admin access to your Coalesce Transform workspace
→ Ability to generate API tokens in Coalesce⏱️ Estimated time to finish: 10 minutes.
Integration
Coalesce is a metadata-driven data transformation platform that helps data teams build and operate governed data pipelines on cloud data platforms. It combines visual DAG-based design with code editing capabilities, built-in governance, and column-level lineage tracking.SYNQ uses read-only APIs to fetch metadata from Coalesce. The integration cannot modify your Coalesce projects, configurations, or pipelines.
Transformation Catalog & Discovery
See your entire Coalesce landscape in SYNQ:- Projects with their Git repository connections
- Environments (dev, staging, prod) with their configurations
- Nodes (transformations) - what each one does, where it writes data
- Jobs - scheduled transformation groups
Run Monitoring & Alerting
Every transformation execution is tracked:- Deploy runs - when new transformation code is deployed
- Refresh runs - when scheduled jobs execute
- Per-query details - which SQL ran, how long it took, rows affected
Data Lineage
Table-level lineage:- Which Coalesce nodes feed into which downstream nodes
- Connection to physical warehouse tables (Snowflake, BigQuery, etc.)
- Which source columns flow into which target columns
- Whether columns are passed through, renamed, or transformed
Data Quality Test Results
Coalesce SQL tests are tracked as part of runs:- Node-level tests (custom SQL assertions)
- Column-level tests (null checks, uniqueness, etc.)
- Pass/fail status per test
- Whether failures block the pipeline or just warn
SQL Visibility
The actual SQL executed by Coalesce is captured:- Pre-SQL (setup statements)
- Main transformation query
- Post-SQL (cleanup/grants)
- Test queries
Cross-Platform Connectivity
Coalesce nodes are linked to:- Their physical warehouse tables (identity relationship)
- Git files that define them
- Downstream BI tools that query the output tables
Setup guide
Name your integration
For exampleCoalesce Transform or Production Coalesce
Select the region
Select your Coalesce server region from the dropdown:| Region | Endpoint |
|---|---|
| US primary | https://app.coalescesoftware.io |
| Europe primary | https://app.eu.coalescesoftware.io |
| Australia primary | https://app.australia-southeast1.gcp.coalescesoftware.io |
| US AWS US East | https://app.us-east-1.aws.coalescesoftware.io |
| US AWS US East with PrivateLink | https://app.us-east-1.aws.privatelink.coalescesoftware.io |
| US AWS US West | https://app.us-west-2.aws.coalescesoftware.io |
| US AWS US West with PrivateLink | https://app.us-west-2.aws.privatelink.coalescesoftware.io |
| Canada Primary | https://app.northamerica-northeast1.gcp.coalescesoftware.io |
| US Azure West 2 | https://app.westus2.azure.coalescesoftware.io |
| US Azure East 2 | https://app.eastus2.azure.coalescesoftware.io |
| Custom endpoint | Enter your own URL |
If your Coalesce instance uses a custom domain or private deployment, select Custom endpoint and enter your Coalesce API URL. Must be an HTTPS URL.
Generate a token
These steps will take you through how to create a token you can use to manage SYNQ access to your Coalesce Transform project
- Log into your Coalesce workspace
- Navigate to the Deploy section
- Click Generate Access Token
- Copy the generated token immediately (you won’t be able to view it again)
- Paste it into the API Token field in SYNQ
Your Coalesce account must have API access enabled. The generated token will have the same access rights as the user who created it, so ensure you have access to the projects you want to sync with SYNQ.
Configure fetch interval
Configure how often SYNQ should poll Coalesce for updates. Default: 5 minutes You can adjust this based on:- Higher frequency (1-5 minutes): For production environments where you need near real-time monitoring
- Lower frequency (10-30 minutes): For development environments or when API rate limits are a concern
Select projects
After entering valid credentials, SYNQ will automatically load your available Coalesce projects. You can:- Select specific projects by checking the boxes next to project names
- Sync all projects by leaving all checkboxes unchecked. This is useful when you want SYNQ to automatically include new projects as they’re created in Coalesce.
- All environments - sync all environments in the project
- Include specific environments - only sync selected environments
- Exclude specific environments - sync all except selected environments
Recommendation: If you have many projects, start by selecting only production projects. You can always edit the integration later to include additional projects.
Typical use cases
| Use Case | How SYNQ Helps |
|---|---|
| ”Our dashboard is showing stale data” | See if Coalesce refresh job failed, when it last ran successfully |
| ”We’re changing a source table schema” | Trace lineage to see which Coalesce nodes and downstream assets are affected |
| ”Transformation is slow” | See query execution times, identify bottlenecks |
| ”Data quality issue in production” | Check which Coalesce tests passed/failed, see test history |
| ”Who changed this transformation?” | See deploy runs with commit info and user who triggered |
| ”What does this Coalesce node actually do?” | View the SQL definition and column-level lineage |
FAQ
What access do you require?
We only request read access to your metadata and won’t be able to read raw data or update or run any models.Will you store personal or business-critical data?
SYNQ only stores log level data and doesn’t access any actual data from your data warehouse.What if projects don’t load?
If projects don’t appear after entering your credentials:- Verify your API token is correct
- Ensure the API endpoint matches your Coalesce region
- Check that your token has the required read permissions
- Try regenerating the token in Coalesce with appropriate permissions