Actions35
- Genie Actions
- Databricks SQL Actions
- Unity Catalog Actions
- Model Serving Actions
- Files Actions
- Vector Search Actions
Overview
The "Create Volume" operation within the Unity Catalog resource of this Databricks node allows users to create a new volume in a specified catalog and schema. This is useful for managing data storage volumes programmatically within Databricks' Unity Catalog, enabling automation of data organization and management tasks.
Typical use cases include:
- Automating the provisioning of storage volumes as part of data pipeline setups.
- Managing data environments by creating isolated volumes for different projects or teams.
- Integrating volume creation into CI/CD workflows for data infrastructure.
For example, a user might create a managed volume in a specific catalog and schema to store processed data outputs securely and separately from external data sources.
Properties
| Name | Meaning |
|---|---|
| Catalog | The catalog under which the volume will be created. |
| Schema | The schema within the catalog where the volume will reside. |
| Volume Name | The name assigned to the new volume. |
| Volume Type | The type of volume to create; options are: EXTERNAL (for externally managed storage) or MANAGED (managed by Databricks). |
Output
The node outputs JSON data representing the result of the volume creation request. This typically includes details about the newly created volume such as its identifier, name, type, and possibly metadata returned by the Databricks API.
If the node supports binary data output, it would relate to any files or artifacts associated with the volume creation process, but based on the provided code and properties, the primary output is structured JSON data describing the created volume.
Dependencies
- Requires an active connection to a Databricks workspace via an API token credential.
- The node depends on proper configuration of the Databricks host URL and authentication token in n8n credentials.
- Access permissions in Databricks must allow volume creation within the specified catalog and schema.
Troubleshooting
- Authentication errors: Ensure that the API token credential is valid and has sufficient permissions.
- Invalid catalog or schema: Verify that the specified catalog and schema exist and are accessible.
- Volume name conflicts: If a volume with the same name already exists, the API may return an error; choose a unique volume name.
- Incorrect volume type: Use only the allowed options (
EXTERNALorMANAGED) for the volume type property. - API connectivity issues: Check network access to the Databricks workspace and correct base URL configuration.
Common error messages will generally come from the Databricks API and should be interpreted accordingly, often indicating permission issues, invalid parameters, or resource conflicts.