Actions42
- Genie Actions
- Databricks SQL Actions
- Unity Catalog Actions
- Model Serving Actions
- Files Actions
- Vector Search Actions
Overview
This node integrates with the Databricks platform, specifically supporting multiple resources including Unity Catalog. For the Unity Catalog - Create Catalog operation, it allows users to create and manage data catalogs within their Databricks workspace. This is useful for organizing and governing data assets such as tables and schemas in a centralized manner.
Typical use cases include:
- Automating the creation of new data catalogs as part of a data pipeline.
- Managing metadata and access control for datasets in Databricks.
- Integrating catalog management into broader workflows that involve data processing or analytics.
For example, a user might configure this node to create a new catalog before loading data into it, ensuring proper organization and governance from the start.
Properties
| Name | Meaning |
|---|---|
| Catalog | Select a Unity Catalog to work with. The list is automatically populated from your Databricks workspace. |
| Schema | Select a schema from the chosen catalog. The list is dynamically loaded based on the selected catalog. |
The Catalog property lets you choose which catalog to operate on, while the Schema property specifies the schema within that catalog relevant to the operation.
Output
The node outputs JSON data representing the response from the Databricks API for the requested operation. For the "Create Catalog" operation under Unity Catalog, the output JSON typically contains details about the newly created catalog or confirmation of the action performed.
If the node supports binary data (not applicable here), it would provide binary output accordingly, but for this operation, the output is purely JSON.
Dependencies
- Requires an active Databricks workspace with Unity Catalog enabled.
- Needs an API authentication token configured in n8n credentials to authorize requests to the Databricks API.
- The node uses the Databricks REST API endpoints under
/api/2.1/unity-catalog/to perform operations. - Network connectivity to the Databricks instance specified in the credentials.
Troubleshooting
Common Issues:
- Authentication failures due to invalid or expired API tokens.
- Insufficient permissions in Databricks to create or modify catalogs.
- Incorrect catalog or schema names leading to API errors.
- Network connectivity problems preventing API calls.
Error Messages:
API Error: <status> <statusText>: Indicates the Databricks API returned an error. Check the status code and message for details, verify credentials and permissions.Network Error: No response received from server: Suggests network issues or incorrect host URL configuration.- Other generic errors will be logged with stack traces if the node is set to continue on failure.
Resolutions:
- Verify and refresh API authentication tokens.
- Ensure the user has appropriate roles and permissions in Databricks.
- Double-check catalog and schema selections exist and are spelled correctly.
- Confirm network access and correct Databricks host URL in credentials.