Set up Coalesce Private Preview

Generate a Coalesce API token and confirm your environment prerequisites so Atlan can fetch nodes, lineage, and run status from Coalesce.

Prerequisites

Before you begin, make sure you have:

• A Coalesce account with administrator-equivalent access to generate API tokens.
• The Snowflake connector already installed in Atlan and a successful crawl completed. Coalesce metadata enriches your existing Snowflake assets, so Atlan must have those Snowflake tables in the catalog before it can attach Coalesce status, lineage, and announcements to them.
• For large workspaces (thousands of nodes), a confirmed API rate-limit threshold from your Coalesce account team. See Rate limits and large workspaces below.
• Access to the Coalesce projects and environments you want to surface in Atlan. The token inherits the generating user's permissions—a user without access to a given project or environment can't produce a token that reads it.

Generate Coalesce API token

1. Sign in to Coalesce at https://app.coalescesoftware.io.
2. Go to the Deploy tab and click Generate Access Tokens. If you don't see this option, follow Coalesce's API token documentation for the latest UI path.

tip

Scope the token to only the projects and environments you intend to surface in Atlan. This limits the impact if the token is ever compromised or needs to be rotated.

3. Copy the bearer token.
4. Store the token in a secret manager. You need it when configuring the crawler workflow in Atlan.

Verify Snowflake connector crawl status

The Coalesce connector writes its enrichment (sqlCoalesce* attributes, announcement banners, and lineage targets) directly onto Snowflake tables and views that Atlan already knows about. If your Snowflake connector hasn't crawled yet, the Coalesce crawl runs successfully but produces no visible enrichment in the UI.

1. In Atlan, confirm your Snowflake connection exists and has completed at least one successful crawl.
2. Open the Snowflake database and schema that Coalesce materializes into, and confirm its tables and views appear with their standard Snowflake metadata.
3. If the connection is missing or the target tables aren't there, set up or re-crawl the Snowflake connector before crawling Coalesce.

Rate limits and large workspaces

Coalesce may enforce per-account API rate limits, as is standard for SaaS APIs. For typical workspaces (a few hundred nodes) the Atlan connector stays well under the threshold and no coordination is needed.

For larger workspaces, plan ahead:

Workspace size	Recommended action
Up to ~500 nodes	No coordination required. Default crawl cadence is fine.
500–2,000 nodes	Confirm your current Coalesce API rate-limit threshold with your Coalesce account team before the first crawl.
More than ~2,000 nodes	The connector has been validated up to ~2,000 nodes. For larger workspaces, contact your Atlan customer success manager before connecting.

If a crawl encounters HTTP 429 (too many requests), Atlan retries with exponential backoff. The crawl still completes, but it runs slower. Proactive rate-limit coordination keeps initial crawls smooth.

warning

Each Atlan crawl makes a high volume of Coalesce API calls. For every environment, the connector lists recent runs and then fetches per-node results for each walked run, so a single crawl can issue many API calls per environment. Run the connector only as frequently as you need refreshed status—less-frequent crawls are the safer default for large workspaces.

Next steps

• Crawl Coalesce assets: Configure the crawler and run your first crawl.