Skip to content
finn.
Integrations Atlan

Integration · Knowledge and documents

Atlan + Finn.

Atlan integration with Finn. Atlan catalogs business data and documents its meaning, ownership, and relationships.

Discuss this integration Explore the workflows

The work behind the connection

What you can do with Atlan.

Atlan catalogs business data and documents its meaning, ownership, and relationships.

Find the right data and complete the analyst handoff

Finn turns a business data request into a documented dataset selection and a concrete path to the requested analysis.

Typically handled byData discovery analyst

Starts when

A business team requests data for a defined report or decision.

What Finn handles

  1. Read the business question, search Atlan for relevant assets and glossary terms, and compare recorded definitions, freshness information, ownership, and quality context.
  2. Confirm the selected dataset with its owner where the catalog leaves a material question, then arrange any required access decision through the connected service system.
  3. Deliver the dataset guide and query requirements in the connected analytics workspace, create the agreed analysis task, and record the selected assets and owner responses against the request.

The result

The business request has a confirmed data source, a documented access decision, and an assigned analysis handoff with usable context.

Close the metadata gaps for a new dataset

Finn gathers the business context behind a newly cataloged dataset and records accepted descriptions and definitions so other teams can use it responsibly.

Typically handled byData steward and catalog coordinator

Starts when

A new dataset appears in Atlan or enters the team's cataloging queue.

What Finn handles

  1. Read the asset's schema, source context, and existing related terms, then ask the responsible owner for missing purpose, field meanings, and operating limitations.
  2. Assemble the metadata changes with source links and submit the exact descriptions and glossary updates for the steward's approval.
  3. Apply the accepted changes in Atlan, link the final asset record in the connected cataloging task, and notify the requesting team that the documentation is complete.

The result

The dataset has accepted business documentation and a closed cataloging record linked to the final asset.

Deliver a schema change impact packet

Finn traces the recorded dependencies of a proposed data change and completes the coordination work needed for the owner to make an informed change decision.

Typically handled byData change coordinator

Starts when

An engineering team proposes a schema or dataset change.

What Finn handles

  1. Locate the affected asset in Atlan, traverse its recorded downstream lineage, and identify related reports, data products, and recorded owners without assuming the catalog captures every dependency.
  2. Build the impact packet in the connected document tool, collect missing owner context, and record the change owner's accepted migration or notification decisions.
  3. Create the agreed consumer tasks in the connected engineering system, send affected owners the change details, and link the final impact record to the proposed change.

The result

The change owner receives a traceable impact assessment and completed notification work, with consumer actions assigned.

Resolve conflicting business metric definitions

Finn coordinates the evidence and owner decisions needed to settle how a business metric is defined and carries the accepted definition into the catalog.

Typically handled byAnalytics operations analyst and business glossary steward

Starts when

Teams report different numbers for what appears to be the same business metric.

What Finn handles

  1. Read the relevant Atlan glossary terms and asset lineage, then compare the metric definitions and reporting context from the connected analytics tools.
  2. Document the differences in filters, time periods, and business meaning, and collect the responsible metric owners' decision about the accepted definition and remaining exceptions.
  3. Apply the approved glossary and asset-description changes in Atlan, create accepted report correction tasks in the connected analytics project system, and deliver the decision record to the affected teams.

The result

The metric has an accepted definition and traceable exceptions, with report changes assigned to their owners.

Coordinate a data quality issue through its recorded resolution

Finn connects a data quality problem to affected people and work, then closes the communication record after confirmed recovery.

Typically handled byData quality operations coordinator

Starts when

A data quality issue is reported for an Atlan-cataloged asset.

What Finn handles

  1. Read the reported issue, asset ownership, and downstream lineage; gather current evidence from connected data quality or pipeline tools.
  2. Notify the data team, create the engineering issue, and apply the owner's accepted catalog warning so consumers see the limitation.
  3. After the data owner confirms repair and validation, update the catalog notice with approval, notify affected consumers, and close the coordination record with repair evidence.

The result

Consumers receive accurate issue and recovery information, and the catalog and engineering record reflect the verified outcome.

Complete a data product's catalog launch

Finn organizes a data product's business description, supporting assets, operating guidance, and owner acceptance into a usable catalog entry.

Typically handled byData product operations manager

Starts when

A data owner accepts a dataset collection for release as a business data product.

What Finn handles

  1. Read the accepted purpose, intended consumers, source assets, and operating limits from Atlan and the connected project records, collecting missing ownership or usage guidance.
  2. Assemble the data product entry and related documentation, then present the exact catalog changes and intended audience to the responsible owner for approval.
  3. Create or update the accepted Atlan records, send the existing authorized audience the product guide through connected messaging, and close the launch task with the final catalog links.

The result

The data product has an accepted catalog presence, documented usage context, and a completed launch handoff.

Connection setup

Set up the connection around your work.

Contact Finn to discuss the records your workflow needs and the actions you want it to perform.

Your team chooses what Finn can access, what agents can change, and when a person must approve the work. The connection needs the appropriate account access and permissions from Atlan.

Visit Atlan

The Finn platform

Finn Agents

Help customers. Work with your team. Finish the job.

Explore Agents

Finn Systems

Business apps for the work behind the conversation.

Explore Systems

Finn AI Gateway

Control connected AI apps, models, access, and spending.

Explore AI Gateway

Meet Finn

Put your Atlan integration to work.

Tell us which records, actions, and teams the connection needs to support.

Discuss your workflow Get started