# Matillion DPC Euno's Matillion Data Productivity Cloud (DPC) integration supports auto-discovery of the following Matillion resources: * Matillion Projects * Matillion Pipelines (Transformations and Orchestrations) * Database Tables and Schemas {% hint style="info" %} This integration is designed for Matillion Data Productivity Cloud (DPC), not Matillion ETL (Matillion's legacy product). {% endhint %} ## Setting up Euno's Matillion Integration ### Step 1: Configure New Matillion Source in Euno #### Step 1: Access the Sources Page 1. Go to the **Sources** page. 2. Click on **Add New Source** and select **Matillion** from the list of supported platforms. #### Step 2: General Configuration Asterisk (\*) means a mandatory field. | Configuration | Description | | ------------------------ | ---------------------------------------------------------------------------------------------------------------- | | Name\* | Enter a name for your Matillion source (e.g., "Matillion") | | Data Platform\* | Select your target data platform: BigQuery, Snowflake, or Databricks | | Account Identifier\* | If Snowflake or Databricks is selected, this is the account URL (e.g. abc12345.us-east-1.snowflakecomputing.com) | | Default Database\* | The default database name for your data warehouse, as configured in Matillion | | Default Schema\* | The default schema name for your data warehouse, as configured in Matillion | | Matillion Project Name\* | The name of your Matillion project | #### Step 3: Optional Matillion Configuration | Configuration | Description | | ---------------------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | | Matillion Project ID | The unique identifier for your Matillion project | | Source Git Repository | The Git repository URL containing your Matillion pipeline definitions | | Source Git Branch | The Git branch to reference (e.g., "main" or "develop") | | Default Environment ID | The default environment ID for your Matillion project (e.g., d3779338-264f-1f3-aeb7-8493cdcca9d4) | | Default Agent ID | The default agent ID for pipeline execution | | Project Variables | To have Euno substitute project variables for their values, see [Configure Matillion Project variables](/sources/transformation-etl/matillion/configure-matillion-project-variables.md) | **How Optional Configuration Affects Discovery:** * **Project Creation**: When both **Matillion Project Name** and **Matillion Project ID** are provided, Euno will create a Matillion project resource that serves as the parent container for all discovered pipelines. * **Git Source Links**: When **Source Git Repository** and **Source Git Branch** are configured, Euno will generate external links from each pipeline directly to its source file in the Git repository, enabling easy navigation to pipeline definitions. * **Matillion Designer Links**: When **all four fields** (Project ID, Source Git Branch, Default Environment ID, and Default Agent ID) are provided, Euno will create direct links to edit each pipeline in the Matillion Designer interface. These links follow the format: ``` https://app.matillion.com/designer/project/{project_id}/branch/{branch}?environmentId={environment_id}&agentId={agent_id} ``` #### Step 4: File Pattern Configuration | Configuration | Description | | ---------------- | --------------------------------------------------------------------------------- | | Include Patterns | File patterns to include (defaults to files ending with .tran.yaml or .orch.yaml) | | Exclude Patterns | File patterns to exclude from processing | #### Step 5: Resource Cleanup To keep your data relevant and free of outdated resources, Euno provides automatic **resource cleanup** options. These settings determine when a resource should be removed if it is no longer detected by a source integration. For a detailed explanation on Euno's cleanup strategies, see: [Resource Sponsorship in Euno](/developer-reference/technical-concepts/resource-sponsorship-and-cleanup-in-euno.md). * **Immediate Cleanup**: Remove resources not detected in the most recent successful source integration run. * **No Cleanup**: Keep all resources indefinitely, even if they are no longer detected. #### Step 7: Save Configuration Click the **Save** button to complete the setup. ## How to Use the Integration ### Step 1: Prepare Your Matillion DPC Artifacts The Matillion integration works by processing DPC artifacts that you upload to Euno. For a one-time ingestion of Matillino pipelines, you can upload the DPC artifact directly through the Euno UI. To setup CI/CD integration with your Matillion Git repository, see [Setting Up continuous ingestion of Matillion Artifacts](/sources/transformation-etl/matillion.md) . ## Features ### Project and Pipeline Discovery The Matillion integration automatically discovers: * **Matillion Projects**: When project name and ID are configured * **Transformation Pipelines**: From `.tran.yaml` files * **Orchestration Pipelines**: From `.orch.yaml` files * **Pipeline Metadata**: Including names, types, and hierarchical relationships ### Database Resource Discovery The integration maps your data infrastructure by discovering: * **Databases**: Target databases referenced in your pipelines * **Schemas**: Database schemas used by your transformations * **Tables**: Input and output tables with full lineage tracking ### Lineage and Dependencies Advanced dependency tracking includes: * **Table Dependencies**: Automatic discovery of input and output tables in each pipeline, including the lineage between them. This means that for each output table, we will show the input tables it depends on. * **Cross-Platform Integration**: Works with Euno's existing dependency resolution for comprehensive lineage ### External Links When Git repository information is provided, the integration creates direct links to: * **Source Code**: Links to pipeline definitions in your Git repository * **Matillion Designer**: Direct links to pipeline editing in Matillion DPC (when all required IDs are configured) --- # Agent Instructions: Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter: ``` GET https://docs.euno.ai/sources/transformation-etl/matillion.md?ask= ``` The question should be specific, self-contained, and written in natural language. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.