Data Assets
Overview
Data assets are pointers to remote data storage locations that workflows use to read from or write to. Rather than configuring storage paths directly in each node, you create data assets once and reference them across multiple workflows. This centralizes storage configuration and simplifies credential management.
Supported Data Asset Types
Delta Table
Delta tables stored directly on cloud storage (S3, GCS, Azure Blob Storage). Use this type when you want to write data in Delta Lake format to your own storage buckets without going through a data platform like Databricks.
| Storage Provider | Path Scheme | Required Credential |
|---|---|---|
| AWS S3 | s3a:// | AWS Access Key |
| Google Cloud Storage | gs:// | GCP Service Account |
| Azure Blob Storage | abfs:// | Azure Storage Key |
Databricks Unity Catalog Table (DATABRICKS_TABLE)
Tables managed through Databricks Unity Catalog. Use this type when you want Databricks to handle storage, governance, and metadata management. Requires a configured Databricks Integration.
Managing Data Assets
Accessing Data Assets
Navigate to Data Assets in the left sidebar to view and manage your data assets.

Creating Data Assets
- Click Create Data Asset in the top right
- Select the asset type (Delta Table or Databricks Table)
- Configure the storage location and credentials
- Provide a name and optional description
- Click Create to save
Data Asset Operations
From the Data Assets page, you can:
- View all existing data assets with their type and storage location
- Edit asset name and description
- Delete assets that are no longer needed
- Filter by asset type using the dropdown
Using Data Assets in Workflows
Reference data assets in sink nodes to write processed data to storage:
- Delta Sink Node - Select a Delta Table asset to write data in Delta Lake format
- Databricks Sink Node - Select a Databricks Table asset to load data into Unity Catalog
When configuring a sink node, use the Select a Saved Table dropdown to choose from your data assets instead of manually entering storage paths.